[jira] [Closed] (MECLIPSE-489) [PATCH] New list-plugin goal which outputs all eclipse osgi bundles within a plugins directory as maven dependencies.

["Robert Scholte (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MECLIPSE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MECLIPSE-489.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

The Apache Maven team has decided to retire the maven-eclipse-plugin, so this issue won't be fixed. 


> [PATCH] New list-plugin goal which outputs all eclipse osgi bundles within a plugins directory as maven dependencies.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-489
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-489
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: Improvement
>          Components: OSGi, Manifest
>    Affects Versions: 2.5.1
>            Reporter: Phillip Merensky
>            Assignee: Robert Scholte
>         Attachments: MECLIPSE-489_maven-eclipse-plugin-2.5.1_list-plugins.patch
>
>
> When using maven for the creation of an eclipse distribution there is the to-maven goal to install all plugins of an eclipse directory into your local or remote repository. However when you want to create a new eclipse distribution it may be necessary to build your distribution on a bunch of eclipse osgi bundles which are not directly referenced by your plugins and thus can not be included directlly via install-plugins. If you want to include these basic eclipse distribution plugins into a pom file it could be lot of manual work.
> That is why I created a new Mojo (EclipseListPluginsMojo) based upon the EclipseToMavenMojo which outputs all plugins within an eclipse directory as maven dependencies. After that the list can be added to your distribution pom via copy paste easily.
> Test cases etc. are not needed in my opinion because the functionality is really simple and bugs can easily be discovered within the output. If an artifact was not listed correctly it will produce a traceable error in your "distribution pom" later.
> At the moment I merely copied the EclipseToMavenMojo cleaned it up and added only minor changes to provide this functionality. That is why I think duplicate methods in these two mojos are defensible in favor of less changes to the whole plugin. In the future it might be better to build an util class, an abstract super class or something similar.
> I hope this is useful to someone. At least it is for me.
> Suggestions are welcome.
> Regards,
> Phillip



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)