On 03/02/2009, at 12:03 PM, Brett Porter wrote:
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
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 fil
>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 porti
On 28/01/2009, at 5:48 AM, Oleg Gusakov wrote:
After a long and interesting discussion last August (http://docs.codehaus.org/display/MAVEN/Secured+Passwords
) and several meetings with users, I felt it's overdue to do the
actual implementation.
I massaged my old, vintage 2007 code and put i
Looks like the name sec.xml is too short and may be confusing. Changing
for encryption-settings.xml
Oleg Gusakov wrote:
After a long and interesting discussion last August
(http://docs.codehaus.org/display/MAVEN/Secured+Passwords) and several
meetings with users, I felt it's overdue to do the
After a long and interesting discussion last August
(http://docs.codehaus.org/display/MAVEN/Secured+Passwords) and several
meetings with users, I felt it's overdue to do the actual implementation.
I massaged my old, vintage 2007 code and put it into 2.1.x trunk.
How it all works - more detaile
