October 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-578) Fuse Fabric commands refactoring

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-578?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-578: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/495, https://github.com/Governance/s-ramp/pull/497 (was: https://github.com/Governance/s-ramp/pull/495) > Fuse Fabric commands refactoring > -------------------------------- > > Key: SRAMP-578 > URL: https://issues.jboss.org/browse/SRAMP-578 > Project: S-RAMP > Issue Type: Enhancement > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Modify the karaf fabric command name. > Allow the deployment of s-ramp and dtgov together in the same container. > There was a problem in the profile folder. As the class was extending the AbstractConfigureFabric command, the getProfileFolder method should not overwrite the parent. There is a problem with the folder where the overlord.properties and the overlord-saml.keystore file is saved. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-167?page=com.atlassian.jira.plugin.... ] Work on SRAMP-167 started by Brett Meyer. ----------------------------------------- > Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc) > ------------------------------------------------------------------------------------- > > Key: SRAMP-167 > URL: https://issues.jboss.org/browse/SRAMP-167 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a document). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-167?page=com.atlassian.jira.plugin.... ] Brett Meyer reassigned SRAMP-167: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc) > ------------------------------------------------------------------------------------- > > Key: SRAMP-167 > URL: https://issues.jboss.org/browse/SRAMP-167 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a document). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-387) add javadoc jars to distro

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-387?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-387. ----------------------------- Fix Version/s: (was: 0.6.0) Resolution: Out of Date Out of date. Javadocs already unpacked under docs/api/javadoc > add javadoc jars to distro > --------------------------- > > Key: SRAMP-387 > URL: https://issues.jboss.org/browse/SRAMP-387 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Kurt Stam > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-533) Wire ZipToSrampArchiveProvider#getArchiveTypeHints up to the UI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-533?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-533: ----------------------------------- Superceded by SRAMP-580 > Wire ZipToSrampArchiveProvider#getArchiveTypeHints up to the UI > --------------------------------------------------------------- > > Key: SRAMP-533 > URL: https://issues.jboss.org/browse/SRAMP-533 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Uploading an artifact through the UI doesn't kick off ZipToSrampArchiveProvider#getArchiveTypeHints to go through all the integration projects and attempt to discover what to use. Make it so! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-533) Wire ZipToSrampArchiveProvider#getArchiveTypeHints up to the UI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-533?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-533. ----------------------------- Resolution: Duplicate Issue > Wire ZipToSrampArchiveProvider#getArchiveTypeHints up to the UI > --------------------------------------------------------------- > > Key: SRAMP-533 > URL: https://issues.jboss.org/browse/SRAMP-533 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Uploading an artifact through the UI doesn't kick off ZipToSrampArchiveProvider#getArchiveTypeHints to go through all the integration projects and attempt to discover what to use. Make it so! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-555) S-RAMP failing to install into Fuse

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-555?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-555. ----------------------------- Resolution: Out of Date > S-RAMP failing to install into Fuse > ----------------------------------- > > Key: SRAMP-555 > URL: https://issues.jboss.org/browse/SRAMP-555 > Project: S-RAMP > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Tried installing 0.6.0-SNAPSHOT into Fuse 6.1 and received this: > {code} > Error executing command: Could not start bundle mvn:org.sonatype.sisu/sisu-inject-bean/2.2.3 in feature(s) s-ramp-dependencies-0.6.0-SNAPSHOT: Unresolved constr > aint in bundle org.sonatype.inject [464]: Singleton conflict. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-587) Not possible to add a property with no value via S-RAMP CLI

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-587: ----------------------------------- Summary: Not possible to add a property with no value via S-RAMP CLI Key: SRAMP-587 URL: https://issues.jboss.org/browse/SRAMP-587 Project: S-RAMP Issue Type: Bug Components: Shell Affects Versions: 0.5.0.Final Reporter: Eric Wittmann Assignee: Brett Meyer The s-ramp shell cannot create a custom property on an artifact without also setting a value (even if the value is empty string). I think this should be possible with the following syntax (currently invalid): {code} s-ramp:property set foo {code} If no value is supplied then the property should be simply added without one. If the property already exists, then the value should be removed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-586) Empty custom property query not quite working

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-586: ----------------------------------- Summary: Empty custom property query not quite working Key: SRAMP-586 URL: https://issues.jboss.org/browse/SRAMP-586 Project: S-RAMP Issue Type: Bug Components: UI Affects Versions: 0.5.0.Final Reporter: Eric Wittmann Assignee: Brett Meyer If a query is done like this: {code} /s-ramp/core/Document[ @foo ] {code} then the assumption is that it should return all artifacts with property "foo" defined, regardless of the *value* of "foo". However, if an artifact has the property defined but no value for the property, this query is failing to return it. To reproduce: 1) add an artifact to s-ramp 2) add a custom property "foo" to the artifact, with no value (this can easily be done via the UI) 3) execute the s-ramp query: /s-ramp[@foo] 4) observe that the artifact is not returned -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-152) Add support for 'configfile' in generated features.xml file

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-152?page=com.atlassian.jira.plug... ] Eric Wittmann resolved OVERLORD-152. ------------------------------------ Resolution: Done Example from apiman. See "configFile" in the markup below (from the apiman-distro-fuse6-dt module's pom.xml): {code} <plugin> <groupId>org.overlord</groupId> <artifactId>overlord-commons-maven-plugin</artifactId> <version>${version.org.overlord.overlord-commons.overlord-commons-maven-plugin}</version> <executions> <execution> <phase>generate-resources</phase> <goals> <goal>generate-features-xml</goal> </goals> <configuration> <outputFile>${project.build.directory}/features.xml</outputFile> <attach>true</attach> <features>  <feature> <name>apiman-dependencies</name> <version>${project.version}</version> <comment>All API Management Dependencies</comment> <dependsOnFeatures> <feature> <name>war</name> </feature> </dependsOnFeatures> <excludes> <exclude>org.overlord.apiman:apiman-*:*</exclude> </excludes> </feature>  <feature> <name>apiman-dt</name> <version>${project.version}</version> <comment>API Management Runtime</comment> <dependsOnFeatures> <feature> <name>apiman-dependencies</name> <version>${project.version}</version> </feature> </dependsOnFeatures> <configFiles> <configFile> <finalName>/etc/apiman-dt.cfg</finalName> <value>mvn:org.overlord.apiman/apiman-distro-fuse6-dt/${project.version}/cfg</value> </configFile> </configFiles> <includes> <include>org.overlord.apiman:apiman-*:*</include> </includes> </feature> </features> </configuration> </execution> </executions> </plugin> {code} > Add support for 'configfile' in generated features.xml file > ----------------------------------------------------------- > > Key: OVERLORD-152 > URL: https://issues.jboss.org/browse/OVERLORD-152 > Project: Overlord > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Overlord-Commons-2.0.11.Final > > > Add the ability to include configfile elements in the generated features.xml file created by the overlord-commons maven plugin. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2014