[
https://issues.jboss.org/browse/SRAMP-583?page=com.atlassian.jira.plugin....
]
David virgil naranjo commented on SRAMP-583:
--------------------------------------------
I think is good to have a maven tree view depending on trhe complex situations we can
reach to.
I thought the current implementation was complete and it displayed the artifacts included
in a group and listed correctly the groups. What are the key areas that are being missed?
And what are the complex situations maybe we have to deal in the future? Just for my
understanding. I imagine the artifact grouping could be one situation.
Just as the user view, I think having a view like this is useful. As this url will be
added as maven repository, I like the idea of having access to the artifacts.
What would be good also, is to have a kind of tree organized view in s-ramp.
Consider completely removing the web-view support in the Maven
Facade
---------------------------------------------------------------------
Key: SRAMP-583
URL:
https://issues.jboss.org/browse/SRAMP-583
Project: S-RAMP
Issue Type: Sub-task
Reporter: Brett Meyer
Although I understand the initial desire to have a web-view interface for the Maven
Facade (similar to Nexus' ability to navigate the repo w/ a web browser), I think
I'd recommend removing the capability entirely. The current implementation isn't
complete and misses a few key areas. Overcoming every complex situation will be
challenging and not worth the effort.
I would much rather require the use of the real S-RAMP UI. If there are specific use
cases that the Facade view aimed for, implement them as improvements to the UI.
So, I'm advocating that we strip out the Facade view, JSPs, etc. entirely. Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)