[
https://jira.jboss.org/jira/browse/JBDS-455?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBDS-455:
------------------------------------------
#1 I was suggesting the simple mapping to have the simplest thing that just works. If we
can use the jboss-system.jar file to locate it then that is good.
#2 Okey - just remember AS does not have same structure as EAP and SOA-P (they have one
extra level of dirs)
#3 Okey
#4 Okey
#5 Okey
#6 Sounds good
#1 yes, I would just put a warning saying something does not match. And even if you find
something to init from then users should be allowed to adjust the settings.
#2 Could you give me an example ? I.e. I would say that if JBoss 5.2 came out after us we
shold still allow it to be installed since it most likely would work with the server
adapter for 5.0
Common versions for all types (JBoss AS, EAP and SOA-P) when select
already installed AP while installation.
------------------------------------------------------------------------------------------------------------
Key: JBDS-455
URL:
https://jira.jboss.org/jira/browse/JBDS-455
Project: Developer Studio
Issue Type: Bug
Components: installer
Affects Versions: 2.0.0.beta1
Reporter: Anton Klimkovich
Assignee: Denis Golovin
Priority: Blocker
Fix For: 2.0.0.cr1
Attachments: Install_Server_Version.PNG
EXECUTE: On step 5 of installation select "No? I already have it installed "
checkbox
EXECUTE: Select any Type (JBoss AS, EAP and SOA-P)
EXECUTE: Select Version
FAILURE: Common versions for all types.
--
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