tom.bujok wrote:
It would be grate if somebody could give a little bit of feedback.
Sorry for not responding earlier.
I think the biggest concern here is backwards compatibility; this is a
puzzle that I don't think any of us have solved, and which blocks a LOT of
cool features we've considered.
Suppose we turn this feature on in Maven 2.2 or even 3.0, and suppose
someone deploys a POM with this feature to the central repository on
repo1.maven.org.
Now suppose a user of Maven 2.0 or 2.1 try to consume the new POM. They
need to follow/understand your dependency exclusions also, but naturally,
we can't go back in time and re-release those old versions with support
for the new POM features.
I don't think we know what to do about this going forward. I don't even
think we've entirely enumerated the potential issues around backward
compatibility to know how to go forward yet.
I hypothesize that the end result will be one more big compatibility
break that includes an extensibility model solid enough to satisfy our
plans for multiple years to come. But this remains to be seen... :-(
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
