[
https://jira.codehaus.org/browse/MECLIPSE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-602.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> OSGI Spec allow multiple versions of the same plugin within an installtion.
> to-maven mojo cannot deal with situations like that
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-602
> URL: https://jira.codehaus.org/browse/MECLIPSE-602
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: PDE support
> Affects Versions: 2.7
> Reporter: Hasan Ceylan
> Priority: Critical
> Attachments: multiple-versions.patch
>
>
> I have noticed this when I was working on the issue:
> http://jira.codehaus.org/browse/MECLIPSE-601
> It looks like that if you have multiple versions of the same plugin, only one
> of them can be installed as the plugins and models maps are used with the
> groupId.artifactId as the key.
> So a subsequent version of the same plugin will replace the previous one
> leading to the last-one-wins situation.
> This might look an innocent bug however image you have two set of plugins in
> your installation. Then you will end up a randomly -picked list of a single
> entry list of the plugins in your repository that can possibly lead to
> unwanted version chaos. Furthermore this situation can be missed easily and
> can cause a big headache to the experiencing person.
> Attached path resolves the issue...
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
