July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-490) Remove version overrides for plugins (inherit from jboss-parent)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-490?page=com.atlassian.jira.plugin.... ] Work on SRAMP-490 started by Brett Meyer. > Remove version overrides for plugins (inherit from jboss-parent) > ---------------------------------------------------------------- > > Key: SRAMP-490 > URL: https://issues.jboss.org/browse/SRAMP-490 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0 > > > In some cases we are overriding the versions of plugins in various projects (overlord-commons, s-ramp, dtgov). > We should remove any version overrides unless they are actually necessary. I don't know of any required overrides, so I think they can all be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer edited comment on SRAMP-433 at 7/2/14 12:20 AM: ------------------------------------------------------------ Thinking through all the use cases for the queues. Thoughts on the following? - configured in sramp.properties via a list of JNDI names - disabled by default - dtgov-specific queue automatically created on the s-ramp installation target, but the JNDI name must be "enabled" (added to the list) during dtgov installation - allow clients to create additional queues on the JMS platform and list them on the config prop - each event is published to all configured queues w/ no expiration time was (Author: brmeyer): Thinking through all the use cases for the queues. Thoughts on the following? - configured in s-ramp properties file via JNDI names - disabled by default - dtgov-specific queue must be enabled during dtgov installation (or programmatically) - allow clients to create additional queues on the JMS platform and list them on the config prop - each event is sent to all registered queues w/ no expiration time > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer edited comment on SRAMP-433 at 7/2/14 12:16 AM: ------------------------------------------------------------ Thinking through all the use cases for the queues. Thoughts on the following? - configured in s-ramp properties file via JNDI names - disabled by default - dtgov-specific queue must be enabled during dtgov installation (or programmatically) - allow clients to create additional queues on the JMS platform and list them on the config prop - each event is sent to all registered queues w/ no expiration time was (Author: brmeyer): Thinking through all the use cases for the queues. Thoughts on the following? - configured in s-ramp properties file - disabled by default - dtgov-specific queue must be enabled during dtgov installation (or programmatically) - allow clients to create additional queues on the JMS platform and list them on the config prop - each event is sent to all registered queues w/ no expiration time > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- Thinking through all the use cases for the queues. Thoughts on the following? - configured in s-ramp properties file - disabled by default - dtgov-specific queue must be enabled during dtgov installation (or programmatically) - allow clients to create additional queues on the JMS platform and list them on the config prop - each event is sent to all registered queues w/ no expiration time > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-433: ------------------------------ Git Pull Request: (was: https://github.com/Governance/s-ramp/pull/448) > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-486) s-ramp.sh should not require JAVA_HOME to be set

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-486?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-486: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/448 > s-ramp.sh should not require JAVA_HOME to be set > ------------------------------------------------ > > Key: SRAMP-486 > URL: https://issues.jboss.org/browse/SRAMP-486 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 > > > s-ramp.sh is the only FSW script that requires JAVA_HOME to be set. As RHEL installations by default do not set it, the requirement should be relaxed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-433: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/448 > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-486) s-ramp.sh should not require JAVA_HOME to be set

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-486?page=com.atlassian.jira.plugin.... ] Work on SRAMP-486 started by Brett Meyer. > s-ramp.sh should not require JAVA_HOME to be set > ------------------------------------------------ > > Key: SRAMP-486 > URL: https://issues.jboss.org/browse/SRAMP-486 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 > > > s-ramp.sh is the only FSW script that requires JAVA_HOME to be set. As RHEL installations by default do not set it, the requirement should be relaxed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- I'll continue to fix up the general approach. Maybe it would be best to have you guys help me come up with a POJO-first approach for the event model. I'll just use RESTEasy JAXB annotations -- iirc, that can be serialized to both JSON and XML. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-491) Support EAP 6.2

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-491: --------------------------------- Summary: Support EAP 6.2 Key: SRAMP-491 URL: https://issues.jboss.org/browse/SRAMP-491 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 0.5.0 ModeShape's new distro supposedly supports both EAP 6.2 and 6.3. 6.2 *should* work without many changes in S-RAMP. Hopefully an additional XSLT section is it... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2014