June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-477) Restructure S-RAMP server projects

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-477?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-477: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/446 > Restructure S-RAMP server projects > ---------------------------------- > > Key: SRAMP-477 > URL: https://issues.jboss.org/browse/SRAMP-477 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Restructure the s-ramp-server projects to be all together in a parent project call s-ramp-server. > The projects to be moved to this parent project are: > s-ramp-server-eap6 > s-ramp-server-fuse61 > s-ramp-server-jetty8 > s-ramp-server-tomcat7 > s-ramp-server -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-477) Restructure S-RAMP server projects

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-477?page=com.atlassian.jira.plugin.... ] Work on SRAMP-477 started by Eric Wittmann. > Restructure S-RAMP server projects > ---------------------------------- > > Key: SRAMP-477 > URL: https://issues.jboss.org/browse/SRAMP-477 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Fix For: 0.5.0.Final > > > Restructure the s-ramp-server projects to be all together in a parent project call s-ramp-server. > The projects to be moved to this parent project are: > s-ramp-server-eap6 > s-ramp-server-fuse61 > s-ramp-server-jetty8 > s-ramp-server-tomcat7 > s-ramp-server -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-506) Bulk actions should describe number of affected situations in confirmation dialog

by Gary Brown (JIRA)

Gary Brown created RTGOV-506: -------------------------------- Summary: Bulk actions should describe number of affected situations in confirmation dialog Key: RTGOV-506 URL: https://issues.jboss.org/browse/RTGOV-506 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Components: User Interface Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final The number of situations that will be affected by the bulk action should be displayed in the confirmation dialog. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-481) Maven View in S-ramp UI Artifact List

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-481?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-481: ------------------------------------- On a different note - I'm not convinced that we should be storing the maven-metadata.xml file(s) in s-ramp. Instead I think perhaps we should be generating those files upon request (GET) and ignore the upload of those files (PUT). > Maven View in S-ramp UI Artifact List > ------------------------------------- > > Key: SRAMP-481 > URL: https://issues.jboss.org/browse/SRAMP-481 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Fix For: 0.6.0 > > Attachments: s-ramp-artifacts.jpeg > > > The s-ramp artifacts view display all the artifacts by name. But it can be not intuitive when there are many artifacts with the same name. > This is the case of the maven-metadata.xml that is uploaded every time a maven artifact is deployed. > What it is proposed is to create in the upper part of the artifact's list, two checkboxes, normal view (default) and maven view. > If maven view is selected then there would be displayed the artifacts as a maven tree. > It would improve the usability, and will be more user friendly. > Take a look to the current implementation (attached file) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-481) Maven View in S-ramp UI Artifact List

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-481?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-481: ------------------------------------- I think the current UI is intended to be very generic, and certainly doesn't know about maven. I do understand and agree that the UI can be confusing when there are a lot of artifacts with the same name. I do not think the s-ramp UI will be (or should be) the primary interface for any particular use-case. This is why dtgov has specific UI pages to solve specific governance use cases. I think instead of implementing a custom UI to view the contents of the s-ramp repository as a Maven Repository, we should instead ensure that any existing maven repository browsing utilities work with the s-ramp maven repo facade. > Maven View in S-ramp UI Artifact List > ------------------------------------- > > Key: SRAMP-481 > URL: https://issues.jboss.org/browse/SRAMP-481 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Fix For: 0.6.0 > > Attachments: s-ramp-artifacts.jpeg > > > The s-ramp artifacts view display all the artifacts by name. But it can be not intuitive when there are many artifacts with the same name. > This is the case of the maven-metadata.xml that is uploaded every time a maven artifact is deployed. > What it is proposed is to create in the upper part of the artifact's list, two checkboxes, normal view (default) and maven view. > If maven view is selected then there would be displayed the artifacts as a maven tree. > It would improve the usability, and will be more user friendly. > Take a look to the current implementation (attached file) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-505) List gateway bindings in Service List, colour coded to reflect the gateway state

by Gary Brown (JIRA)

Gary Brown created RTGOV-505: -------------------------------- Summary: List gateway bindings in Service List, colour coded to reflect the gateway state Key: RTGOV-505 URL: https://issues.jboss.org/browse/RTGOV-505 Project: RTGov (Run Time Governance) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: User Interface Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Currently the 'binding' column in the service list table is empty. This needs to be populated with the gateway value(s). If multiple gateways are defined for the service, then the interface and binding values should be defined on separate lines in the single table row. The gateway state (enabled/disabled) should be reflected in the presentation (possibly colour coded). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-504) Remove 'Processing State' from RTGov UI Service List

by Gary Brown (JIRA)

Gary Brown created RTGOV-504: -------------------------------- Summary: Remove 'Processing State' from RTGov UI Service List Key: RTGOV-504 URL: https://issues.jboss.org/browse/RTGOV-504 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Components: User Interface Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-481) Maven View in S-ramp UI Artifact List

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-481?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-481: ---------------------------------- Sounds like a reasonable suggestion, although rather than 'maven view' for the tree, I think it should be more general. When I deriver extracts artifacts from an uploaded artifact, this may also create many 'artifacts' with the same name. So I think it would be good to understand what is the main artifacts, and list them at the top level of the 'tree', and any derived artifacts are scoped to the main artifact? So this would apply regardless of whether the artifact was uploaded via maven or direct. > Maven View in S-ramp UI Artifact List > ------------------------------------- > > Key: SRAMP-481 > URL: https://issues.jboss.org/browse/SRAMP-481 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Fix For: 0.6.0 > > Attachments: s-ramp-artifacts.jpeg > > > The s-ramp artifacts view display all the artifacts by name. But it can be not intuitive when there are many artifacts with the same name. > This is the case of the maven-metadata.xml that is uploaded every time a maven artifact is deployed. > What it is proposed is to create in the upper part of the artifact's list, two checkboxes, normal view (default) and maven view. > If maven view is selected then there would be displayed the artifacts as a maven tree. > It would improve the usability, and will be more user friendly. > Take a look to the current implementation (attached file) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-481) Maven View in S-ramp UI Artifact List

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-481?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-481: -------------------------------- Component/s: UI > Maven View in S-ramp UI Artifact List > ------------------------------------- > > Key: SRAMP-481 > URL: https://issues.jboss.org/browse/SRAMP-481 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Attachments: s-ramp-artifacts.jpeg > > > The s-ramp artifacts view display all the artifacts by name. But it can be not intuitive when there are many artifacts with the same name. > This is the case of the maven-metadata.xml that is uploaded every time a maven artifact is deployed. > What it is proposed is to create in the upper part of the artifact's list, two checkboxes, normal view (default) and maven view. > If maven view is selected then there would be displayed the artifacts as a maven tree. > It would improve the usability, and will be more user friendly. > Take a look to the current implementation (attached file) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-481) Maven View in S-ramp UI Artifact List

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-481?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-481: -------------------------------- Fix Version/s: 0.6.0 > Maven View in S-ramp UI Artifact List > ------------------------------------- > > Key: SRAMP-481 > URL: https://issues.jboss.org/browse/SRAMP-481 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI > Reporter: David virgil naranjo > Assignee: Eric Wittmann > Fix For: 0.6.0 > > Attachments: s-ramp-artifacts.jpeg > > > The s-ramp artifacts view display all the artifacts by name. But it can be not intuitive when there are many artifacts with the same name. > This is the case of the maven-metadata.xml that is uploaded every time a maven artifact is deployed. > What it is proposed is to create in the upper part of the artifact's list, two checkboxes, normal view (default) and maven view. > If maven view is selected then there would be displayed the artifacts as a maven tree. > It would improve the usability, and will be more user friendly. > Take a look to the current implementation (attached file) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014