On Thu, 03 Oct 2002 13:43, [EMAIL PROTECTED] wrote: > Can you try running maven -g against the simple-java example in the > MAVEN_HOME\plugins\maven-examples-plugin-1.0\simple-java directory? > > That way you're working off something that's guaranteed :) to work....
Ok, I assume you mean the example in the plugins/maven-examples-plugin-1.0.jar, I unzipped and tried maven -g against it's project.xml. I get the same output on the command line, a slightly different maven.log. Command line output: [daniel@lithium mavenexample]$ maven -g __ __ | \/ |__ Jakarta _ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-7 /home/daniel/devel/tmp/mavenexample Available [Plugins] / Goals ``````````````````````````` [build] ( NO DEFAULT GOAL ) start ...................... ( NO DESCRIPTION ) maven.log contents: [daniel@lithium mavenexample]$ cat maven.log 2002-10-03 13:40:25,932 DEBUG org.apache.maven.app.App - Initializing core. 2002-10-03 13:40:30,836 ERROR org.apache.commons.jelly.tags.ant.AntTag - Class org.apache.commons.jelly.tags.werkz.ProjectTag doesn't support the nested "path" element. I would infer from the ERROR in the log file that I've got some sort of version mismatch with jelly. I don't have a classpath defined, the maven script just uses a classpath of tho forehead jar and then I suppose the classpath is expanded to include those elements specified in forehead.conf, all of which come from within MAVEN_HOME. Presumably other people are successfully using a fresh install of beta7 though? Dan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
