[
http://jira.codehaus.org/browse/MECLIPSE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl moved MPECLIPSE-130 to MECLIPSE-254:
--------------------------------------------------
Affects Version/s: (was: 1.10)
Workflow: Maven New (was: jira)
Key: MECLIPSE-254 (was: MPECLIPSE-130)
Project: Maven 2.x Eclipse Plugin (was: maven-eclipse-plugin)
> Eclipse plugin to provide maven integration not packaged so it can be reused
> by other Eclipse plugins.
> ------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-254
> URL: http://jira.codehaus.org/browse/MECLIPSE-254
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Environment: MS Windows XP running Eclipse321/Wtp151 all in one
> package using a Sun Java 1.5 sdk.
> Reporter: Gary Mohr
>
> The Eclipse plugin that provides maven integration is installed into Eclipse
> as an unpacked Jar file. This top level Jar file does not contain the class
> files which provide the maven functionallity, instead they are found in the
> "m2plugin.jar" runtime library found in this top level Jar file.
> This means that if I am developing my own Eclipse plugin, it is not possible
> to simply list the maven plugin (org.maven.ide.eclipse) as a dependency in my
> plugin and then gain access to the classes delivered with the maven plugin.
> In order to use the classes delivered in the maven plugin I am required to
> extract the runtime library "m2plugin.jar" and put a copy of it in my
> plugin's "lib" directory then add it to my plugin's classpath.
> Somehow it seems ironic that Maven the champion of not having to manually
> replicate Jar files within projects would leave me in this situation.
> Please provide me an easier way to write Eclipse plugins that utilize the
> services delivered with the Maven Eclipse plugin.
> If for instance the Maven Eclipse plugin were unpacked when it is installed
> into Eclipse, then I should be able to add the "m2plugin.jar" to my plugin's
> classpath without the need to replicate it. As a different approach if the
> class files from the 3 runtime libraries delivered in the plugin Jar file
> were found in the plugin Jar file instead of buried inside the runtime
> library, then Eclipse would be able to reference these classes when I list
> the Maven Eclipse plugin as a dependency of my plugin.
> I am sorry if the project this was submitted to is not the correct project.
> From its name it is kinda of hard to tell if it represents the Maven plugin
> to support Eclipse stuff or the Eclipse plugin to support Maven stuff.
--
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
