On 12/18/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Stephen Colebourne wrote: > > One I noted that was missing was clirr. This is an integral part of > > commons releases, although I don't believe it has ever been part of > > maven in the past. > > > I didn't think this was at all standardised across commons. Some used > clirr, some used jdiff, most used nothing.
Yes, that's correct. I think very few use either. -- Martin Cooper There is a jdiff plugin - you > are right in that clirr was external to Maven before and it is on the > long todo list. > > > >> Inheritence - I believe the common parent is a good way to go, and > Maven > >> 2 facilitates this by allowing it to be in the repository, avoiding a > >> bizarre checkout structure. This should avoid the need for externals > >> that has been under discussion. > > So long as the resulting zip files can build a site/dist independently > > of svn, and everything can be versioned properly, a common parent is > > OK. But is that what you mean? > Yes, that's what I mean. > > I doubt it handles [collections] ;-) We release a testframework jar > > that is a subset of the src/test classes as well as the main jar. No > > separate multiproject structure. > Maven 2 can do the entirety of src/test as a separate JAR with some > limitations. While I think the multiproject structure would be a better > idea, you would have to do some customisation to do the subset you have > at the moment. > > I was actually referring to the assemblies rather than the distributable > jars, though :) > > - Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
