September 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-557) "No artifacts found" shown erroneously when artifact type suggestion is clicked

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-557?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-557. ------------------------------- Fix Version/s: 0.6.0 Resolution: Done > "No artifacts found" shown erroneously when artifact type suggestion is clicked > ------------------------------------------------------------------------------- > > Key: SRAMP-557 > URL: https://issues.jboss.org/browse/SRAMP-557 > Project: S-RAMP > Issue Type: Bug > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Minor > Fix For: 0.6.0 > > > In the UI, upload an xsd. Then, on the left, search for the "XsdDocumen" type (leave off the "t"), then click the suggestion. The display shows results, but also shows "No artifacts found." in addition. Logic off? Note that this *only* happens when the suggestion is clicked. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-557) "No artifacts found" shown erroneously when artifact type suggestion is clicked

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-557?page=com.atlassian.jira.plugin.... ] Work on SRAMP-557 started by Brett Meyer. ----------------------------------------- > "No artifacts found" shown erroneously when artifact type suggestion is clicked > ------------------------------------------------------------------------------- > > Key: SRAMP-557 > URL: https://issues.jboss.org/browse/SRAMP-557 > Project: S-RAMP > Issue Type: Bug > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Minor > > In the UI, upload an xsd. Then, on the left, search for the "XsdDocumen" type (leave off the "t"), then click the suggestion. The display shows results, but also shows "No artifacts found." in addition. Logic off? Note that this *only* happens when the suggestion is clicked. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-525) Release plugin not changing the artifact versions

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-525?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-525. ----------------------------- Resolution: Out of Date Closing -- not worth the time to investigate. release.sh doesn't even use the plugin > Release plugin not changing the artifact versions > ------------------------------------------------- > > Key: SRAMP-525 > URL: https://issues.jboss.org/browse/SRAMP-525 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > The release plugin doesn't appear to be changing the artifact versions. All POMs have the same SNAPSHOT version, even after correctly setting the release version with the release.sh script. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (OVERLORD-145) Re-write the home page's "What is Overlord?"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-145?page=com.atlassian.jira.plug... ] Brett Meyer commented on OVERLORD-145: -------------------------------------- [~eric.wittmann], [~objectiser], any ideas on this one? > Re-write the home page's "What is Overlord?" > -------------------------------------------- > > Key: OVERLORD-145 > URL: https://issues.jboss.org/browse/OVERLORD-145 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > "What is Overlord?" is old and could be better utilized. Re-write -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (OVERLORD-145) Re-write the home page's "What is Overlord?"

by Brett Meyer (JIRA)

Brett Meyer created OVERLORD-145: ------------------------------------ Summary: Re-write the home page's "What is Overlord?" Key: OVERLORD-145 URL: https://issues.jboss.org/browse/OVERLORD-145 Project: Overlord Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer "What is Overlord?" is old and could be better utilized. Re-write -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (OVERLORD-137) Ensure cached OSGi services are removed when service bundle uninstalled

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-137?page=com.atlassian.jira.plug... ] Gary Brown updated OVERLORD-137: -------------------------------- Fix Version/s: Overlord-Commons-2.0.10.Final (was: Overlord-Commons-2.0.8.Final) > Ensure cached OSGi services are removed when service bundle uninstalled > ----------------------------------------------------------------------- > > Key: OVERLORD-137 > URL: https://issues.jboss.org/browse/OVERLORD-137 > Project: Overlord > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.10.Final > > > When services are retrieved using the getServices or getSingleService method on the ServiceRegistry(Util), they are cached for more efficient subsequent access. > The ServiceListener mechanism enables a client to be notified when services implementing a particular interface are registered or unregistered. > Either use a direct OSGi service listener, or the ServiceRegistry ServiceListener, to determine when the cached services should be removed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (OVERLORD-138) Tests for OSGiServiceRegistry

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-138?page=com.atlassian.jira.plug... ] Gary Brown updated OVERLORD-138: -------------------------------- Fix Version/s: Overlord-Commons-2.0.10.Final (was: Overlord-Commons-2.0.8.Final) > Tests for OSGiServiceRegistry > ----------------------------- > > Key: OVERLORD-138 > URL: https://issues.jboss.org/browse/OVERLORD-138 > Project: Overlord > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.10.Final > > > Provide unit or integration tests to ensure OSGi services accessed via 'get' or service listener approach are correctly initialized and closed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-561) Support Fuse JMS

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-561?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-561: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/484, https://github.com/Governance/overlord-commons/pull/106 (was: https://github.com/Governance/s-ramp/pull/484) > Support Fuse JMS > ---------------- > > Key: SRAMP-561 > URL: https://issues.jboss.org/browse/SRAMP-561 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > SRAMP-433 created JMS events within S-RAMP. For Tomcat, Jetty, and standalone EAP, we use an embedded ActiveMQ broker. For standalone-full EAP, we re-use the existing HornetQ JMS and JNDI resources. > Supposedly, Fuse provides ActiveMQ out-of-the-box. We should re-use that, rather than relying on the embedded broker. Investigate and figure out a way to add the JMS resources during S-RAMP installation, similar to the new configureJMS-jboss-eap-6.xslt. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-457) S-ramp installer error when installing over an existing server instance

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-457?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-457. ----------------------------- Resolution: Rejected According to David, this was opened in error. Closing. > S-ramp installer error when installing over an existing server instance > ----------------------------------------------------------------------- > > Key: SRAMP-457 > URL: https://issues.jboss.org/browse/SRAMP-457 > Project: S-RAMP > Issue Type: Bug > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Error in the s-ramp distro assembly for jboss eap: > > > > It happens when it is installed over a not clean jboss server instance: > > Steps: > > Unzip Jboss eap 6.3 Alpha > > Install switchyard over eap > > execute the ant s-ramp-distro assembly build > > If you run now jboss eap it will work. > > Install again s-ramp in jboss eap then causes the following error: > https://gist.github.com/dvirgiln/b2f5f80234c97fc2b3b1 > The overlord-commons installer will get skipped if run multiple times, > but it does this by looking for the keystore. If it finds the keystore > it assumes that it's already been run and skips itself. > Nothing like this exists for s-ramp. So it will make all the > standalone.xml changes (using XSLT) each time you run it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[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 commented on SRAMP-409: ----------------------------------- Leaving this open. But, based on discussions, deferring. It's an admirable thought, but has quite a few implications that need thoroughly addressed. > 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.1#6329)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2014