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/apache-maven/target...
Compiling sources ...
Packaging resources ...
Packaging
/projects/maven2/temp/maven-2.0.x/apache-maven/target/apache-maven.jar ...
------------------------------------------------------------------
Exception in thread "main" java.lang.NullPointerException
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.createInstallation(BootstrapInstaller.java:254)
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.run(BootstrapInstaller.java:136)
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.main(BootstrapInstaller.java:91)
John Casey wrote:
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 same way we did with ${wagonVersion}
simply because the maven POMs are all in the reactor, where the wagon
ones must be resolved.
Looks like the usage of wagonVersion started with the introduction of
the webdav wagon.
-john
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
