[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=comments#action_60204 ]
Thorsten Kamann commented on MNGECLIPSE-85: ------------------------------------------- In the view there aren't pom files. I know only the name of the goal to execute and the IProject the goal belongs to. The ISelection points to the goal and not to the pom file. Therefore i thought the most flexible way were the externalizing of the launcher to allow other views and action to reuse an specialized launcher based on the IMavenLauncher. regards Thorsten > MavenLauncher should be externalized > ------------------------------------ > > Key: MNGECLIPSE-85 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-85 > Project: Maven 2.x Extension for Eclipse > Type: Improvement > Components: Maven Launcher > Versions: 0.0.5 > Reporter: Thorsten Kamann > Assignee: Eugene Kuleshov > Attachments: AbstractMavenLauncher.java, DefaultMavenLauncher.java, > ExecutePomAction.java.patch, IMavenLauncher.java, launcher.patch > > > The MavenLauncher is included in the ExecutePomAction. To allow other views > to use this launcher I want to extract the code in a seperate class. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
