[JBoss JIRA] Created: (JBDS-748) Modifying JDK version from "Open Launch Configuration" is misleading
6:40 a.m.
Modifying JDK version from "Open Launch Configuration" is misleading
--------------------------------------------------------------------
Key: JBDS-748
URL: https://jira.jboss.org/jira/browse/JBDS-748
Project: Developer Studio
Issue Type: Feature Request
Components: servers
Affects Versions: 2.0.0.GA
Reporter: Stelios Koussouris
Priority: Minor
From the IDE in the Open Launch Configuration you are be able to
modify details related to the JDK but not the JDK itself. This is in order for the launch
configurations not to go out of sync (ie. you are allowed to add, not modify things you
already setup). The fact that when closing the "Open Launch Configuration" the
changes of JDK is maintained (ie. showing different from the one in the "Runtime
Environment") can be misleading since the server will start with the JDK set in
"Runtime Environment".
--
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
9:12 a.m.
New subject: [JBoss JIRA] Moved: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading
[
https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen moved JBDS-748 to JBIDE-4410:
-------------------------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio)
Key: JBIDE-4410 (was: JBDS-748)
Component/s: JBossAS
(was: servers)
Affects Version/s: 3.0.0.GA
(was: 2.0.0.GA)
Modifying JDK version from "Open Launch Configuration" is
misleading
--------------------------------------------------------------------
Key: JBIDE-4410
URL: https://jira.jboss.org/jira/browse/JBIDE-4410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Priority: Minor
From the IDE in the Open Launch Configuration you are be able to modify details related
to the JDK but not the JDK itself. This is in order for the launch configurations not to
go out of sync (ie. you are allowed to add, not modify things you already setup). The fact
that when closing the "Open Launch Configuration" the changes of JDK is
maintained (ie. showing different from the one in the "Runtime Environment") can
be misleading since the server will start with the JDK set in "Runtime
Environment".
--
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
11:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading
[
https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plu...
]
Stelios Koussouris commented on JBIDE-4410:
-------------------------------------------
Open Server View Perspective
Right click on a server
Open
In the "Overview" choose "Open Launch Configuration" and then modify
the JDK and as follows from the description above to recreate it
Modifying JDK version from "Open Launch Configuration" is
misleading
--------------------------------------------------------------------
Key: JBIDE-4410
URL: https://jira.jboss.org/jira/browse/JBIDE-4410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Priority: Minor
From the IDE in the Open Launch Configuration you are be able to modify details related
to the JDK but not the JDK itself. This is in order for the launch configurations not to
go out of sync (ie. you are allowed to add, not modify things you already setup). The fact
that when closing the "Open Launch Configuration" the changes of JDK is
maintained (ie. showing different from the one in the "Runtime Environment") can
be misleading since the server will start with the JDK set in "Runtime
Environment".
--
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
2:06 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading
[
https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-4410:
---------------------------------------
Fix Version/s: 3.1.0.M3
Assignee: Rob Stryker
Rob - was thinking about this issue the other day. Couldn't this be "fixed"
by adding validation in the configuration tabs we use and simply check if the user changed
something that we know will be changed/wrong/fixed/overwritten based on runtime ?
Modifying JDK version from "Open Launch Configuration" is
misleading
--------------------------------------------------------------------
Key: JBIDE-4410
URL: https://jira.jboss.org/jira/browse/JBIDE-4410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.1.0.M3
From the IDE in the Open Launch Configuration you are be able to modify details related
to the JDK but not the JDK itself. This is in order for the launch configurations not to
go out of sync (ie. you are allowed to add, not modify things you already setup). The fact
that when closing the "Open Launch Configuration" the changes of JDK is
maintained (ie. showing different from the one in the "Runtime Environment") can
be misleading since the server will start with the JDK set in "Runtime
Environment".
--
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
6:22 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading
[
https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-4410:
------------------------------------
It's really a lot of work to go extending all the individual tabs and trying to sneak
validation in. I had tried that route in the past and I ended up having to copy several
classes entirely because of private methods / variables etc. In the end I opted to use the
cleaner version we see now which silently overwrites invalid changes.
Modifying JDK version from "Open Launch Configuration" is
misleading
--------------------------------------------------------------------
Key: JBIDE-4410
URL: https://jira.jboss.org/jira/browse/JBIDE-4410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.1.0.M3
From the IDE in the Open Launch Configuration you are be able to modify details related
to the JDK but not the JDK itself. This is in order for the launch configurations not to
go out of sync (ie. you are allowed to add, not modify things you already setup). The fact
that when closing the "Open Launch Configuration" the changes of JDK is
maintained (ie. showing different from the one in the "Runtime Environment") can
be misleading since the server will start with the JDK set in "Runtime
Environment".
--
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
6:26 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading
[
https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4410:
--------------------------------------------
Shouldn't be that hard nor require any private references.
new CommonTab() {
validate() {
x = super.validate();
if x!=null return x;
else
// check our constraints in the stored properties which all has *public* names
// if problem found return info or set warning.
}
Modifying JDK version from "Open Launch Configuration" is
misleading
--------------------------------------------------------------------
Key: JBIDE-4410
URL: https://jira.jboss.org/jira/browse/JBIDE-4410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.1.0.M3
From the IDE in the Open Launch Configuration you are be able to modify details related
to the JDK but not the JDK itself. This is in order for the launch configurations not to
go out of sync (ie. you are allowed to add, not modify things you already setup). The fact
that when closing the "Open Launch Configuration" the changes of JDK is
maintained (ie. showing different from the one in the "Runtime Environment") can
be misleading since the server will start with the JDK set in "Runtime
Environment".
--
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
7:13 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4410) Modifying JDK version from "Open Launch Configuration" is misleading
[
https://jira.jboss.org/jira/browse/JBIDE-4410?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4410.
--------------------------------
Fix Version/s: 3.0.2.GA
Resolution: Done
Fixed in branch and trunk.
For now, the fix is the same as all my fixes are: this selection has been added to the
list of overrides when setting up the launch configuration rather than just in the launch.
If at any point we think the validation is the right way to go and extend all of the
various tabs in the launch config, I'd suggest a new jira be most appropriate for
that.
Modifying JDK version from "Open Launch Configuration" is
misleading
--------------------------------------------------------------------
Key: JBIDE-4410
URL: https://jira.jboss.org/jira/browse/JBIDE-4410
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.GA
Reporter: Stelios Koussouris
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.0.2.GA, 3.1.0.M3
From the IDE in the Open Launch Configuration you are be able to modify details related
to the JDK but not the JDK itself. This is in order for the launch configurations not to
go out of sync (ie. you are allowed to add, not modify things you already setup). The fact
that when closing the "Open Launch Configuration" the changes of JDK is
maintained (ie. showing different from the one in the "Runtime Environment") can
be misleading since the server will start with the JDK set in "Runtime
Environment".
--
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
6138
days inactive
6154
days old
jbosstools-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Rob Stryker (JIRA)
-
Stelios Koussouris (JIRA)