[JBoss JIRA] (ARTIF-582) Create Maven Facade unit/integration test
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-582?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-582:
------------------------------
Fix Version/s: 1.0.0.Alpha1
> Create Maven Facade unit/integration test
> -----------------------------------------
>
> Key: ARTIF-582
> URL: https://issues.jboss.org/browse/ARTIF-582
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Priority: Critical
> Fix For: 1.0.0.Alpha1
>
>
> This should be the priority and done before any other sub-task. Create extensive unit/integration tests to provide adequate coverage of all Maven Facade functionality. Due to the Facade's potential complexity, it should be developed with a test-first approach.
> See SrampWagonTest for some inspiration. Some of it may be directly applicable.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-582) Create Maven Facade unit/integration test
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-582?page=com.atlassian.jira.plugin.... ]
Brett Meyer reassigned ARTIF-582:
---------------------------------
Assignee: Brett Meyer
> Create Maven Facade unit/integration test
> -----------------------------------------
>
> Key: ARTIF-582
> URL: https://issues.jboss.org/browse/ARTIF-582
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Priority: Critical
> Fix For: 1.0.0.Alpha1
>
>
> This should be the priority and done before any other sub-task. Create extensive unit/integration tests to provide adequate coverage of all Maven Facade functionality. Due to the Facade's potential complexity, it should be developed with a test-first approach.
> See SrampWagonTest for some inspiration. Some of it may be directly applicable.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-583) Consider completely removing the web-view support in the Maven Facade
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-583?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-583:
------------------------------
Fix Version/s: 1.0.0.Alpha1
> Consider completely removing the web-view support in the Maven Facade
> ---------------------------------------------------------------------
>
> Key: ARTIF-583
> URL: https://issues.jboss.org/browse/ARTIF-583
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> 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.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-583) Consider completely removing the web-view support in the Maven Facade
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-583?page=com.atlassian.jira.plugin.... ]
Brett Meyer reassigned ARTIF-583:
---------------------------------
Assignee: Brett Meyer
> Consider completely removing the web-view support in the Maven Facade
> ---------------------------------------------------------------------
>
> Key: ARTIF-583
> URL: https://issues.jboss.org/browse/ARTIF-583
> Project: Artificer
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> 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.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-604) Show relationships targeting the current artifact in the UI
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-604?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-604:
------------------------------
Fix Version/s: 1.0.0.Alpha1
> Show relationships targeting the current artifact in the UI
> -----------------------------------------------------------
>
> Key: ARTIF-604
> URL: https://issues.jboss.org/browse/ARTIF-604
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> Great idea from [~eric.wittmann] on an email thread:
> {quote}
> I also think there is room in the UI for some way to show all artifacts
> that point to the current artifact by a specific relationship. So
> perhaps an editable drop-down control allowing the user to select a
> common relationship or type their own, which would result in this query:
> /s-ramp/<model>/<type>[<relationship>[@uuid = <uuid>]]
> The <model>, <type>, and <uuid> values come from the currently selected
> artifact. The <relationship> comes from the dropdown. Populate a table
> with the results!
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months