[JBoss JIRA] (SRAMP-521) Change pom.xml version property format to "version.x.y.x"
by Gary Brown (JIRA)
Gary Brown created SRAMP-521:
--------------------------------
Summary: Change pom.xml version property format to "version.x.y.x"
Key: SRAMP-521
URL: https://issues.jboss.org/browse/SRAMP-521
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Eric Wittmann
Fix For: 0.5.0
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, 5 months
[JBoss JIRA] (SRAMP-520) Use BOM version of guava-gwt
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-520:
-----------------------------------
Summary: Use BOM version of guava-gwt
Key: SRAMP-520
URL: https://issues.jboss.org/browse/SRAMP-520
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.5.0
We're currently overriding the version of guava-gwt in s-ramp and dtgov to 14.0.1. The BOM uses 13. I don't think we need to override it to the newer version. Need to test both s-ramp and dtgov to verify.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (SRAMP-519) Change pom.xml version property format to "version.x.y.x"
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-519:
-----------------------------------
Summary: 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: Eric Wittmann
Fix For: 0.5.0
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, 5 months
[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on SRAMP-395:
-----------------------------------------------
Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1114732|https://bugzilla.redhat.com/show_bug.cgi?id=1114732] from POST to ON_QA
> 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.Alpha1, 0.5.0
>
>
> 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.6#6264)
10 years, 5 months