Dan Diephouse wrote: > > Requiring the user to override/exclude dependencies in their pom > somehow would be kind of a pain.
Ok, but the alternative is just to turn it off (still needing to be specified), which I feel like is too much of an easy out. We're in early days here, we can make the metadata get better. We do need to make it simple though. > But, what if m2 made it simple for a user to change this. Ie m2 would > iterate through the dependency conflicts and allow you to select > different options. I don't feel like this type of prompting is appropriate in most cases, especially for something as common as dependency resolution. I think we should definitely have tools to help setup the previously mentioned configurations though. What you are proposing sounds exactly like http://deputy.sourceforge.net/ > I guess I'm just thinking how to make it easier for the user, because > I believe that ease of entry will be a real barrier to use the way > things are now. > I agree - though you have bitten off probably the hardest one of all given all your sun spec dependencies :) - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
