[
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)