March 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-665) Add additional Tika text extractors for full-text searching

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-665: --------------------------------- Summary: Add additional Tika text extractors for full-text searching Key: ARTIF-665 URL: https://issues.jboss.org/browse/ARTIF-665 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final ModeShape's tika extractors include several useful defaults. However, consider adding additional extractors, at least for each built-in plugin. For example, the XML extractor considers element *values* only. Under certain circumstances (XSD types, SwitchYard, etc.), element attributes will be vital. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 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 resolved ARTIF-202. ------------------------------- Resolution: Done > 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.1.0.Final, 1.0.0.Alpha2 > > > 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, 9 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 commented on ARTIF-202: ----------------------------------- ARTIF-656 implicitly corrected this -- relationship predicates are handled with non-correlated subqueries that can be easily applied to NOT(). But, committing a regression test. > 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.1.0.Final, 1.0.0.Alpha2 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-659: ----------------------------------- Hey [~csa]! Quick question: Has anyone had success building against Errai 2 with Java 8? guava-gwt:14.0.1 appears to require 6 or 7, so at least errai-data-binding is an issue. Can I safely upgrade guava-gwt, etc., or is stepping up to Errai 3 the only option? > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-659: ----------------------------------- On hold. At least guava-gwt, and therefore Errai 2, require Java 6-7 and fail with Java 8. > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-659: ------------------------------ Fix Version/s: (was: 1.1.0.Final) (was: 1.0.0.Alpha2) > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-659: ------------------------------ Fix Version/s: 1.0.0.Alpha2 > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-571) Support stored queries in UI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-571?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-571: ------------------------------ Fix Version/s: 1.1.0.Final > Support stored queries in UI > ---------------------------- > > Key: ARTIF-571 > URL: https://issues.jboss.org/browse/ARTIF-571 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > SRAMP-29 added support for stored queries. Once SRAMP-554 is finished, add stored query support in the UI. Consider adding a "Save as Stored Query" button to the search sidebar or above the search results. The latter may be more natural. When clicked, it would open a small prompt to provide a name. All queries would be available in a drop down, available for execution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 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: 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.1.0.Final > > > 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.11#6341)

9 years, 9 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: 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: Eric Wittmann > Fix For: 1.1.0.Final > > > 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.11#6341)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2015