February 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-143) ModeShape should persist between restarts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-143?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-143. --------------------------- set purge=false in the modeshape file-store > ModeShape should persist between restarts > ----------------------------------------- > > Key: SRAMP-143 > URL: https://issues.jboss.org/browse/SRAMP-143 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: Milestone 3 (Workflow and Relationships) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > The ModeShape service is not persisting data between restarts, iow it must be in memory at the moment. I thought it was set to files on disk but apparently not so.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-143) ModeShape should persist between restarts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-143?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-143. ----------------------------- Resolution: Done > ModeShape should persist between restarts > ----------------------------------------- > > Key: SRAMP-143 > URL: https://issues.jboss.org/browse/SRAMP-143 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: Milestone 3 (Workflow and Relationships) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > The ModeShape service is not persisting data between restarts, iow it must be in memory at the moment. I thought it was set to files on disk but apparently not so.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-143) ModeShape should persist between restarts

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-143?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-143: ---------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/179 > ModeShape should persist between restarts > ----------------------------------------- > > Key: SRAMP-143 > URL: https://issues.jboss.org/browse/SRAMP-143 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: Milestone 3 (Workflow and Relationships) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > The ModeShape service is not persisting data between restarts, iow it must be in memory at the moment. I thought it was set to files on disk but apparently not so.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-117) Add caching of ontologies to JCR persistence layer

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-117?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-117: ---------------------------- Priority: Minor (was: Major) > 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 > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: Milestone 4 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-127) review modules and package structures

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-127?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-127. --------------------------- > review modules and package structures > ------------------------------------- > > Key: SRAMP-127 > URL: https://issues.jboss.org/browse/SRAMP-127 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > I find it hard to find classes at the moment, we should review what we have and map package names to module names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-127) review modules and package structures

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-127?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-127. ----------------------------- Resolution: Done Done, Eric performed a refactoring for m3. > review modules and package structures > ------------------------------------- > > Key: SRAMP-127 > URL: https://issues.jboss.org/browse/SRAMP-127 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > I find it hard to find classes at the moment, we should review what we have and map package names to module names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-136) Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-136?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-136. --------------------------- > Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate > -------------------------------------------------------------------- > > Key: SRAMP-136 > URL: https://issues.jboss.org/browse/SRAMP-136 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Kurt Stam > Fix For: Milestone 4 > > > The S-RAMP spec is changing the name of the UserDefinedArtifactType. We need to go through our code to mirror that change, once we make the adjustment to the schema/generated java code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-136) Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-136?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-136. ----------------------------- Resolution: Done > Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate > -------------------------------------------------------------------- > > Key: SRAMP-136 > URL: https://issues.jboss.org/browse/SRAMP-136 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Kurt Stam > Fix For: Milestone 4 > > > The S-RAMP spec is changing the name of the UserDefinedArtifactType. We need to go through our code to mirror that change, once we make the adjustment to the schema/generated java code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-136) Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-136?page=com.atlassian.jira.plugin.... ] Kurt Stam reassigned SRAMP-136: ------------------------------- Assignee: Kurt Stam (was: Eric Wittmann) > Rename "UserDefinedArtifact" to "ExtendedArtifact" where appropriate > -------------------------------------------------------------------- > > Key: SRAMP-136 > URL: https://issues.jboss.org/browse/SRAMP-136 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Kurt Stam > Fix For: Milestone 4 > > > The S-RAMP spec is changing the name of the UserDefinedArtifactType. We need to go through our code to mirror that change, once we make the adjustment to the schema/generated java code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-138) Upgrade the SimpleReleaseProcess

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-138?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-138. --------------------------- > Upgrade the SimpleReleaseProcess > -------------------------------- > > Key: SRAMP-138 > URL: https://issues.jboss.org/browse/SRAMP-138 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Governance > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: Milestone 4 > > > So it includes a notification after deployment, with a url to the taskform to approve the smoke test. Then a notification afterwards to display the status text the SmokeTester put in OK/FAIL. > Later we can make a more complex/realistic workflow, but this at least shows off the capabilities. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2013