[
https://jira.jboss.org/jira/browse/JBDS-1001?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen commented on JBDS-1001:
-------------------------------------------
The behavior you describe is already what we do today (try run the installer ;)
The users does not have to select the type and version - we recognize it for them.
They are only there in case users try and install servers that we might not be able to
recognize correctly.
EWP is not available to us so not happening, EWS we can look into after CR1.
But If you find there are servers we do not recognize (and we should) then open separate
issues for them.
Need to integrate new ESB and SOA-P runtimes into JBDS installer
----------------------------------------------------------------
Key: JBDS-1001
URL:
https://jira.jboss.org/jira/browse/JBDS-1001
Project: JBoss Developer Studio
Issue Type: Bug
Components: installer
Affects Versions: 3.0.0.CR2
Reporter: Brian Fitzpatrick
Assignee: Denis Golovin
Fix For: 3.0.0.CR2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
For the JBDS installer, we have the ability to install additional servers such as EAP 4,
EAP 5, SOA-P 4 and EPP 4 and plain JBoss AS. We should add the ability to install the
SOA-P 5 runtime and possibly the ESB server (4.7).
How do we go about doing that? Need to look at the latest JBDS build
(
http://reports.qa.atl.jboss.com/binaries/RHDS/builds/nightly/3.0.0.RC1/20...) and
try to install it to see what, if anything is missing.
--
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