>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? 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. >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. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
