Found the problem myself. The PATH was incorrectly pointing to the old maven installation.
2005/8/25, Wim Deblauwe <[EMAIL PROTECTED]>: > > I installed Maven 1.1beta1 on a machine that already had Maven 1.0.2 and > executed 'maven' (without any goal specified). I got the following error > everytime (and I'm not using the cruisecontrol plugin). > > Any ideas? Currently I can't do anything with that maven installation... > > regards, > > Wim > > plugin maven-cruisecontrol-plugin-1.6 is cached (dynatag dep) but no > longer present > Cache invalidated due to out of date plugins > javax.xml.parsers.FactoryConfigurationError: Provider > org.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated: > java.lang.NullPointerExce > ption > at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java > :113) > at org.apache.maven.plugin.JellyScriptHousing.parse( > JellyScriptHousing.java:152) > at org.apache.maven.plugin.JellyScriptHousing.parse( > JellyScriptHousing.java:177) > at org.apache.maven.plugin.PluginManager.loadUncachedPlugins( > PluginManager.java:238) > at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java > :303) > at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java > :204) > at org.apache.maven.MavenSession.initialize(MavenSession.java:171) > at org.apache.maven.cli.App.doMain(App.java:498) > at org.apache.maven.cli.App.main(App.java:1258) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > > You have encountered an unknown error running Maven. > Please help us to correct this problem by following these simple steps: > - read the Maven FAQ at http://maven.apache.org/faq.html > - run the same command again with the '-e' parameter, eg 'maven -e jar' > - search the maven-user archives for the error at > http://www.mail-archive.com/users@maven.apache.org > - post the output of maven -e to JIRA at ???issueTrackingUrl??? (you must > sign up first) > - run 'maven --info' and post the output as the environment to the bug > above > > Total time : 29 seconds > Finished at : Thursday, August 25, 2005 12:00:38 PM CEST >
