On 03/02/2009, at 1:24 AM, Brian E. Fox wrote:
Any reason not to use a new field in settings.xml? I think 2.1.x can
be capable of updating the model version.
Why introduce a bunch of new work for this?
I'm just concerned that we make this exception here and suddenly we
have multiple files springing up in ~/.m2, and then having to
duplicate work like supporting $M2_HOME/conf/settings.xml.
It's not a showstopper.
Also, we wanted to make it
work in 2.0.x if possible. Since it's completely optional to use,
there
should be little downside risk to porting it back.
I'd really prefer we focused on getting 2.1 out, as you said, rather
than allow another excuse not to.
What's left before this is releasable as part of 2.1.x?
Just some manual testing and docs updates for the site when it's
ready.
In the mean time, can someone please release the dependency so that we
can move forward with the next milestone release? I think it's ready
to go.
- Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
