[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3073) Changing home location does not take effect for deploy/launch
[
https://jira.jboss.org/jira/browse/JBIDE-3073?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-3073:
------------------------------------
For QA:
1) have two jboss 4.2.2.GA (or any specific version) installations
2) Make a runtime / server combo out of installation 1
3) click "open launch configuration", verify arguments include
"--configuration=default" and vmargs include
-Djava.endorsed.dirs="/home/rob/apps/jboss/jboss-4.2.2.GA/lib/endorsed" (or
something similar)
4) Double click server, click "runtime environment", modify runtime location to
second install, change configuration to "all", press finish
5) DO NOT SAVE. Click "open launch configuration"
6) verify command line arguments now say "--configuration=all" and vmargs
include
-Djava.endorsed.dirs="/home/rob/apps/jboss/jboss-4.2.2.GA_INSTALLATION2/lib/endorsed"
(or something similar)
Changing home location does not take effect for deploy/launch
-------------------------------------------------------------
Key: JBIDE-3073
URL: https://jira.jboss.org/jira/browse/JBIDE-3073
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.0.0.CR2
We cannot do another release where the servers are created with hardcoded full paths
instead of relative to the runtime.
If we interpret the directories as relative (i.e. new File(runtime.getDir(),
server.getDir())) then it will even be fully backwards compatible (at least on windows)
--
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