> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 26, 2004 8:54 AM > [...] > 2/ These share-12-13-14 and share-13-14 subprojects have no functional > meaning and I'd like to have a single javadoc report, a single site, a > single checkstyle errors, etc. > > I think this point 2 is my main problem. It's fine to have several > subprojects when they have a functional meaning but I don't > feel this is > the case.
Why not? You have them already but you are just willing to hide this fact. For maven users soon when transitive dependecies will work (they are alredy implement in m2 alpha) there will be no differnce - they still will be required to define single dependecy on given cactus version and other dependecies will be auto magically resolved... The same will happen with javadocs... >This problem is all the more evident in that Cactus already > has an existing build which does this and it's hard to > justify to users > that we have something "less" good because of a technical > problem. If we > don't have a single site, looking at reports is harder > because you have > to navigate to different location to get a full vision (which > is BTW the > reason for the dashboard plugin I have started). > > Any other ideas? Don't know if this is wise or if it will work but you might also think about sharing sources in one project (let's call it 'main') and having 3 other projects which will generated jars. In those 3 project you can use <sourceModifications> for removing some classes and have their own dependecies and <sourceDirectory>../main/src/main/java/</sourceDirectory>. This might work with maven but it might be more tricky to use such layout with IDEs. Anyway I am not sure if this is good idea... Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
