[JBoss JIRA] (SRAMP-390) Installer should just use major version for supported platforms
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-390?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed SRAMP-390.
-----------------------------
Resolution: Out of Date
> Installer should just use major version for supported platforms
> ---------------------------------------------------------------
>
> Key: SRAMP-390
> URL: https://issues.jboss.org/browse/SRAMP-390
> Project: S-RAMP
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Eric Wittmann
>
> This issue affects overlord-commons, sramp and dtgov.
> Currently jetty8 and tomcat7 are supported platforms, however the redhat platforms (eap and fuse) use a major/minor version number. This means that a new distribution would be required for each minor version release of these platforms.
> Would prefer if just the major version number was used, and the installer for that major version cater for any differences that may occur through the minor versions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-409) Overlord commons Messages
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-409?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed SRAMP-409.
-----------------------------
Resolution: Won't Fix
> Overlord commons Messages
> -------------------------
>
> Key: SRAMP-409
> URL: https://issues.jboss.org/browse/SRAMP-409
> Project: S-RAMP
> Issue Type: Feature Request
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
> Priority: Minor
>
> Create a new project in Overlord-commons called overlord-commons-messages.
> Then use this Messages abstraction in S-ramp and dtgov. In case necessary, in these projects extends the CommonMessages functionality and customize it.
> Also add the overlord-commons-messages to the project overlord-commons-ant and use it.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-252) Implement common overlord config file to share properties across all overlord projects
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-252?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed SRAMP-252.
-----------------------------
Resolution: Out of Date
> Implement common overlord config file to share properties across all overlord projects
> --------------------------------------------------------------------------------------
>
> Key: SRAMP-252
> URL: https://issues.jboss.org/browse/SRAMP-252
> Project: S-RAMP
> Issue Type: Task
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
>
> Since all overlord apps leverage the overlord-commons-config code to load configuration, it should be easy to add support for a common "overlord.properties" file in standalone/configuration.
> This overlord.properties file should have any common overlord properties, which could then be used in specific project configuration.
> The obvious first use-case is the governance server's port #. The port # could then be used in all the other configs, making it easy to port-offset your jboss server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-117) Add caching of ontologies to JCR persistence layer
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-117?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-117:
-----------------------------------
[~eric.wittmann], do you still think this is necessary, since we're using ModeShape's query indexing?
> Add caching of ontologies to JCR persistence layer
> --------------------------------------------------
>
> Key: SRAMP-117
> URL: https://issues.jboss.org/browse/SRAMP-117
> Project: S-RAMP
> Issue Type: Task
> Components: Persistence
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Priority: Minor
>
> The getOntologies method should return a cached version of the ontologies rather than reading the JCR nodes each time. The cache should be invalidated when ontology nodes are changed. This can be done by hooking into the JCR eventing feature. The eventing feature of JCR may or may not be supported by the JCR impl - so only cache if eventing is available.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-620) Deprecate Fuse and Jetty support
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-620:
---------------------------------
Summary: Deprecate Fuse and Jetty support
Key: SRAMP-620
URL: https://issues.jboss.org/browse/SRAMP-620
Project: S-RAMP
Issue Type: Task
Reporter: Brett Meyer
Assignee: Brett Meyer
For now, deprecate all Fuse and Jetty support. Leave the modules be, but remove them from the project POM. Also comment out applicable sections in the doc and website.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month