[JBoss JIRA] Created: (JBDS-1708) CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
1:37 a.m.
CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-------------------------------------------------------------------------------------------
Key: JBDS-1708
URL: https://issues.jboss.org/browse/JBDS-1708
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 4.1.0.M1
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux
32bit, Java Sun JDK 1.6_25
Reporter: Vlado Pakan
Assignee: Denis Golovin
Priority: Critical
Fix For: 4.1.0.CR2
Attachments: editServerRuntimeEnvironmentDialogWarning.png, screenshot81.png,
screenshot82.png
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime. It's
recognized as AS v.4.3.0 and added to available runtimes during installation. But after
installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime and
therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:37 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1708) CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1708?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1708:
--------------------------------
Fix Version/s: 5.0.0.M3
(was: 4.1.0.CR2)
Description:
Cloned to verify this issues in trunk
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime. It's
recognized as AS v.4.3.0 and added to available runtimes during installation. But after
installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime and
therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
was:
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime. It's
recognized as AS v.4.3.0 and added to available runtimes during installation. But after
installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime and
therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
Affects Version/s: 5.0.0.M2
(was: 4.1.0.M1)
CLONE - SOA-P 4.3.0 standalone is not properly added to Server
Runtimes after installation.
-------------------------------------------------------------------------------------------
Key: JBDS-1708
URL: https://issues.jboss.org/browse/JBDS-1708
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux
32bit, Java Sun JDK 1.6_25
Reporter: Vlado Pakan
Assignee: Denis Golovin
Priority: Critical
Fix For: 5.0.0.M3
Attachments: editServerRuntimeEnvironmentDialogWarning.png, screenshot81.png,
screenshot82.png
Cloned to verify this issues in trunk
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime.
It's recognized as AS v.4.3.0 and added to available runtimes during installation. But
after installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime
and therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1708) CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1708?page=com.atlassian.jira.plugin....
]
Denis Golovin resolved JBDS-1708.
---------------------------------
Resolution: Out of Date
This issue is outdated because of installer now configures runtime detection instead od
adding runtimes.
CLONE - SOA-P 4.3.0 standalone is not properly added to Server
Runtimes after installation.
-------------------------------------------------------------------------------------------
Key: JBDS-1708
URL: https://issues.jboss.org/browse/JBDS-1708
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux
32bit, Java Sun JDK 1.6_25
Reporter: Vlado Pakan
Assignee: Denis Golovin
Priority: Critical
Fix For: 5.0.0.M3
Attachments: editServerRuntimeEnvironmentDialogWarning.png, screenshot81.png,
screenshot82.png
Cloned to verify this issues in trunk
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime.
It's recognized as AS v.4.3.0 and added to available runtimes during installation. But
after installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime
and therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:12 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1708) CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1708?page=com.atlassian.jira.plugin....
]
Pavol Srna commented on JBDS-1708:
----------------------------------
Verified on jbdevstudio-product-linux-gtk-5.0.0.v201109071858R-H28-M3.
CLONE - SOA-P 4.3.0 standalone is not properly added to Server
Runtimes after installation.
-------------------------------------------------------------------------------------------
Key: JBDS-1708
URL: https://issues.jboss.org/browse/JBDS-1708
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux
32bit, Java Sun JDK 1.6_25
Reporter: Vlado Pakan
Assignee: Denis Golovin
Priority: Critical
Fix For: 5.0.0.M3
Attachments: editServerRuntimeEnvironmentDialogWarning.png, screenshot81.png,
screenshot82.png
Cloned to verify this issues in trunk
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime.
It's recognized as AS v.4.3.0 and added to available runtimes during installation. But
after installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime
and therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:14 p.m.
New subject: [JBoss JIRA] Closed: (JBDS-1708) CLONE - SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1708?page=com.atlassian.jira.plugin....
]
Pavol Srna closed JBDS-1708.
----------------------------
CLONE - SOA-P 4.3.0 standalone is not properly added to Server
Runtimes after installation.
-------------------------------------------------------------------------------------------
Key: JBDS-1708
URL: https://issues.jboss.org/browse/JBDS-1708
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux
32bit, Java Sun JDK 1.6_25
Reporter: Vlado Pakan
Assignee: Denis Golovin
Priority: Critical
Fix For: 5.0.0.M3
Attachments: editServerRuntimeEnvironmentDialogWarning.png, screenshot81.png,
screenshot82.png
Cloned to verify this issues in trunk
When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime.
It's recognized as AS v.4.3.0 and added to available runtimes during installation. But
after installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime
and therefore there is a warning displayed in Edit Server Runtime Environment dialog.
When added manually via Preferences > Server Runtime > Environments > Add
it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed
in Edit Server Runtime Environment dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4676
days inactive
4740
days old
jbosstools-issues@lists.jboss.org
4 comments
2 participants
participants (2)
-
Denis Golovin (JIRA) -
Pavol Srna (JIRA)