[JBoss JIRA] (ARTIF-733) Improve expansion/derivation relationship lookups
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-733:
---------------------------------
Summary: Improve expansion/derivation relationship lookups
Key: ARTIF-733
URL: https://issues.jboss.org/browse/ARTIF-733
Project: Artificer
Issue Type: Enhancement
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 1.0.0.Beta3
When an expanded or derived artifact is persisted, it typically results in a slew of query-by-UUID hits on the DB, often ones that are repetitious. Instead, hold a map of UUIDs and artifacts in memory for that unit of work, reducing the lookups.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (ARTIF-732) Allow nested artifact expansion
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-732:
---------------------------------
Summary: Allow nested artifact expansion
Key: ARTIF-732
URL: https://issues.jboss.org/browse/ARTIF-732
Project: Artificer
Issue Type: Enhancement
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 1.0.0.Beta3
Ex: Upload a dist ZIP which contains two WARs. Currently, the root ZIP will be the "expandedFromArchive" target for all artifacts, even the artifacts expanded from the WARs. Instead, ArtifactServiceImpl#upload should allow nested expansion, where each level of "expandedFromArchive" relationship creates an expansion chain.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (ARTIF-499) Include another filter for Expanded (similar to Derived)
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-499?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved ARTIF-499.
-------------------------------
Resolution: Done
> Include another filter for Expanded (similar to Derived)
> --------------------------------------------------------
>
> Key: ARTIF-499
> URL: https://issues.jboss.org/browse/ARTIF-499
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 1.0.0.Beta2
>
>
> Reported by David via his 0.5.0.Beta1 testing:
> "S-ramp Artifacts --> include another column called Expanded.
> Then with this we can filter the original items (for example jars, war) from the files that are expanded from those Original Artifacts uploaded.
> I continue thinking that when there are many artifadts uploaded it is difficult to filter and have an easy understanding of the artifact result list. For example you see a file kmodule.xml, and you do not know to what artifact it belongs. You need to enter in the artifact to have this information. And when the number of artifacts in s-ramp is so big, then you see many many files, that you have no idea about them.
> If we include this expanded column and also filter field then we could have a view of the original artifacts (with no artifact parent property).
> I will prepare a html mock with my idea..."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ARTIF-499) Include another filter for Expanded (similar to Derived)
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-499?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on ARTIF-499:
-----------------------------------
Use a drop down with 4 options:
- All
- Primary (Origin)
- Primary (Expanded From Archive)
- Derived
> Include another filter for Expanded (similar to Derived)
> --------------------------------------------------------
>
> Key: ARTIF-499
> URL: https://issues.jboss.org/browse/ARTIF-499
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 1.0.0.Beta2
>
>
> Reported by David via his 0.5.0.Beta1 testing:
> "S-ramp Artifacts --> include another column called Expanded.
> Then with this we can filter the original items (for example jars, war) from the files that are expanded from those Original Artifacts uploaded.
> I continue thinking that when there are many artifadts uploaded it is difficult to filter and have an easy understanding of the artifact result list. For example you see a file kmodule.xml, and you do not know to what artifact it belongs. You need to enter in the artifact to have this information. And when the number of artifacts in s-ramp is so big, then you see many many files, that you have no idea about them.
> If we include this expanded column and also filter field then we could have a view of the original artifacts (with no artifact parent property).
> I will prepare a html mock with my idea..."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months