Great! Debugged 2.0-alpha-4, and I think I've solved ARCHETYPE-220<http://jira.codehaus.org/browse/ARCHETYPE-220>issue. Can someone with enough privileges please flag the issue that it contains a patch (no additional tests, yet), and if agreed to increase issue priority from Minor to Major as IMO this issue prevents archetype-plugin from being fully adopted, especially in (closed source) corporate environments.
Regards, Stevo. On Thu, Nov 12, 2009 at 12:26 PM, Brett Porter <[email protected]> wrote: > Nice catch, I've removed it. > > On 12/11/2009, at 7:22 PM, Stevo Slavić wrote: > > > Hello Maven developers, > > > > I'd like just to inform you that while checking out maven archetype I've > > noticed that there is a maven-archetype-2.0-alpha-5 tag created in April > > 2009; most recent release is 2.0-alpha-4 from September 2008, and current > > trunk is 2.0-alpha-5-SNAPSHOT, so this existing > maven-archetype-2.0-alpha-5 > > tag might cause problems when 2.0-alpha-5 gets actually released. > > > > Regards, > > Stevo. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
