[
https://jira.jboss.org/jira/browse/JBIDE-4346?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4346:
------------------------------------
I suppose it's one undefined-behaviour and one feature request.
Yes, it overwrites with some default because that default is related to the runtime. Often
times a user will go and change hte runtime or change the runtime's information in the
runtime wizard, and hten they complain that hte launch configuration doesn't follow
suit. So there are several variables that are directly related to the runtime.
As for why I don't consider the duplication a bug, really, is that hte user
specifically went in and added a second -Djava.library.path himself... so my code, being
told to replace the java.library.path replaced all instances with its new value. So I see
this as undefined behaviour and not necessarily a bug.
Obviously no launch configuration should have two of the args, so I guess I can ask what
is the proper syntax for setting multiple paths here?
-Djava.library.path always overwritten with some default
--------------------------------------------------------
Key: JBIDE-4346
URL:
https://jira.jboss.org/jira/browse/JBIDE-4346
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.1.GA
Environment: jboss 4.2.2.GA
eclipse:
Version: 3.4.2
Build id: M20090211-1700
Reporter: arne anka
Assignee: Rob Stryker
Fix For: 2.1.3, 3.1.0.M1
in the launch configuration for my configured jboss server i need to add another
directory to the parameter -Djava.library.path.
after editing it looks like
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native:/foo/bar/"
saving and reopening shows instead
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
adding another parameter instead
-Djava.library.path="/foo/bar"
resulting in
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
-Djava.library.path="/foo/bar"
ends up with
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
-Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native"
after saving
obviously some simple logic checks for the existence of the -Djava.library.path parameter
and overwrites it with a default instead of at least appending its default.
i don't really see what's the meaning behind that, and therefore am convinced it
has to be a bug.
additionally, it stops me from running at least one webapp, that requires the parameter
to be set correctly.
--
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