[ http://jira.codehaus.org/browse/MNGECLIPSE-85?page=comments#action_60241
]
Eugene Kuleshov commented on MNGECLIPSE-85:
-------------------------------------------
I'd organize view like this:
project1
+--- pom1
+--- launch config1
+--- launch config2
+--- launch config3
+--- launch config4
+--- pom2
+--- launch config1
+--- launch config2
....
Basically it would look similar to Spring beans view from Spring IDE, but show
poms instead of config files.
You could also set a default launch configuration that would be launched when
clicking on project of pom node.
> 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]
