June 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > > Support free-text searching through any client. Expand "xp2:matches" to support a "." value. > /s-ramp[xp2:matches(., '.*foo.*')] == find all artifacts that have "foo" in *any* metadata. > Further expand the above to include artifact *content*. We'll need to make use of ModeShape full text searching, as well as its support for Tika text extractors. > In addition, we should consider allowing searches through a content-specific value. Something like: /s-ramp[xp2:matches(@content, '.*foo.*')] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-464) Docker image

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-464?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-464: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Docker image > ------------ > > Key: ARTIF-464 > URL: https://issues.jboss.org/browse/ARTIF-464 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-657) Remove updateContent and deleteContent

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-657: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Remove updateContent and deleteContent > -------------------------------------- > > Key: ARTIF-657 > URL: https://issues.jboss.org/browse/ARTIF-657 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta1 > > > In the middle of ImpactAnalysisDemo, after all artifacts and relationships have been created, run updateContent on the XSD, using the same .xsd file. The demo will still run successfully. But when finished, pull up the UI and hit one of the Part 'parameter" artifacts, then hit their Relationship tab. It fails, most likely because the relationship wasn't re-created. > Not sure how to handle that. Should the relationships really be re-generated? If so, what happens if, for example, a WSDL Part uses a type that's been modified or removed? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-656?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-656: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Cannot query with 2 relationship predicates > ------------------------------------------- > > Key: ARTIF-656 > URL: https://issues.jboss.org/browse/ARTIF-656 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > > Example: > {code} > /s-ramp/wsdl/Part[relatedDocument[@uuid = '%1$s'] and element] > {code} > That currently results in something like: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 > INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) > INNER JOIN [sramp:target] AS target3 ON ISCHILDNODE(target3,relationship2) > INNER JOIN [sramp:baseArtifactType] AS artifact4 ON target3.[sramp:targetArtifact] = artifact4.[jcr:uuid] > INNER JOIN [sramp:relationship] AS relationship5 ON ISCHILDNODE(relationship5,artifact1) > WHERE > artifact1.[sramp:artifactType] = 'Part' > AND relationship2.[sramp:relationshipType] = 'relatedDocument' > AND artifact4.[sramp:uuid] = 'cea13510-e7a6-4195-a18e-c091eb5a939e' > AND relationship5.[sramp:relationshipType] = 'element' > AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp' > {code} > Since we use an artifact -> relationship -> target structure, and since ModeShape doesn't allow you to use the selectors transitively (ie, can't use "artifact1" in a subselect), inner joins were the method used. Each time a relationship predicate is hit, the parser assumes "I need to join and add a condition". > Forgetting the parser, for a moment, I'm not sure what the eventual query should look like... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-660) Embed ant in installer

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-660?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-660: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Embed ant in installer > ---------------------- > > Key: ARTIF-660 > URL: https://issues.jboss.org/browse/ARTIF-660 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > > To simplify the docker image, embed ant in the installer (similar to RTGov) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-661) Add "create artifact" button to UI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-661?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-661: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Add "create artifact" button to UI > ---------------------------------- > > Key: ARTIF-661 > URL: https://issues.jboss.org/browse/ARTIF-661 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > > The UI currently supports uploading artifact files. Add the ability to create logical, metadata-only artifacts as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-324) UI: Edit artifact relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-324?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-324: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > UI: Edit artifact relationships > ------------------------------- > > Key: ARTIF-324 > URL: https://issues.jboss.org/browse/ARTIF-324 > Project: Artificer > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Beta1 > > > Provide a way for the user to manage the relationships on the artifact. The user should be able to add and remove relationships. Note that some relationships are derived and thus cannot be removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-311) Add support for comments associated with an Artifact

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-311?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-311: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Add support for comments associated with an Artifact > ---------------------------------------------------- > > Key: ARTIF-311 > URL: https://issues.jboss.org/browse/ARTIF-311 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Beta1 > > > Add a UI around commenting on artifacts in the repository. Each comment should be its own artifact in the repository with a relationship to the artifact being discussed. The artifact type should be something like: > /ext/ArtifactComment -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-310) Import Artifact dialog - only enable submit button once a file is selected

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-310?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-310: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Import Artifact dialog - only enable submit button once a file is selected > -------------------------------------------------------------------------- > > Key: ARTIF-310 > URL: https://issues.jboss.org/browse/ARTIF-310 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > > The Submit (labeled "Import") button should only be enabled once the user has selected a file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-662) Upgrade to Aesh 0.59

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-662?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-662: ------------------------------ Fix Version/s: (was: 1.1.0.Final) > Upgrade to Aesh 0.59 > -------------------- > > Key: ARTIF-662 > URL: https://issues.jboss.org/browse/ARTIF-662 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha2 > > > Aesh 0.58 corrects many issues found during the Artificer CLI re-write. When available, upgrade and re-test. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2015