I'm not currently working in trunk so it doesn't really matter to me but I think to not disrupt our
users and potential developers it would be nice to simply say we've switched to maven 2 and not
break them if they are being productive on Maven 1. Is there something about Maven 1 that is
impeding the conversion? Or is the disruption to generate a sense of urgency?
Matt
Jason Dillon wrote:
I think that removing the m1 files is a good idea, as it will help force
us to get m2 to build... which really should not take that long to get
functional 100% of the time.
--jason
On Jun 26, 2006, at 9:19 PM, Alan D. Cabrera wrote:
Jacek Laskowski wrote:
On 6/26/06, David Jencks <[EMAIL PROTECTED]> wrote:
I'm suggesting that we declare the m1 build obsolete and remove it,
except possibly for the assembly step and perhaps modules where the
tests do not run under m2.
Well, don't get it annoying, but I still don't understand it. Let's
pretend we've named the m1 build obsolete, what's next? Shall we call
a vote? If it passes, what would be the next steps? If you removed the
top-level build.xml I'd know what it'd mean, but now I don't get it.
Yes, we call a vote then remove the project.xml/project.properties
files. build.xml is for Ant; I don't think we use that.
Regards,
Alan
