Yes, I noticed this when upgrading to RC4 on a clean box. Seems like the cache refresh method has a bug in it.
As for installing into plugin.user.dir - I will add a new method to do somethinng like plugin:install-user in the next release. - Brett On Wed, 30 Jun 2004 14:12:20 +0200, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I don't know if it is normal but... > In one of my plugin project I do an maven plugin:install. > The plugin was install I see a 1.0 version in maven.plugin.dir but I don't > find it in maven.plugin.user.dir. The doc says that maven.plugin.user.dir > stand for "Where maven can find plugins for this user only" so I think that > plugin:install should copy it in this directory to and > not in maven.plugin.dir ! > > The older version of the plugin (1.0-b1) is delete from both > maven.plugin.user.dir and maven.plugin.unpacked.dir > > In an other project I call this plugin and there is the following trace : > > [EMAIL PROTECTED] ~...applications/extractionVSE-test-preprod]$ maven > clean compositewar > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 > > plugin maven-compositewar-plugin-1.0-b1 is cached (goal) but no longer > present > Cache invalidated due to out of date plugins > ASTIdentifier : java.lang.reflect.InvocationTargetException > java.lang.reflect.InvocationTargetException > 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:324) > at > org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:304) > at > org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:56) > at > org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:106) > at > org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:88) > at > org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:123) > at > org.apache.commons.jelly.expression.jexl.JexlExpression.evaluate(JexlExpression.java:115) > at > org.apache.commons.jelly.expression.jexl.JexlExpressionFactory$ExpressionSupportLocal.evaluate(JexlExpressionFactory.java:168) > at > org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:106) > at > org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsString(ExpressionSupport.java:91) > at > org.apache.commons.jelly.expression.CompositeExpression.evaluateAsString(CompositeExpression.java:354) > at > org.apache.commons.jelly.expression.CompositeExpression.evaluate(CompositeExpression.java:346) > at > org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:130) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at > org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) > at > org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) > at com.werken.werkz.jelly.ProjectTag.doTag(ProjectTag.java:112) > at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) > at > org.apache.maven.plugin.PluginManager.runScript(PluginManager.java:966) > at > org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:680) > at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:606) > at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > at org.apache.maven.cli.App.doMain(App.java:486) > at org.apache.maven.cli.App.main(App.java:1215) > 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:324) > at com.werken.forehead.Forehead.run(Forehead.java:551) > at com.werken.forehead.Forehead.main(Forehead.java:581) > Caused by: org.apache.maven.plugin.UnknownPluginException: Unknown plugin > "maven-xdoc-plugin" > at > org.apache.maven.plugin.PluginManager.getPluginContext(PluginManager.java:867) > at > org.apache.maven.project.Project.getPluginContext(Project.java:331) > ... 33 more > build:start: > ... > > After this my plugin is execute correctly. > I have a maven-xdoc-plugin-1.7.2 intall in my in the maven.plugin.unpacked.dir but I > the trace i can see that maven-xdoc-plugin is unknown. > > When I try to launch my plugin an second time I didn't have the same > message and if I call maven site (for example) the xdoc tasks are call > corectly. > > Did some see that before? > > Nicolas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
