Eclipse Community Forums: IAM (Eclipse Integration for Apache Maven)

Help

Home

Home » Archived » IAM (Eclipse Integration for Apache Maven) » PluginDescriptor not found

Show: Today's Messages :: Show Polls :: Message Navigator

PluginDescriptor not found [message #20909]

Fri, 05 June 2009 21:49

David Wolff

Messages: 4
Registered: July 2009

Junior Member

Hello all,
I have created a custom mojo that I have deployed to a local
artifactory repository and am using in a project. The plugin executes as
expected from the maven command line; however, when I try to execute the
plugin from the Eclipse/IAM integration it bombs with the following
exception:

"The PluginDescriptor for the plugin
edu.letu.maven.plugin:ddl-post-processor was not found. Should have been
in realm:
ClassRealm[/plugins/edu.letu.maven.plugin:ddl-post-processor :1.0-SNAPSHOT@48/thread:Worker-10,
parent: null]"

I have my plugin deploying to the plugins repository in artifactory and
have verified that the plugin.xml file is in the proper place in the jar.
The m2 settings for my profile has a <pluginRepositories> element that
points to the local artifactory repo.

Is there anything I'm missing in my configuration or is this a bonafide
issue?

Thanks in advance for your help!
Dave

Report message to a moderator

Re: PluginDescriptor not found [message #20914 is a reply to message #20909]

Mon, 08 June 2009 10:35

Abel Mui

Messages: 247
Registered: July 2009

Senior Member

Hello David,

There should be no difference between your plug-in and other external
plugins.

However, if your mojo project is open in the workspace, IAM will try to
use the project (instead of the jar in your local or remote repositories).
In this case, try closing the plug-in project.

If this solves your problem, then probably there is a bug in using plugins
from the workspace.

Hope that helps!
--
Abel Muiño

David Wolff wrote:

> Hello all,
> I have created a custom mojo that I have deployed to a local
> artifactory repository and am using in a project. The plugin executes as
> expected from the maven command line; however, when I try to execute the
> plugin from the Eclipse/IAM integration it bombs with the following
> exception:

> "The PluginDescriptor for the plugin
> edu.letu.maven.plugin:ddl-post-processor was not found. Should have been
> in realm:
>
ClassRealm[/plugins/edu.letu.maven.plugin:ddl-post-processor :1.0-SNAPSHOT@48/thread:Worker-10,
> parent: null]"

> I have my plugin deploying to the plugins repository in artifactory and
> have verified that the plugin.xml file is in the proper place in the jar.
> The m2 settings for my profile has a <pluginRepositories> element that
> points to the local artifactory repo.

> Is there anything I'm missing in my configuration or is this a bonafide
> issue?

> Thanks in advance for your help!
> Dave

Report message to a moderator

Re: PluginDescriptor not found [message #20918 is a reply to message #20914]

Mon, 08 June 2009 16:16

David Wolff

Messages: 4
Registered: July 2009

Junior Member

When I closed down the mojo project in the eclipse workspace everything
ran smooth as butter. Should I report this as a bug?

Thanks!
Dave

Abel Muiño wrote:

> Hello David,

> There should be no difference between your plug-in and other external
> plugins.

> However, if your mojo project is open in the workspace, IAM will try to
> use the project (instead of the jar in your local or remote repositories).
> In this case, try closing the plug-in project.

> If this solves your problem, then probably there is a bug in using plugins
> from the workspace.

> Hope that helps!
> --
> Abel Muiño

Report message to a moderator

Re: PluginDescriptor not found [message #20922 is a reply to message #20918]

Mon, 08 June 2009 19:00

Abel Mui

Messages: 247
Registered: July 2009

Senior Member

David Wolff wrote:
> When I closed down the mojo project in the eclipse workspace everything
> ran smooth as butter.

Happy to know!

> Should I report this as a bug?

Sure, go ahead.

If you could provide a simple test case, that would be very useful. A
patch even better :-)

>
> Thanks!
> Dave
>
> Abel Muiño wrote:
>
>> Hello David,
>
>> There should be no difference between your plug-in and other external
>> plugins.
>
>> However, if your mojo project is open in the workspace, IAM will try
>> to use the project (instead of the jar in your local or remote
>> repositories). In this case, try closing the plug-in project.
>
>> If this solves your problem, then probably there is a bug in using
>> plugins from the workspace.
>
>> Hope that helps!
>> --
>> Abel Muiño
>
>

--
Abel Muiño

Report message to a moderator