[jira] Closed: (MPECLIPSE-8) Support shared Eclipse launch configurations

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: David Eric Pugh
       Date: Tue, 19 Oct 2004 8:00 AM

Over a year old, time to close it!
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPECLIPSE-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPECLIPSE-8
    Summary: Support shared Eclipse launch configurations
       Type: New Feature

     Status: Closed
   Priority: Minor
 Resolution: INCOMPLETE

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-eclipse-plugin
   Fix Fors:
             1.9

   Assignee: David Eric Pugh
   Reporter: Charlie Dobbie

    Created: Mon, 6 Oct 2003 7:34 AM
    Updated: Tue, 19 Oct 2004 8:00 AM
Environment: All

Description:
I think it would be useful to be able to execute shared Eclipse launch configurations from Maven.  An example launch configuration may look like this (Eclipse 2.1.1):

<?xml version="1.0" encoding="UTF-8"?>
<launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication">
    <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="mypackage.MyClassName"/>
    <stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="MyProjectName"/>
    <listAttribute key="org.eclipse.debug.ui.favoriteGroups">
        <listEntry value="org.eclipse.debug.ui.launchGroup.run"/>
    </listAttribute>
    <stringAttribute key="org.eclipse.debug.ui.target_debug_perspective" value="perspective_default"/>
    <stringAttribute key="org.eclipse.debug.ui.target_run_perspective" value="perspective_default"/>
    <stringAttribute key="org.eclipse.debug.core.source_locator_id" value="org.eclipse.jdt.debug.ui.javaSourceLocator"/>
</launchConfiguration>

I believe Eclipse locates shared launch configurations by searching the project's tree for *.launch files.  (Local configurations reside in the .metadata tree, but are out of scope of this request.)

I am not sure how best to expose this functionality to the Maven system.  Perhaps a plugin-eclipse goal would read the class to run from a property, so it could be invoked by one of:

  <j:set var="maven.eclipse.launchConfiguration" value="com.company.Main"/>
  <j:attainGoal name="eclipse:execute-launch-configuration"/>

or:

  maven -Dmaven.eclipse.launchConfiguration=com.company.Main eclipse:execute-launch-configuration

Or maybe the eclipse-plugin goal would process the launch files and add them to the project's maven.xml as <java> tasks, so the goal is a one-shot setup task, much like the other plugin-eclipse goals.

I welcome any and all comments on this feature request - thoughts on implementation, usefulness or even whether or not it's a good idea!


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org