On 14/05/2008, Rahul Akolkar <
rahul.akolkar@...> wrote:
> On 5/14/08, sebb <
sebbaz@...> wrote:
> > On 14/05/2008,
rahul@... <
rahul@...> wrote:
> > > Author: rahul
> > > Date: Tue May 13 18:22:45 2008
> > > New Revision: 656075
> > >
> > > URL:
http://svn.apache.org/viewvc?rev=656075&view=rev> > > Log:
> > > Hard code version in source assembly descriptor to work around m2 bug when releasing with JDK 1.4 (thanks to Niall Pemberton).
> > >
> >
> >
> > BTW, which Maven command is affected by this bug?
> >
> > I just tried "mvn assembly:assembly" using the original version of
> > src.xml, and the generated src.zip file used 0.8 rather than 2.4.1.
> > This was using Maven 2.0.8/Java 1.4.2/WinXP
> >
> > I must be doing something wrong for it to come out right ;-)
> >
>
> <snip/>
>
> :-)
>
> In this case, it manifested itself via "mvn -Prc release:perform"
> (which requires a "mvn -Prc release:prepare" beforehand).
>
> But you probably don't want to try that unless you are cutting a
> release (it will try to make changes to the pom and add the svn tag
> etc.)
>
> See same issue with couple [1] of [2] other RCs. Maybe "mvn -Prc
> install" will bring it out as well. If that doesn't, try "mvn -Prc
> deploy" (this is part of release:perform) but purposely enter bad
> creds in settings.xml so nothing actually gets deployed. Or something
> creative like that if you really want to reproduce it :-)
>
Thanks, I'll have a play.
I've not set up any user etc in settings.xml so it should not try to update SVN.
I can always unplug my network cable ...
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...