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

[Gail Nagle (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-699?page=comments#action_12374838 ] 
            
Gail Nagle commented on JBIDE-699:
----------------------------------

I apologize for not seeing that I needed to attach my documentation to this page.
I am new to JIRA. I have added the additional documentation you requested.
To summarize, the problem is that my team needs to be able to share JBOSS AS launch configurations.

It takes a lot of time to set these up. We are working on individual VMs and need to be able to store these in svn so others can use them.

The main issue is that we need to be able to use variables to specify the path to various external jars that are needed by JBOSS to run our applications. 

The interesting thing is that after importing the Server project, the launcher plugin "sees" the existing launch since it will not let you create a new server of the same name. But IT WILL NOT RUN THE EXISTING LAUNCH config from the imported server.

 The attachments show screen shots that demonstrate the problem. It takes multiple steps so if you need further clarification, you can call me today between 1:30 and 5:30 PST and I would be glad to explain the problem further. 858-675-1922.

I hope this helps. 

 

Please do not close this as it is vital to our use the plugin.



> 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-Launch-Config-Reuse-Problem-ScreenShots.doc, 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