Vincent Massol wrote: >I understand you're trying to figure good alternatives to this aggregated >jar use case but jdepend isn't a good one... :-) > > I'm not trying to think of alternatives... I already agreed we probably want to implement the use case. I'm just trying to get to the bottom of why you think doing things two ways is a good idea. You've given reasons yourself that it is a bad idea. It's not just about functionality, but the best practices we recommend.
>BTW, this will require the ability to dynamically include/exclude m2 modules >according to a configuration. As a builder, I need to say in my profile that >I want to build for, say, resin and tomcat but not for any other containers >(because I don't have them installed for example). How will I be able to >specify this? :-) > > I assume you are now talking about how you'd configure a Cactus plugin such that the project specifies all of the containers, but the user only builds one or two. Yes, we need profile support. >>You can start doing so if you like... snapshots work very nicely now :) >> >> > >Hmm... Is there a maven2 repository @ codehaus now? > > > Equivalent to dist.codehaus.org? No, but let's discuss that on [EMAIL PROTECTED] It would be good to have a plan for all the projects there. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
