[
https://jira.jboss.org/jira/browse/JBIDE-3770?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-3770:
------------------------------------
I asked some jboss guys under any circumstances would *anyone* need to modify the run.sh
classpath.
I was told repeatedly the answer is no. In order to add jars to classpaths the user should
put hte jar in a lib folder or a deploy folder properly. Simply adding it to the run.jar
classpath is inappropriate and not a proper use.
Because of this, it was determined the classpath was one of those launch config variables
that would be directly managed by the server. This is so that the user doesn't go
removing random things from the classpath, but also so that if the user changes the
runtime (or runtime location) we don't end up with two run.jar's on the classpath.
If a valid use case can be presented to me for modifying the classpath to launch the
config rather than using the proper methods (lib / deploy folder etc) then I can try to
come up with a more intelligent way to make sure we don't end up with two competing
run.jars on the classpath.
can not edit server runtime classpath
-------------------------------------
Key: JBIDE-3770
URL:
https://jira.jboss.org/jira/browse/JBIDE-3770
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.CR2
Environment: windows eclipse 3.4.1
Reporter: filippo rossoni
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.0.0.GA
when edit the server runtime configuration the changes are lost after save
--
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