July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-507) Modify way the snapshot artifacts are stored in s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-507?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-507. ------------------------------- Resolution: Done > Modify way the snapshot artifacts are stored in s-ramp > ------------------------------------------------------ > > Key: SRAMP-507 > URL: https://issues.jboss.org/browse/SRAMP-507 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0 > > > Include a property mvn.snapshot.timestamp (in case the name contains the timestamp) > When deploying a snapshot artifact, maven will include a timestamp in the filename. The maven repository facade *and* the s-ramp wagon should be updated to store this timestamp info in a new s-ramp property (see above). In addition, the s-ramp wagon should no longer *ever* attempt to update an artifact. Here is what it should do: > h4. Release artifacts > * If this artifact (GAV) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it > h4. Snapshot artifacts > * If this artifact (GAV + timestamp) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it along with its timestamp information -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-510) Fully audit the S-RAMP Maven structure and dependencies

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-510: --------------------------------- Summary: Fully audit the S-RAMP Maven structure and dependencies Key: SRAMP-510 URL: https://issues.jboss.org/browse/SRAMP-510 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 0.6.0 Completely audit: 1.) The project architecture, ensuring proper module structure, parents, etc. 2.) Module dependencies 3.) Parent dependencyManagement -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-509) Unify s-ramp maven code

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-509?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-509: ----------------------------------- See https://github.com/Governance/s-ramp/pull/454/files for examples > Unify s-ramp maven code > ----------------------- > > Key: SRAMP-509 > URL: https://issues.jboss.org/browse/SRAMP-509 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system. > They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different mojos. > This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType. > Also it is required a MavenUtil class where will be included the common operations. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-527) Create Service for accessing active collections from event processors

by Gary Brown (JIRA)

Gary Brown created RTGOV-527: -------------------------------- Summary: Create Service for accessing active collections from event processors Key: RTGOV-527 URL: https://issues.jboss.org/browse/RTGOV-527 Project: RTGov (Run Time Governance) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Need to be able to reference information in active collections from an event processor. So information derived from some previous processing, and stored in an active collection, can then be used in subsequent EPNs or AVs. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-505) maven:deploy CLI command missing maven.type property sometimes

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-505?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-505. ------------------------------- Resolution: Done > maven:deploy CLI command missing maven.type property sometimes > -------------------------------------------------------------- > > Key: SRAMP-505 > URL: https://issues.jboss.org/browse/SRAMP-505 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 > > > The maven:deploy s-ramp cli command does not currently set the maven.type property under all circumstances. A requirement is that maven.type always be set. Currently the CLI command gets this information from the arguments to the command. In some cases the user will not include the "type" information on the command line. In this case the type should be pulled from the file extension of the file being uploaded. > If the file being uploaded does *not* have an extension and the maven.type is not provided as part of the GAV argument, then the command should fail. > Note: the name of the artifact should also include the file's extension - this is currently being left off. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-509) Unify s-ramp maven code

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-509?page=com.atlassian.jira.plugin.... ] David virgil naranjo reassigned SRAMP-509: ------------------------------------------ Assignee: David virgil naranjo (was: Brett Meyer) > Unify s-ramp maven code > ----------------------- > > Key: SRAMP-509 > URL: https://issues.jboss.org/browse/SRAMP-509 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system. > They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different mojos. > This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType. > Also it is required a MavenUtil class where will be included the common operations. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-509) Unify s-ramp maven code

by David virgil naranjo (JIRA)

David virgil naranjo created SRAMP-509: ------------------------------------------ Summary: Unify s-ramp maven code Key: SRAMP-509 URL: https://issues.jboss.org/browse/SRAMP-509 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: Brett Meyer Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system. They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different mojos. This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType. Also it is required a MavenUtil class where will be included the common operations. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-431: ----------------------------------- Pushed to 0.6 branch > Arquillian-based integration tests > ---------------------------------- > > Key: SRAMP-431 > URL: https://issues.jboss.org/browse/SRAMP-431 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Create a new s-ramp-test module to contain all integration tests. Thoughts: > - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them. Arquillian would then use them in a "managed mode." > - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network. Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME > - Fuse should be run in embedded mode. > - No tests should run by default. Hide all behind container-specific profiles, enabled only on the CI job(s). > - Include a simple s-ramp-client based test to at least ensure the app comes up, auth works, and uploading/querying works. > - Pull in any functional tests from the other modules requiring the server to be spun-up. Leave behind only pure *unit* tests. > The work-in-progress: https://github.com/brmeyer/s-ramp/compare/integration-tests -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-431. ------------------------------- Resolution: Done > Arquillian-based integration tests > ---------------------------------- > > Key: SRAMP-431 > URL: https://issues.jboss.org/browse/SRAMP-431 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Create a new s-ramp-test module to contain all integration tests. Thoughts: > - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them. Arquillian would then use them in a "managed mode." > - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network. Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME > - Fuse should be run in embedded mode. > - No tests should run by default. Hide all behind container-specific profiles, enabled only on the CI job(s). > - Include a simple s-ramp-client based test to at least ensure the app comes up, auth works, and uploading/querying works. > - Pull in any functional tests from the other modules requiring the server to be spun-up. Leave behind only pure *unit* tests. > The work-in-progress: https://github.com/brmeyer/s-ramp/compare/integration-tests -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-486) Align deployment targets with other overlord sub-projects

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-486?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-486: ---------------------------------- Most places have been changed to reflect the target. Currently samples are still split as jbossas and karaf. As more platforms are supported, may need to rethink this. Ant script now used at top level, with the platform using consistent names for the targets. > Align deployment targets with other overlord sub-projects > --------------------------------------------------------- > > Key: RTGOV-486 > URL: https://issues.jboss.org/browse/RTGOV-486 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Change deployment targets to be consistent with other overlord sub-projects. For example, instead of jbossas, it should be eap6 (or eap61/63 if split required), and fuse61 instead of karaf - although support for Karaf will also be required. > As part of this change, change the deployment approach to use ant script at top level, instead of maven - again for consistency with sramp/dtgov. Quickstarts could still use maven, unless deployment across targets is more consistent with ant. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2014