[
https://jira.jboss.org/jira/browse/JBIDE-5742?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-5742:
-------------------------------
Attachment: JBIDE-5742.patch
This is the patch I've come up with. Each jboss server type has a default execution
environment which is honored in the wizard and in the launch.
It *should* also be honored when right-clicking the server and seeing whether start / stop
are enabled, however I've discovered some bugs upstream in WTP that prevent that from
happening. So for now we make do and just error as soon as we can on a bad launch.
I encourage testing on this ASAP.
Add the notion of execution environments to servers and runtimes
----------------------------------------------------------------
Key: JBIDE-5742
URL:
https://jira.jboss.org/jira/browse/JBIDE-5742
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.1.0.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.1.0.CR2
Attachments: JBIDE-5742.patch
Each jboss runtime has a specific execution environment associated with it. Some JBoss
versions require more than others. Using execution environments might even be able to help
clean up a few dirty classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira