Asking here on the dev-list because I would like to contribute to any of
the points below if unaddressed.
What is the current status of the ConflictResolver SPI as outlined in:
* http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
* http://www.nabble.com/-m2--Conflict-resolvers-td10144607i40.html
...?
The issue is tracked as open in:
http://jira.codehaus.org/browse/MNG-612
Additionally, I'm not seeing a "FailFastConflictResolver" in
org.apache.maven.artifact.resolver, the purpose of which would be to
immediately fail the build if two projects bring in transitive
dependencies of different versions. Perhaps this is because conflict
resolvers are based on a chain implementation, and it's not the resolver
itself which has authority to fail a build (ie. can just return null and
delegate to the next resolver in the chain)?
Some related questions:
* Is support here planned to be backported into 2.0.x or 2.1.x? I do
see some year-old commits into
https://svn.apache.org/repos/asf/maven/components/branches/MNG-612-2.0.x/,
for example.
* Is there a publicly-viewable roadmap for 3.0 with time estimates?
* I see ConflictResolver unit tests to check for proper resolution, but
no examples of a POM configuring an explicit ConflictResolver set?
We've moved our build implementation heavily to Maven over at JBoss
within the Application Server, and I'd like to help augment Maven to fit
our needs.
Appreciated. :)
S,
ALR
--
Andrew Lee Rubinger
Sr. Software Engineer
JBoss EJB3
JBoss, a division of Red Hat, Inc.
http://www.jboss.org/jbossejb3/
http://exitcondition.alrubinger.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
