Hi, I was just wondering that if you're going to reorganize the whole source tree and have distinct structure for each "produced jar", maybe we could use easyant :). Note that the next release of easyant will provide a maven-publisher plugin. Ping me if you want to POC this or have more informations
In any case here is my vote : 2010/5/18 Jesse Glick <jesse.gl...@oracle.com> > Should the Ant source tree (src/main/ and perhaps also src/tests/) be split > into subtrees? > > [ ] No, leave it the way it is - one big tree, using <selector> to > conditionally compile pieces and route classes to various JARs. > > [X] Yes, split it into subtrees, where each tree maps to an output JAR, may > have its own classpath, and is compiled completely or not at all. > > And while we're at it: > > Should ant.jar and ant-nodeps.jar be consolidated? > > [ ] No, leave these as two JAR outputs (and two subtrees if the first > proposal is accepted). > > [X] Yes, merge them into one ant.jar (and one subtree " " " " " "), to > include all tasks and types with no linkage-level deps on 3rd-party > libraries (even if there is an implicit dep on a 3rd-party tool such as > Perforce), and remove the "Core" vs. "Optional" distinction in the manual. > -- Jean Louis Boudart Independent consultant Project Lead http://www.easyant.org
