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 "<project />" 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]
