[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-699) Re-use of saved launch configurations is not working.

[Gail Nagle (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-699?page=all ]

Gail Nagle updated JBIDE-699:
-----------------------------

    Attachment: JBOSS_AS_40.launch

This is an example of the launch file that is produced by the JBOSS_AS server and is used to start the JBOSS server inside Eclispe. It would be nice if this were shareable and reuseable after the import of the Server Project into a workspace. Currently it is not and has to be recreated in each workspace by every team member. Not very efficient. Also, when things change, every member of the team must be notified to make the change instead of simply doing an svn update and getting what is needed.

> Re-use of saved launch configurations is not working.
> -----------------------------------------------------
>
>                 Key: JBIDE-699
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-699
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.0.0.Beta2
>         Environment: Redhat Linux, Eclipse and JBOSS AS package Downloaded as JBossIDE-2.0.0.Beta2-Bundle-linux-gtk.tar
>            Reporter: Gail Nagle
>         Assigned To: Rob Stryker
>         Attachments: JBOSS_AS_40.launch
>
>
> There is a fair amount of effort required to create a launch configuration. 
> In particular, a long list of external jars often must be added.
> The clear intention of the JBOSS AS IDE is to be able to save, share and generally re-use these configurations.
> Sharing is further supported by the use of VARIABLE macros in the path of the jars.
> The IDE adds a project to the Eclipse workspace and the launch configuration is also saved to a file
> When attempting to re-use the configuration, the IDE detects the existence of these files since it will not allow the creation of a second configuration with the same name. BUT IT WILL NOT RUN THE EXISTING CONFIGURATION.
> This issue was resolved previously in an earlier version of Eclipse:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=12898
> I recently reported it on http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg17939.html and worked with IBM engineers in Canada to determine that the issue exists in the JBOSS IDE plugin, not in Eclipse itself.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira