[JBoss JIRA] (ARTIF-625) Support Target#otherAttributes
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-625?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-625.
-----------------------------
> Support Target#otherAttributes
> ------------------------------
>
> Key: ARTIF-625
> URL: https://issues.jboss.org/browse/ARTIF-625
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> Target is currently mapped directly on the sramp:relationship node type, through the following:
> {code}
> - sramp:targetType (string) multiple
> - sramp:relationshipTarget (weakreference) multiple < 'sramp:baseArtifactType'
> {code}
> Instead, that needs pulled out into a separate sramp:target type. Then, also include the following, necessary for Target#otherAttributes:
> {code}
> - * (string)
> - * (string) multiple
> {code}
> Add support for storing Target#otherAttributes in the visitors. See Relationship#otherAttributes and SRAMP-622.
> This needs to wait till 1.0 as it's a breaking change in the CND.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-554) Improve the UI search capabilities and query syntax support
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-554?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-554.
-----------------------------
> Improve the UI search capabilities and query syntax support
> -----------------------------------------------------------
>
> Key: ARTIF-554
> URL: https://issues.jboss.org/browse/ARTIF-554
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Priority: Critical
> Fix For: 1.0.0.Alpha1
>
>
> Ideas:
> - Completely replace the top "Search" bar with a field explicitly for S-RAMP queries.
> - When left sidebar search is used, automatically add the equivalent query in the new bar.
> - Include a link to the S-RAMP query docs.
> - Add "name" and "uuid" fields to the search sidebar.
> - Also on the sidebar, differentiate between search fields that are encompassed by the query language and ones that extend it (literally use a linebreak, etc.).
> This would gain us both more powerful search capabilities, as well as "teaching" users the query language as they go.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-615.
-----------------------------
> S-RAMP performance enhancements
> -------------------------------
>
> Key: ARTIF-615
> URL: https://issues.jboss.org/browse/ARTIF-615
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of:
> - logical artifact uploads
> - document artifact uploads (including derivation and extraction)
> - artifact updates
> - artifact content updates
> - artifact deletes
> - queries
> Minor fixes will be committed under this ticket. More complex issues will be sub-tasks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (ARTIF-509) Unify s-ramp maven code
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-509?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-509.
-----------------------------
> Unify s-ramp maven code
> -----------------------
>
> Key: ARTIF-509
> URL: https://issues.jboss.org/browse/ARTIF-509
> Project: Artificer
> Issue Type: Sub-task
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
> Fix For: 1.0.0.Alpha1
>
>
> Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system.
> They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different mojos.
> This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType.
> Also it is required a MavenUtil class where will be included the common operations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months