FYI: http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-115
Filed as an issue not too long ago. -Peter ----- Original Message ----- From: "Daniel McAllansmith" <[EMAIL PROTECTED]> To: "Turbine Maven Users List" <[EMAIL PROTECTED]> Sent: Wednesday, October 02, 2002 8:01 PM Subject: Re: Goals not found with beta7... > Lovely! All seems to be working, I get my list of goals at least. > Seems to be ok if have a read only plugins dir once they're all extracted. > Is there anything other than the local repos and the plugins dir, at plugin > install time, that maven needs write access to? > > Thanks for the help > Dan > > On Thu, 03 Oct 2002 14:30, Daniel McAllansmith wrote: > > On Thu, 03 Oct 2002 14:23, [EMAIL PROTECTED] wrote: > > > > > > Bugger! > > After doing the -X -e -g (output below), I thought 'extracts the sample, > > eh?', 'I wonder where too?'. > > I installed the maven onto a shared drive, for which I only have read > > permission, when I ran it the first time it complained about not being able > > to write to the local repos, so I moved local repos. > > I didn't realise it would need write permissions for the plugins > > directory... nothing mentioned in the doc, and that error is less than > > crystal clear. > > > > It _seems_ to be working now, still downloading all the jars (slow > > connection), but that's more than it was doing before. > > > > Fingers crossed > > Dan > > > > > Can you run maven -X -e -g and post the output/or email it to me? > > > > Ok. Run against the unjarred example project.xml I get: > > [daniel@lithium mavenexample]$ maven -X -e -g > > __ __ > > > > | \/ |__ Jakarta _ ___ > > | > > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > > | > > |_| |_\__,_|\_/\___|_||_| v. 1.0-beta-7 > > > > /home/daniel/devel/tmp/mavenexample > > > > [DEBUG] Adding reference: maven.dependency.classpath -> > > [DEBUG] Adding reference: maven-classpath -> > > > > Available [Plugins] / Goals > > ``````````````````````````` > > [build] ( NO DEFAULT GOAL ) > > start ...................... ( NO DESCRIPTION ) > > > > and the same maven.log messages as before. > > Those DEBUG messages sure look dodgy... > > > > > Daniel McAllansmith <[EMAIL PROTECTED]> wrote on 03/10/2002 > > > > > > 11:55:45 AM: > > > > 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. > > > > > > Nope, when maven first runs it should expand that jar into a directory. > > > That means it hasn't successfully started ever....that's not a good sign. > > > > > > > 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. > > > > > > Can't tell, but it's definitely a baddie. > > > > > > > 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? > > > > > > Yep, I sanity tested it before sending the previous email on my machine. > > > > > > > > > Can you run maven -X -e -g and post the output/or email it to me? > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
