[jbosstools-issues] [JBoss JIRA] (JBIDE-12089) LaunchConfiguration can be edited, but will be lost because of deferred delete

[Koen Aers (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698527#comment-12698527 ] 

Koen Aers commented on JBIDE-12089:
-----------------------------------

This was indeed the last step that I mentioned earlier. Another advantage is that we can give the user complete control over the environment in which Forge executes: it will be possible to specify (and/or change) vm arguments and environment variables.

Not sure what the best way would be to tackle this though. Probably there are examples that show similar use cases in the execution of JBoss AS. Let's pull Max (or somebody else that knows about this) in the loop and get some more input.
                
> LaunchConfiguration can be edited, but will be lost because of deferred delete
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-12089
>                 URL: https://issues.jboss.org/browse/JBIDE-12089
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: forge
>            Reporter: Thomas Frühbeck
>            Assignee: Koen Aers
>            Priority: Minor
>              Labels: development, forge, plugin
>             Fix For: 3.3.x
>
>
> The Forge LaunchConfiguration can be changed to allow source lookup.
> Due to the fact that the name of the launch config is artificial, it will be destroyed.
> By defining a name for LauchConfiguration in the ForgePreferences we can allow for persistent configurations:
>  - a (list of) names can be defined in ForgePreferences 
>  - each LaunchConfiguration will be associated with a specific Runtime
>  - Forge development can be assisted by integrating Forge core/dist/target as Runtime
>  - development of plugins can be assisted be integration of other project's source 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira