January 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-612) Exceptions cleanup

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-612?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-612. ------------------------------- Resolution: Done > Exceptions cleanup > ------------------ > > Key: ARTIF-612 > URL: https://issues.jboss.org/browse/ARTIF-612 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Cleanup our Exception approach. They're kind of spread everywhere and inconsistent. Re-evaluate their homes, their inheritance, HTTP response mappings, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-610) Remove the old Deriver concepts

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-610?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-610. ------------------------------- Resolution: Done > Remove the old Deriver concepts > ------------------------------- > > Key: ARTIF-610 > URL: https://issues.jboss.org/browse/ARTIF-610 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following: > org.overlord.sramp.common.derived.* > temp code in ArtifactBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[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 updated ARTIF-554: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-506) Maven repository facade. Add extended type

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-506?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-506: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Maven repository facade. Add extended type > ------------------------------------------ > > Key: ARTIF-506 > URL: https://issues.jboss.org/browse/ARTIF-506 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > It is necessary to add the possibility of setting a different s-ramp type. > By default right now the s-ramp type is Java Archive. For uploading switchyard applications it is necessary to add a mechanism to set the extended type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[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 updated ARTIF-509: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Unify s-ramp maven code > ----------------------- > > Key: ARTIF-509 > URL: https://issues.jboss.org/browse/ARTIF-509 > Project: Artificer > Issue Type: Enhancement > 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, 11 months

1
0
0 / 0

[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 updated ARTIF-499: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > 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.Alpha1 > > > 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.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-89) Create Policy derived artifact handler

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-89?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated ARTIF-89: ----------------------------- Fix Version/s: 1.0.0.Alpha1 > Create Policy derived artifact handler > -------------------------------------- > > Key: ARTIF-89 > URL: https://issues.jboss.org/browse/ARTIF-89 > Project: Artificer > Issue Type: Sub-task > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-202: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > The not() function doesn't quite work with relationships > -------------------------------------------------------- > > Key: ARTIF-202 > URL: https://issues.jboss.org/browse/ARTIF-202 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > The not() function works well with properties, but not quite with relationships. An example of what doesn't work: > /s-ramp/wsdl/Part[not(element)] > That should return all Parts that do *not* have an element relationship. Since relationships are found by doing a JOIN, it's actually tricky to invert. Right now I think the query engine will produce something that would return all Parts that have some *other* relationship - but it won't return Parts without any relationships at all. I'm not sure how to do the latter other than by using an IN with a subquery (which is supported by ModeShape but is non-standard). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-203) Ensure the not() function works with classifiers

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-203?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-203: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Ensure the not() function works with classifiers > ------------------------------------------------ > > Key: ARTIF-203 > URL: https://issues.jboss.org/browse/ARTIF-203 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > Not sure if this is working or not (I expect not): > /s-ramp/core/Document[xp2:not(classifiedByAnyOf(., '#blue', '#red'))] > It shouldn't be too hard to support - but not sure if it's working ATM. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-304) Add "Derived From" feature to Artifact Details page

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-304?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-304: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Add "Derived From" feature to Artifact Details page > --------------------------------------------------- > > Key: ARTIF-304 > URL: https://issues.jboss.org/browse/ARTIF-304 > Project: Artificer > Issue Type: Enhancement > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > > The "Derived From" feature was never implemented. This should be added back in (it's currently hidden in the template). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues January 2015