Jason van Zyl-5 wrote:
>
> What will happen is that when we get close to a beta, many of the
> dependencies will boil out, and once things are thoroughly tested
> we'll have the versions we need.
>
Can you provide an overview of the plans? Which dependencies are being
considered for removal? Which ones might be added?
This would come handy for any early adopter, like it is our case.
Jason van Zyl-5 wrote:
>
> I have no problems making CQs for the
> dependencies are needed.
>
Submitting CQs is not the problem. You could save months if dependencies are
already approved, since you will skip full IP review (something that takes
months). And you can not release an 1.0 version at Eclipse without full
review.
Jason van Zyl-5 wrote:
>
> I have a tool to automate
> the submission of CQs so this is not going to be a burden for me.
>
I'm trying to propose something that works for everyone, not "you" or "me".
As you probably know, the Eclipse Buckminster project is also interested, so
with just settling on a few versions, maven developers can help a community
of adopters.
-----
http://www.linkedin.com/in/amuino Abel Muiño Vizcaino -
http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com
--
View this message in context:
http://www.nabble.com/Alignment-of-maven-3.0-dependencies-and-Eclipse-IP-approved-libraries-tp22187681p22189191.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
