|
From: Colin S. <col...@ex...> - 2004-11-17 15:46:22
|
Yannick Menager wrote: >Rod Johnson <rod <at> interface21.com> writes: > > >>Juergen and I have discussed having a new "tiger" tree parallel to "src" >> >> >and "test". tiger would have its own > > >>src and >>test trees. >> >> > >I would suggest: > >src/java1.3/ >src/java1.5/ >src/test1.3/ >src/test1.5/ > >personally I've always like to keep all things that are created by the >development team under src/ package, rather than cluttering the root level > > Yes, if jdk1.5 moves into the main module and is actually built by the main build file, I don't think it's very consistent with the existing structure or with other common layouts, to do it as /tiger/src /tiger/test I've personally always tried to keep all source artifacts handled by the one build, underneath /src in various dirs off of that, with output going to various dirs off of: /target (we already do the latter, for the most part, in Spring as a result of the build reorg I did about a year ago). In terms of an exact format for the dirs underneath /src I've generally tried to standardize on the Maven recommended directory format, which is as good as any other, and makes it simpler for people to use Maven if they want to, i.e. /src/java /src/test /src/test-cactus /src/webapp etc... Rod,Juergen, if the source does come into the main module, how do you see it being compiled? As part of the main build, or as its own little mini project? Colin |