maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phillip Merensky (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MECLIPSE-489) [PATCH] New list-plugin goal which outputs all eclipse osgi bundles within a plugins directory as maven dependencies.
Date Wed, 17 Sep 2008 13:12:48 GMT
[PATCH] New list-plugin goal which outputs all eclipse osgi bundles within a plugins directory
as maven dependencies.
---------------------------------------------------------------------------------------------------------------------

                 Key: MECLIPSE-489
                 URL: http://jira.codehaus.org/browse/MECLIPSE-489
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Improvement
          Components: OSGi, Manifest
    Affects Versions: 2.5.1
            Reporter: Phillip Merensky


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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message