May 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-258) Create a tomcat compatible deployment/package

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-258: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > Create a tomcat compatible deployment/package > --------------------------------------------- > > Key: SRAMP-258 > URL: https://issues.jboss.org/browse/SRAMP-258 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1. We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-395: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-382: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Add support for EAP 6.3. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-240) Modify installer to install into an existing JBoss EAP

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-240?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened SRAMP-240: ------------------------------- > Modify installer to install into an existing JBoss EAP > ------------------------------------------------------ > > Key: SRAMP-240 > URL: https://issues.jboss.org/browse/SRAMP-240 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Currently we require a zip'd up version of EAP to be available. Instead, let's install to an existing JBoss EAP. This requires users to download *and* unzip EAP 6.1, but that seems ok. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-258) Create a tomcat compatible deployment/package

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened SRAMP-258: ------------------------------- > Create a tomcat compatible deployment/package > --------------------------------------------- > > Key: SRAMP-258 > URL: https://issues.jboss.org/browse/SRAMP-258 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1. We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened SRAMP-395: ------------------------------- > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-235) New set of "maven" CLI commands

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-235?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened SRAMP-235: ------------------------------- > New set of "maven" CLI commands > ------------------------------- > > Key: SRAMP-235 > URL: https://issues.jboss.org/browse/SRAMP-235 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: IDE Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Implement some CLI commands in the "maven" namespace. At the very least, a "deploy" command is needed so that an artifact can be uploaded to s-ramp as a maven artifact. This command should set all of the same properties that the s-ramp maven wagon sets. It should also generate SHA1 and MD5 hashes. > This will also allow us to use the CLI to see the dtgov data in the s-ramp repository. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-391) ArtifactType hints should be order sensitive

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-391?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened SRAMP-391: ------------------------------- > ArtifactType hints should be order sensitive > -------------------------------------------- > > Key: SRAMP-391 > URL: https://issues.jboss.org/browse/SRAMP-391 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.5.0.Final > > > When guessing the type of zip archive the order of the types specified in the code should matter (and not be alphabetical) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-386) Add Jetty 8+ support to the installer

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-386?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened SRAMP-386: ------------------------------- > Add Jetty 8+ support to the installer > ------------------------------------- > > Key: SRAMP-386 > URL: https://issues.jboss.org/browse/SRAMP-386 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > We currently support Fuse 6.1 which uses Jetty 8 under the covers. It wouldn't be hard to add support for Jetty 8+ directly. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-384) Add validation for password in overlord commons installer

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-384?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-384: ------------------------------ Fix Version/s: 0.5.0.Alpha1 > Add validation for password in overlord commons installer > --------------------------------------------------------- > > Key: SRAMP-384 > URL: https://issues.jboss.org/browse/SRAMP-384 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0.Final, 0.5.0.Alpha1 > > > Currently the overlord commons installer is responsible for doing all security related work. This includes creating the overlord 'admin' user and configured a password for this user. The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility. This utility will fail if the password does not meet certain standards. However, the utility fails without failing the overall install. > The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen. Also note that the password input and validation should happen before anything else security related gets installed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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 May 2014