[JBoss JIRA] Created: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
4:56 a.m.
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
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
4:58 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Vlado Pakan updated JBDS-1658:
------------------------------
Attachment: editServerRuntimeEnvironmentDialogWarning.png
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
Attachments: editServerRuntimeEnvironmentDialogWarning.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
8:16 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1658:
--------------------------------------
Fix Version/s: 4.1.0.CR1
Priority: Critical (was: Major)
Assignee: Denis Golovin
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
8:16 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1658:
-------------------------------------------
Vlado - is this in the installer or only the runtime detection ?
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
9:14 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1658:
-------------------------------------
This is runtime detection
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
9:20 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1658:
--------------------------------
Component/s: runtime
(was: installer)
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
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.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
9:24 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1658:
--------------------------------
Assignee: Snjezana Peco (was: Denis Golovin)
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
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: Snjezana Peco
Priority: Critical
Fix For: 4.1.0.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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:45 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Snjezana Peco resolved JBDS-1658.
---------------------------------
Release Notes Text: Fixed within JBIDE-8918.
Resolution: Done
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
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: Snjezana Peco
Priority: Critical
Fix For: 4.1.0.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
3:47 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1658:
-------------------------------------------
done via JBIDE-8918 (from Snjeza on #jbosstools)
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
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: Snjezana Peco
Priority: Critical
Fix For: 4.1.0.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
5:41 a.m.
New subject: [JBoss JIRA] Reopened: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Martin Malina reopened JBDS-1658:
---------------------------------
This issue is still present.
I just verified the scenario on
jbdevstudio-product-macosx-cocoa-4.1.0.v201105312352R-H528-CR1.jar .
Note that I added the soa standalone 4.3 location during installation. After starting
JBDS, I saw exactly the same warning as in the screenshot from Vlado.
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
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: Snjezana Peco
Priority: Critical
Fix For: 4.1.0.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
5:43 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Martin Malina commented on JBDS-1658:
-------------------------------------
If you use the runtime detection in jbds preferences, it works fine. The problem only
occurs if you add the server location during installation.
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
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: Snjezana Peco
Priority: Critical
Fix For: 4.1.0.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
6:37 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Snjezana Peco updated JBDS-1658:
--------------------------------
Assignee: Denis Golovin (was: Snjezana Peco)
Component/s: installer
(was: runtime)
This is a installer issue.
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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.CR1
Attachments: editServerRuntimeEnvironmentDialogWarning.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
9:02 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1658:
--------------------------------------
Fix Version/s: 4.1.0.CR2
(was: 4.1.0.CR1)
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
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:33 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin commented on JBDS-1658:
-------------------------------------
Verified on last build published for QA which is 4.1.0.v201107051610R-H628-CR2
works for me now
!screenshot81.png!
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
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:33 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1658:
--------------------------------
Attachment: screenshot81.png
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
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:35 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin edited comment on JBDS-1658 at 7/6/11 7:35 PM:
-------------------------------------------------------------
Verified on last build published for QA which is 4.1.0.v201107051610R-H628-CR2
works for me now.
Adding standalone SOA 4.3.0 in installer looks like this:
!screenshot81.png!
After start it appears in Servers View
!screenshot82.png!
was (Author: dgolovin):
Verified on last build published for QA which is 4.1.0.v201107051610R-H628-CR2
works for me now
!screenshot81.png!
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
6:35 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin updated JBDS-1658:
--------------------------------
Attachment: screenshot82.png
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
6:37 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Denis Golovin resolved JBDS-1658.
---------------------------------
Resolution: Done
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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
3:07 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Jiri Peterka reassigned JBDS-1658:
----------------------------------
Assignee: Pavol Srna (was: Denis Golovin)
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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: Pavol Srna
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
8:29 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Pavol Srna commented on JBDS-1658:
----------------------------------
Verified on jbdevstudio-product-eap-linux-gtk-4.1.0.v201107071833R-H630-CR2.
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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: Pavol Srna
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
8:29 a.m.
New subject: [JBoss JIRA] Closed: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
[
https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin....
]
Pavol Srna closed JBDS-1658.
----------------------------
SOA-P 4.3.0 standalone is not properly added to Server Runtimes after
installation.
-----------------------------------------------------------------------------------
Key: JBDS-1658
URL: https://issues.jboss.org/browse/JBDS-1658
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: Pavol Srna
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
5380
days inactive
5443
days old
jbosstools-issues@lists.jboss.org
20 comments
7 participants
participants (7)
-
Denis Golovin (JIRA) -
Jiri Peterka (JIRA)
-
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Pavol Srna (JIRA)
-
Snjezana Peco (JIRA)
-
Vlado Pakan (JIRA)