Try removing the plugin cache directory (.../.maven/plugins) and see if that helps. Check whether there is a mistaken plugin-parent-1.0.jar in $MAVEN_HOME/plugins first and remove that too.
- Brett
Joe Germuska wrote:
Perhaps if you run maven -e and show the FileNotFoundException stack trace
we could find out where it is occurring, although it would be easier to grep
for the use of plugin-parent :)
Well in all my mucking around, I'm getting different behavior now -- even when I remove the jimmied "plugin.jelly" file, I don't get the error any more, but I was able to find it in one of the scrollback buffers.
germuska% maven -e tomcat __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3
Plugin cache will be regenerated
org.apache.maven.MavenException: Error reading plugin script
at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:181)
at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManager.java:205)
at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:257)
at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:207)
at org.apache.maven.MavenSession.initialize(MavenSession.java:174)
at org.apache.maven.cli.App.doMain(App.java:472)
at org.apache.maven.cli.App.main(App.java:1214)
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)
--- Nested Exception ---
java.io.FileNotFoundException: /Users/germuska/.maven/plugins/plugin-parent-1.0/plugin.jelly (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:177)
at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManager.java:205)
at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:257)
at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:207)
at org.apache.maven.MavenSession.initialize(MavenSession.java:174)
at org.apache.maven.cli.App.doMain(App.java:472)
at org.apache.maven.cli.App.main(App.java:1214)
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)
At 1:52 PM +1000 5/27/04, Brett Porter wrote:
The problem is that the project.xml file is shared between plugin build-time
and plugin run-time. Extending another parent if useful for build-time, but
not run-time when it is not present.
I guess I have a pretty primitive understanding of how plugins work; I managed to write one a while back, but I didn't realize that project.xml had any run-time implications. Can you point to any more info about this?
Thanks Joe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
