Re: plugin-parent error with 1.0rc3
You shouldn't have the plugin-parent-1.0 directory in your cache - it thinks this is a plugin, but it doesn't have a script. 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.(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]
RE: plugin-parent error with 1.0rc3
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.(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 -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin-parent error with 1.0rc3
That'll work, but it's a bit dodgy on the other peron's behalf - and if they decide to start depending on that its going to break everywhere. 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. However, Maven shouldn't be following any link in the plugin at run-time. 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 :) I'm guessing it's in maven.xml or plugin.jelly inside the plugin. Cheers, Brett > -Original Message- > From: Joe Germuska [mailto:[EMAIL PROTECTED] > Sent: Thursday, 27 May 2004 1:38 PM > To: Maven Users List > Subject: RE: plugin-parent error with 1.0rc3 > > > At 12:41 PM +1000 5/27/04, Brett Porter wrote: > >Sounds like a bug in that plugin somewhere... Where is > >plugin-parent-1.0 referred to in the other developers plugin? > > I'll check further into that; I've only written one plugin myself, a > while ago, and at the time, I don't think plugin-parent had been > introduced. Then when I found that in JIRA, I didn't spend as long as > perhaps I should have trying to figure out what's going on with with > this local plugin because that sounded like a more global problem. > > He seems to be extending a slightly modified copy of a plugin-parent > project.xml, probably coping from maven-plugins in CVS. I'm not > quite following the process that causes his plugin to look for > plugin-parent. > > I fiddled around a bit and took the suggestion from MAVEN-1262 of > putting "" in a plugin.jelly file in plugin-parent, and I > think I've got things kind of working. At least, I'm not getting > that error any more. > > Thanks > Joe > > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com >"Imagine if every Thursday your shoes exploded if you > tied them > the usual way. This happens to us all the time with computers, and > nobody thinks of complaining." > -- Jef Raskin > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: plugin-parent error with 1.0rc3
At 12:41 PM +1000 5/27/04, Brett Porter wrote: Sounds like a bug in that plugin somewhere... Where is plugin-parent-1.0 referred to in the other developers plugin? I'll check further into that; I've only written one plugin myself, a while ago, and at the time, I don't think plugin-parent had been introduced. Then when I found that in JIRA, I didn't spend as long as perhaps I should have trying to figure out what's going on with with this local plugin because that sounded like a more global problem. He seems to be extending a slightly modified copy of a plugin-parent project.xml, probably coping from maven-plugins in CVS. I'm not quite following the process that causes his plugin to look for plugin-parent. I fiddled around a bit and took the suggestion from MAVEN-1262 of putting "" in a plugin.jelly file in plugin-parent, and I think I've got things kind of working. At least, I'm not getting that error any more. Thanks Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin-parent error with 1.0rc3
Sounds like a bug in that plugin somewhere... Where is plugin-parent-1.0 referred to in the other developers plugin? > -Original Message- > From: Joe Germuska [mailto:[EMAIL PROTECTED] > Sent: Thursday, 27 May 2004 12:25 PM > To: [EMAIL PROTECTED] > Subject: plugin-parent error with 1.0rc3 > > > I am having a problem with 1.0 rc2 and 1.0 rc3 when using a plugin > written by another developer who uses 1.0 rc1. > > After I installed his plugin (maven plugin:install), I started > getting this error: > java.io.FileNotFoundException: > /Users/germuska/.maven/plugins/plugin-parent-1.0/plugin.jelly (No > such file or directory) > > I upgraded from rc2 to rc3, and am getting pretty much the > same behavior. > > The only thing I can find about this is a closed JIRA issue: > http://jira.codehaus.org/browse/MAVEN-1262 > > Is the only > solution to work from CVS HEAD? > > Thanks in advance. > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com >"Imagine if every Thursday your shoes exploded if you > tied them > the usual way. This happens to us all the time with computers, and > nobody thinks of complaining." > -- Jef Raskin > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
plugin-parent error with 1.0rc3
I am having a problem with 1.0 rc2 and 1.0 rc3 when using a plugin written by another developer who uses 1.0 rc1. After I installed his plugin (maven plugin:install), I started getting this error: java.io.FileNotFoundException: /Users/germuska/.maven/plugins/plugin-parent-1.0/plugin.jelly (No such file or directory) I upgraded from rc2 to rc3, and am getting pretty much the same behavior. The only thing I can find about this is a closed JIRA issue: http://jira.codehaus.org/browse/MAVEN-1262 Is the only solution to work from CVS HEAD? Thanks in advance. -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jef Raskin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
