I would like to change the directory structure in AS trunk to fit the Maven conventions. This just means changing src/main to src/main/java, src/resources to src/main/resources, etc. This will make the AS build consistent with other Maven builds. I plan to start making these changes tomorrow around 14 UTC and should be finished by the end of the day. Please let me know if there is any reason not to do this.

I have a pretty big patch I need to merge into trunk: http://fisheye.jboss.org/changelog/JBossAS/?cs=93783 I'll try and start it tomorrow AM, would you mind holding until then? S, ALR On 09/22/2009 04:02 PM, Paul Gier wrote: > I would like to change the directory structure in AS trunk to fit the Maven > conventions. This just means changing src/main to src/main/java, src/resources > to src/main/resources, etc. This will make the AS build consistent with other > Maven builds. I plan to start making these changes tomorrow around 14 UTC and > should be finished by the end of the day. Please let me know if there is any > reason not to do this. > > Thanks! > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development

Paul Gier wrote: > I would like to change the directory structure in AS trunk to fit the Maven > conventions. This just means changing src/main to src/main/java, src/resources > to src/main/resources, etc. This will make the AS build consistent with other > Maven builds. I plan to start making these changes tomorrow around 14 UTC and > should be finished by the end of the day. Please let me know if there is any > reason not to do this. > > Thanks! > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > I expect you are also going to modify the directories used for output (.e. classes, resources). Is the testsuite going to work after these changes? There are pointers from the testsuite into the build, and not all of these use the classpaths from libraries.ent.