[
http://jira.codehaus.org/browse/MPECLIPSE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92641
]
Gary Mohr commented on MPECLIPSE-130:
-------------------------------------
Actually the plugin that I am building is creating projects that use Maven2 to
control their build lifecycle. The projects currently "Enable" Maven for the
created projects by adding the Maven nature and creating a Maven classpath
container that is added to the projects classpath.
The current implementation of my plugin prespecifies each project dependency in
the created "pom.xml" files. This approach sort of works for now but it is a
requirement to be able to programatically create these dependencies as the
project content is populated.
I have found classes in the Maven Eclipse plugin that seem ready to do this
work for me but because of the packaging they are awkward to use.
This is my current need but I expect there will be additional reasons why I
will need access to the Maven Eclipse plugin classes as we try to further
integrate the work we are doing with the Eclipse plugin you are providing.
> Eclipse plugin to provide maven integration not packaged so it can be reused
> by other Eclipse plugins.
> ------------------------------------------------------------------------------------------------------
>
> Key: MPECLIPSE-130
> URL: http://jira.codehaus.org/browse/MPECLIPSE-130
> Project: maven-eclipse-plugin
> Issue Type: Bug
> Affects Versions: 1.10
> 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
