July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-539) Change pom.xml version property format to "version.x.y.x"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/RTGOV-539?page=com.atlassian.jira.plugin.... ] Work on RTGOV-539 started by Brett Meyer. > Change pom.xml version property format to "version.x.y.x" > --------------------------------------------------------- > > Key: RTGOV-539 > URL: https://issues.jboss.org/browse/RTGOV-539 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 2.0.0.Final > > > Currently we use x.y.z.version in the overlord projects. > We need to change this in all Overlord projects, not just S-RAMP. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-539) Change pom.xml version property format to "version.x.y.x"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/RTGOV-539?page=com.atlassian.jira.plugin.... ] Brett Meyer reassigned RTGOV-539: --------------------------------- Assignee: Brett Meyer (was: Gary Brown) > Change pom.xml version property format to "version.x.y.x" > --------------------------------------------------------- > > Key: RTGOV-539 > URL: https://issues.jboss.org/browse/RTGOV-539 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 2.0.0.Final > > > Currently we use x.y.z.version in the overlord projects. > We need to change this in all Overlord projects, not just S-RAMP. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-519) Change pom.xml version property format to "version.x.y.x"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-519?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-519. ------------------------------- Resolution: Done > Change pom.xml version property format to "version.x.y.x" > --------------------------------------------------------- > > Key: SRAMP-519 > URL: https://issues.jboss.org/browse/SRAMP-519 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > Currently we use x.y.z.version in the overlord projects. > We need to change this in all Overlord projects, not just S-RAMP. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-532) Create RTGov artifact types and expander

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-532?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-532. ------------------------------- Resolution: Done > Create RTGov artifact types and expander > ---------------------------------------- > > Key: SRAMP-532 > URL: https://issues.jboss.org/browse/SRAMP-532 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > RTGov deployable artifacts can be created as jars (for OSGi) and wars (for JEE). > There are four types of artifact, identified by a JSON file in their root: > Event Processor Network - epn.json > Activity Validator - av.json > Information Processor - ip.json > Active Collection Source - acs.json > If each of these types can have a classification. > Additionally, as part of the RTGov tooling work, a templating approach is likely to be used to help create instances of these deployable artifacts from parameterised versions. These templated instances would need to be classified differently. To identify a templated approach, a "-template.json" name will be used, e.g. the Event Processor Network template would be "epn-template.json". > So if each of these file names could be used to classify the templated versions. > Therefore 8 classifications in total should be catered for. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-380) Passwords in clear text when running in Fuse 6.1

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-380?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-380: --------------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/94, https://github.com/Governance/s-ramp/pull/466, https://github.com/Governance/overlord-commons/pull/96, https://github.com/Governance/dtgov/pull/214 (was: https://github.com/Governance/overlord-commons/pull/94, https://github.com/Governance/s-ramp/pull/466) > Passwords in clear text when running in Fuse 6.1 > ------------------------------------------------ > > Key: SRAMP-380 > URL: https://issues.jboss.org/browse/SRAMP-380 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > When we install into JBoss EAP we make sure that we don't have any clear text passwords in any configuration files. This is made possible by using the Vault, which allows us to store passwords in the vault and then refer to those vault locations from our config files. > I don't know if there is something similar to be done in Fuse 6.1 > In addition, the login credentials for supported users in EAP are not stored in clear text (the EAP Application Realm config files store an encrypted version of the passwords). > In Fuse 6.1 we are storing the login user credentials in a users.properties file in clear text. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-380) Passwords in clear text when running in Fuse 6.1

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-380?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-380: --------------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/94, https://github.com/Governance/s-ramp/pull/466 (was: https://github.com/Governance/overlord-commons/pull/94) > Passwords in clear text when running in Fuse 6.1 > ------------------------------------------------ > > Key: SRAMP-380 > URL: https://issues.jboss.org/browse/SRAMP-380 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > When we install into JBoss EAP we make sure that we don't have any clear text passwords in any configuration files. This is made possible by using the Vault, which allows us to store passwords in the vault and then refer to those vault locations from our config files. > I don't know if there is something similar to be done in Fuse 6.1 > In addition, the login credentials for supported users in EAP are not stored in clear text (the EAP Application Realm config files store an encrypted version of the passwords). > In Fuse 6.1 we are storing the login user credentials in a users.properties file in clear text. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-534) Content assist in S-RAMP shell not working well for maven command

by Stefan Bunciak (JIRA)

Stefan Bunciak created SRAMP-534: ------------------------------------ Summary: Content assist in S-RAMP shell not working well for maven command Key: SRAMP-534 URL: https://issues.jboss.org/browse/SRAMP-534 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Shell Affects Versions: 0.5.0.Beta3 Reporter: Stefan Bunciak Assignee: Brett Meyer Priority: Minor Content assist/command completion in S-RAMP shell did not provide me with possible commands for 'maven' namespace. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-532) Create RTGov artifact types and expander

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-532?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-532: ----------------------------------- The initial artifact types and expander are complete. Note that I'm not currently deriving anything specific from the json. We could eventually look into defining new relationships, etc. Also note that this should currently be used from the Maven *wagon*, not the facade. > Create RTGov artifact types and expander > ---------------------------------------- > > Key: SRAMP-532 > URL: https://issues.jboss.org/browse/SRAMP-532 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > RTGov deployable artifacts can be created as jars (for OSGi) and wars (for JEE). > There are four types of artifact, identified by a JSON file in their root: > Event Processor Network - epn.json > Activity Validator - av.json > Information Processor - ip.json > Active Collection Source - acs.json > If each of these types can have a classification. > Additionally, as part of the RTGov tooling work, a templating approach is likely to be used to help create instances of these deployable artifacts from parameterised versions. These templated instances would need to be classified differently. To identify a templated approach, a "-template.json" name will be used, e.g. the Event Processor Network template would be "epn-template.json". > So if each of these file names could be used to classify the templated versions. > Therefore 8 classifications in total should be catered for. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-532) Create RTGov artifact types and expander

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-532?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-532: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/465 > Create RTGov artifact types and expander > ---------------------------------------- > > Key: SRAMP-532 > URL: https://issues.jboss.org/browse/SRAMP-532 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > RTGov deployable artifacts can be created as jars (for OSGi) and wars (for JEE). > There are four types of artifact, identified by a JSON file in their root: > Event Processor Network - epn.json > Activity Validator - av.json > Information Processor - ip.json > Active Collection Source - acs.json > If each of these types can have a classification. > Additionally, as part of the RTGov tooling work, a templating approach is likely to be used to help create instances of these deployable artifacts from parameterised versions. These templated instances would need to be classified differently. To identify a templated approach, a "-template.json" name will be used, e.g. the Event Processor Network template would be "epn-template.json". > So if each of these file names could be used to classify the templated versions. > Therefore 8 classifications in total should be catered for. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-532) Create RTGov artifact types and expander

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-532?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-532: ------------------------------ Summary: Create RTGov artifact types and expander (was: Tag RTGov deployable artifacts with appropriate type) > Create RTGov artifact types and expander > ---------------------------------------- > > Key: SRAMP-532 > URL: https://issues.jboss.org/browse/SRAMP-532 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > RTGov deployable artifacts can be created as jars (for OSGi) and wars (for JEE). > There are four types of artifact, identified by a JSON file in their root: > Event Processor Network - epn.json > Activity Validator - av.json > Information Processor - ip.json > Active Collection Source - acs.json > If each of these types can have a classification. > Additionally, as part of the RTGov tooling work, a templating approach is likely to be used to help create instances of these deployable artifacts from parameterised versions. These templated instances would need to be classified differently. To identify a templated approach, a "-template.json" name will be used, e.g. the Event Processor Network template would be "epn-template.json". > So if each of these file names could be used to classify the templated versions. > Therefore 8 classifications in total should be catered for. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 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