[ http://jira.codehaus.org/browse/MNGECLIPSE-130?page=comments#action_67112 ]
Philip Dodds commented on MNGECLIPSE-130: ----------------------------------------- Actual the use cases extend beyond a simple archetype, though I do see your point about placing that inside Mavens code. Really the aim was to reuse the Console and the M2 embedded integration with that, since I want to be able to a run Maven 2 goals from an Eclipse plugin and have it log to the M2 Console etc, also reusing the prefences (ie. local repo/logging). > Extending the Maven Plugin to allow reuse from other plugins > ------------------------------------------------------------ > > Key: MNGECLIPSE-130 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-130 > Project: Maven 2.x Extension for Eclipse > Type: New Feature > Versions: 0.0.9 > Environment: Eclipse 3.1 > Reporter: Philip Dodds > Assignee: Eugene Kuleshov > Attachments: newMethod.patch > > > I am currently working to build out some tooling around the ServiceMix/FUSE > platform and I have been successful at integrating the Maven2 Eclipse Plugin > to allow the re-use of the archetype plugin in Eclipse (ie. a wizard using > the archetype under the hood) and also the working with using the JBI plugins > to enable integration with publishing to servers. > In order to maximise reuse I wanted to leverage the Maven 2 Eclipse Plugin to > provide access to the MavenEmbedded infrastructure, however it required some > changes to the plugin to provide access from other plugins and to give a > clean simple interface. > Can you review the attached patch for the Maven 2 plugin that offers the > required functionality > Thanks -- 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
