[
https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin....
]
David virgil naranjo commented on SRAMP-450:
--------------------------------------------
Ok, gary, Going to do the following:
- Place the keystore in the s-ramp-profile. Set the sramp-ui.properties with the default
keystore references and properties.
About the note you mentioned at the end of your message, I do not think it would affect
that different overlord-subprojects are being installed sharing overlord-commons. We need
to think fuse fabric profiles, like adding features to the container. If we add the
overlord-commons-profile features to the same container multiple times, the result is
gonna be the same, because the features related the profile would be only added once.
S-ramp installer && S-ramp-distro add fabric as a new target
------------------------------------------------------------
Key: SRAMP-450
URL:
https://issues.jboss.org/browse/SRAMP-450
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly.
The Fabric deployment needs to unzip the overlord-commons.profile zip and the
s-ramp-profile.zip inside the fabric installation.
The question is, what to do with the keystore and the references to the keystore from the
sramp-ui.properties?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)