We should fix it, but it has no bearing on the binary that is staged.
-Original Message-
From: Ralph Goers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 6:36 PM
To: Maven Developers List
Subject: Re: 2.0.x bootstrap process is fixed
Brian E. Fox wrote:
> Nope, you ca
Brian E. Fox wrote:
Nope, you can't run the release plugin from the bootstrap...I just use
whatever maven I happen to have installed, usually the snapshot I last
built for testing.
Does this mean it is OK to release 2.0.9 even though bootstrap.sh
doesn't work? Just curious.
opers List
Subject: Re: 2.0.x bootstrap process is fixed
Now I'm wondering how the rest of you actually build maven. I checked
out from the 2.0.9 tag and it failed the same way. So I guess
bootstrap.sh isn't actually used to build Maven for a release?
Ralph Goers wrote:
> Now it is fai
Now I'm wondering how the rest of you actually build maven. I checked
out from the 2.0.9 tag and it failed the same way. So I guess
bootstrap.sh isn't actually used to build Maven for a release?
Ralph Goers wrote:
Now it is failing again, albeit differently. I'm getting a
NullPointerException.
Now it is failing again, albeit differently. I'm getting a
NullPointerException. Here is the tail end of the log.
Building project in /projects/maven2/temp/maven-2.0.x/apache-maven
--
Cleaning /projects/maven2/temp/maven-2.0.x/apach
The bootstrap should be fixed now, just FYI. It seems the bootstrap-
mini code, which the bootstrap.[sh|bat] scripts depend on, doesn't
track POM properties, and isn't smart enough to interpolate them into
dependency versions for now. My guess is, we didn't get bitten by $
{mavenVersion} the
