[
https://issues.jboss.org/browse/SRAMP-447?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-447:
-----------------------------------
Instead of splitting the installers back up, I'm wondering if we could do something
simpler/smarter. At least with respect to S-RAMP, really the only *runtime* difference
between EAP 6.1 and 6.3 was the ModeShape distro that the installer pulls down.
Everything else, including compile time, IDP, etc. can stay the same.
Knowing that, could we attempt to simply decide, during the installation, what ModeShape
distro to grab, based on the EAP instance's full path (assuming it's not renamed
and still contains the version within the dir name)? If that fails, fall back on the
latest?
Theoretically, that *should* allow S-RAMP to simultaneously support both, but not
splitting up the installers in overlord, overlord-commons, and s-ramp.
[~eric.wittmann]/[~objectiser], thoughts?
Re-split the installer into EAP 6.1 and 6.3
-------------------------------------------
Key: SRAMP-447
URL:
https://issues.jboss.org/browse/SRAMP-447
Project: S-RAMP
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 0.5.0.Final
SRAMP-382 combined EAP 6.1 and 6.3 support. For the most part, that's fine -- no
compile issues, etc. However, the installer needs split back up in order to provide the
correct ModeShape distro, etc.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)