[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=comments#action_60201 ]
Eugene Kuleshov commented on MNGECLIPSE-85: ------------------------------------------- This is kind of thing I am talking about. If your view would use IFile or something adaptable to IFile to represent poms, then existing launch action would be automatically contributed to its popup menu. Unless you are trying to do something else or I am missing something. Can you please describe what exactly you going to implement in that view? Otherwise it could help to see the other part of the code. > 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]
