|
Re: pluginManagement, extensions versioning issue [message #21140 is a reply to message #21123] |
Mon, 19 January 2009 16:58 |
Eclipse User |
|
|
|
Originally posted by: igor.ifedorenko.com
What jetty version are you building (svn url)? I want try it locally to
see what is going on.
--
Regards,
Igor
Jesse McConnell wrote:
>
> Jetty uses the o.a.felix:maven-bundle-plugin for getting the osgi
> manifests in order but lately with the m2e plugin I am getting the
> following error for about 20 or so sub-projects (each module declaring
> the plugin).
>
>
> Project build error:Cannot resolve pre-scanned plugin artifact (for use
> as an extension): org.apache.felix:maven-bundle-plugin: Failed to
> resolve extension plugin:
> org.apache.felix:maven-bundle-plugin:maven-plugin:RELEASE pom.xml
> jetty line 1 Maven Problem
>
>
> The top level project file declares the version (1.4.0) in the
> pluginManagement section but that doesn't seem to matter. There are
> some relativePath statements that might be a factor, and then the plugin
> declaration also includes <extension>true</extension>
>
> thoughts?
>
> jesse
|
|
|
|
Re: pluginManagement, extensions versioning issue [message #21173 is a reply to message #21123] |
Fri, 23 January 2009 06:47 |
Eclipse User |
|
|
|
Originally posted by: lists.remove-me.varnes.remove-me.net
* Jesse McConnell wrote, On 20/01/09 03:21:
>
> Jetty uses the o.a.felix:maven-bundle-plugin for getting the osgi
> manifests in order but lately with the m2e plugin I am getting the
> following error for about 20 or so sub-projects (each module declaring
> the plugin).
>
>
> Project build error:Cannot resolve pre-scanned plugin artifact (for use
> as an extension): org.apache.felix:maven-bundle-plugin: Failed to
> resolve extension plugin:
> org.apache.felix:maven-bundle-plugin:maven-plugin:RELEASE pom.xml
> jetty line 1 Maven Problem
>
>
> The top level project file declares the version (1.4.0) in the
> pluginManagement section but that doesn't seem to matter. There are
> some relativePath statements that might be a factor, and then the plugin
> declaration also includes <extension>true</extension>
>
> thoughts?
>
> jesse
I can confirm this as well. If the version of the bundle plugin is
inherited from a parent <pluginManagement>, this problem occurs.
Specifying the version locally is a (unpalatable) work-around.
I have been thinking it is because the bundle plugin is declared
as an extension ?
thanks
davidv
|
|
|
|
Re: pluginManagement, extensions versioning issue [message #21699 is a reply to message #21186] |
Sun, 08 February 2009 04:23 |
Eclipse User |
|
|
|
Originally posted by: lists.remove-me.varnes.remove-me.net
* Jesse McConnell wrote, On 24/01/09 07:10:
>> david varnes wrote:
>> I can confirm this as well. If the version of the bundle plugin is
>> inherited from a parent <pluginManagement>, this problem occurs.
>>
>> Specifying the version locally is a (unpalatable) work-around.
>>
>> I have been thinking it is because the bundle plugin is declared
>> as an extension ?
>
> Agreed, that was my suspicion..
>
>> thanks
>> davidv
A search of JIRA brings up quite a few issues with extension related
origins. I am sure the response will be to see if the issues go away
with the merge of an updated 3.x embedder.
In the meantime, responding to Jason's call for voting on issues,
the following issue seems to match our case, you may consider
voting:
http://jira.codehaus.org/browse/MNGECLIPSE-487
regards
davidv
|
|
|
Powered by
FUDForum. Page generated in 0.04225 seconds