From issues at jboss.org Mon Mar 2 11:08:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Mar 2015 11:08:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045311#comment-13045311 ] Brett Meyer commented on ARTIF-573: ----------------------------------- Use this: https://github.com/aeshell/aesh/blob/master/src/main/java/Example.java#L88 > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 2 14:17:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Mar 2015 14:17:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-573: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 2 14:17:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Mar 2015 14:17:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTIF-573 started by Brett Meyer. ----------------------------------------- > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 2 14:17:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Mar 2015 14:17:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-573. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 2 14:17:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Mar 2015 14:17:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-140: ------------------------------ Parent: (was: ARTIF-396) Issue Type: Feature Request (was: Sub-task) > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 2 14:17:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Mar 2015 14:17:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-396. ------------------------------- Resolution: Done > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. > Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java > Many commands could be replaced by aesh-extensions: https://github.com/aeshell/aesh-extensions/tree/master/src/main/java/org/jboss/aesh/extensions -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 03:58:50 2015 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 3 Mar 2015 03:58:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-148) Add support for wildfly 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo reassigned OVERLORD-148: --------------------------------------------- Assignee: Gary Brown (was: David virgil naranjo) > Add support for wildfly 8 > ------------------------- > > Key: OVERLORD-148 > URL: https://issues.jboss.org/browse/OVERLORD-148 > Project: Overlord > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.12.Fina > > > We need to make sure overlord-commons works and can be installed on wildfly 8. This means updating the installer and ensuring that the IDP functions properly. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 03:58:50 2015 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 3 Mar 2015 03:58:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-597) Exception when installing overlord-rtgov-samples-all-sla profile in fabric In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo reassigned RTGOV-597: ------------------------------------------ Assignee: Gary Brown (was: David virgil naranjo) > Exception when installing overlord-rtgov-samples-all-sla profile in fabric > -------------------------------------------------------------------------- > > Key: RTGOV-597 > URL: https://issues.jboss.org/browse/RTGOV-597 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > Installing the SLA sample causes the following exceptions when the container is being provisioned: > {noformat} > Provision Exception: > io.fabric8.agent.utils.MultiException: Error updating agent > at io.fabric8.agent.DeploymentAgent.install(DeploymentAgent.java:943) > at io.fabric8.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:579) > at io.fabric8.agent.DeploymentAgent$2.run(DeploymentAgent.java:304) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > org.osgi.framework.BundleException: Activator start error in bundle samples-karaf-sla-epn [367]. > at org.apache.felix.framework.Felix.doActivateBundle(Felix.java:2437) > at org.apache.felix.framework.Felix$7.call(Felix.java:2325) > at org.apache.felix.framework.Felix.runInContext(Felix.java:2188) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:2323) > at org.apache.felix.framework.Felix.startBundle(Felix.java:2090) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942) > at io.fabric8.agent.DeploymentAgent.install(DeploymentAgent.java:936) > at io.fabric8.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:579) > at io.fabric8.agent.DeploymentAgent$2.run(DeploymentAgent.java:304) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.RuntimeException: Failed to register network > at org.overlord.rtgov.epn.loader.osgi.EPNActivator.registerEPN(EPNActivator.java:121) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator$1.registered(EPNActivator.java:52) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator$1.registered(EPNActivator.java:48) > at org.overlord.commons.services.OSGiServiceRegistry$ServiceListenerAdapter.init(OSGiServiceRegistry.java:305) > at org.overlord.commons.services.OSGiServiceRegistry$ServiceListenerAdapter.(OSGiServiceRegistry.java:262) > at org.overlord.commons.services.OSGiServiceRegistry.addServiceListener(OSGiServiceRegistry.java:222) > at org.overlord.commons.services.CompositeServiceRegistry.addServiceListener(CompositeServiceRegistry.java:85) > at org.overlord.commons.services.ServiceRegistryUtil.addServiceListener(ServiceRegistryUtil.java:60) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator.start(EPNActivator.java:61) > at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645) > at org.apache.felix.framework.Felix.doActivateBundle(Felix.java:2387) > ... 15 more > Caused by: java.lang.Exception: Failed to load Drools rules 'SLAViolationDerived.drl' for Event Processor 'SLAViolationDerived' > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:347) > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:244) > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:90) > at org.overlord.rtgov.epn.Node.init(Node.java:233) > at org.overlord.rtgov.epn.Network.preInit(Network.java:202) > at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator.registerEPN(EPNActivator.java:109) > ... 25 more > Caused by: java.lang.NoClassDefFoundError: org/drools/compiler/lang/DRL6Expressions$relationalExpression_scope > at org.drools.compiler.lang.DRL6Expressions.relationalExpression(DRL6Expressions.java:2442) > at org.drools.compiler.lang.DRL6Expressions.inExpression(DRL6Expressions.java:2280) > at org.drools.compiler.lang.DRL6Expressions.instanceOfExpression(DRL6Expressions.java:2211) > at org.drools.compiler.lang.DRL6Expressions.equalityExpression(DRL6Expressions.java:2111) > at org.drools.compiler.lang.DRL6Expressions.andExpression(DRL6Expressions.java:2042) > at org.drools.compiler.lang.DRL6Expressions.exclusiveOrExpression(DRL6Expressions.java:1974) > at org.drools.compiler.lang.DRL6Expressions.inclusiveOrExpression(DRL6Expressions.java:1906) > at org.drools.compiler.lang.DRL6Expressions.conditionalAndExpression(DRL6Expressions.java:1817) > at org.drools.compiler.lang.DRL6Expressions.conditionalOrExpression(DRL6Expressions.java:1727) > at org.drools.compiler.lang.DRL6Parser.constraint(DRL6Parser.java:3482) > at org.drools.compiler.lang.DRL6Parser.positionalConstraints(DRL6Parser.java:3397) > at org.drools.compiler.lang.DRL6Parser.speculatePositionalConstraints(DRL6Parser.java:3379) > at org.drools.compiler.lang.DRL6Parser.lhsPattern(DRL6Parser.java:3288) > at org.drools.compiler.lang.DRL6Parser.lhsPatternBind(DRL6Parser.java:3038) > at org.drools.compiler.lang.DRL6Parser.lhsUnary(DRL6Parser.java:2367) > at org.drools.compiler.lang.DRL6Parser.lhsAnd(DRL6Parser.java:2261) > at org.drools.compiler.lang.DRL6Parser.lhsOr(DRL6Parser.java:2117) > at org.drools.compiler.lang.DRL6Parser.lhsExpression(DRL6Parser.java:2016) > at org.drools.compiler.lang.DRL6Parser.lhs(DRL6Parser.java:1992) > at org.drools.compiler.lang.DRL6Parser.rule(DRL6Parser.java:1323) > at org.drools.compiler.lang.DRL6Parser.statement(DRL6Parser.java:230) > at org.drools.compiler.lang.DRL6Parser.compilationUnit(DRL6Parser.java:110) > at org.drools.compiler.lang.AbstractDRLParser.compilationUnit(AbstractDRLParser.java:86) > at org.drools.compiler.compiler.DrlParser.compile(DrlParser.java:238) > at org.drools.compiler.compiler.DrlParser.parse(DrlParser.java:155) > at org.drools.compiler.compiler.DrlParser.parse(DrlParser.java:144) > at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.drlToPackageDescr(KnowledgeBuilderImpl.java:409) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl$1.map(CompositeKnowledgeBuilderImpl.java:443) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildResource(CompositeKnowledgeBuilderImpl.java:368) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackageDescr(CompositeKnowledgeBuilderImpl.java:351) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:100) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:91) > at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:220) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:43) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:208) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:177) > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:316) > ... 31 more > Caused by: java.lang.ClassNotFoundException: Unable to load class 'org.drools.compiler.lang.DRL6Expressions$relationalExpression_scope' because the bundle wiring for org.drools.compiler is no longer valid. > at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1494) > at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75) > at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 68 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 03:59:49 2015 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 3 Mar 2015 03:59:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tv In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo reassigned ARTIF-214: ------------------------------------------ Assignee: Brett Meyer (was: David virgil naranjo) > When uploading a jar - upload a text file with the output of jar tv > ------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 03:59:49 2015 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 3 Mar 2015 03:59:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-316) Implement sorting for all tables In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo reassigned ARTIF-316: ------------------------------------------ Assignee: Brett Meyer (was: David virgil naranjo) > Implement sorting for all tables > -------------------------------- > > Key: ARTIF-316 > URL: https://issues.jboss.org/browse/ARTIF-316 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Currently there is no way to sort the items in, for example, the Artifacts table. The user should be able to click on the header and sort. > This same behavior should be added to dtgov as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 04:00:50 2015 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 3 Mar 2015 04:00:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-472) Selenium UI tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo reassigned ARTIF-472: ------------------------------------------ Assignee: Brett Meyer (was: David virgil naranjo) > Selenium UI tests > ----------------- > > Key: ARTIF-472 > URL: https://issues.jboss.org/browse/ARTIF-472 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 12:04:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 3 Mar 2015 12:04:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045762#comment-13045762 ] Gary Brown commented on RTGOV-645: ---------------------------------- Have an implementation of these requirements, albeit not visually represented using a tree, in this branch: https://github.com/objectiser/rtgov/tree/RTGOV-645 This can be built locally (using mvn clean install -Pdocs) - the docs profile will be required initially to build a version of the docs to be included in the distribution. This distribution is for installation into a Wildfly 8.1 environment (which will also need switchyard to be installed to create some situations). The distribution will be available from "distribution/overlord-rtgov-dist-all-wildfly8/target". The new install instructions for this build are documented here: http://docs.jboss.org/overlord/rtgov/2.1.0.Beta1/userguide/html/_installation.html#_setup_target_environment (suggest using the ./standalone.sh startup approach shown at the end of section 2.1 to initialise the SSO mechanism). Note: these changes are currently made in master, but will be backported to the EAP version once completed. > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 3 14:16:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 3 Mar 2015 14:16:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-654) ModeShape query indexing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-654. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > ModeShape query indexing > ------------------------ > > Key: ARTIF-654 > URL: https://issues.jboss.org/browse/ARTIF-654 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > ModeShape query indexing needs setup: https://docs.jboss.org/author/display/MODE40/Query+and+search#Queryandsearch-Usingindexes > MS local filesystem index is currently limited to single columns. So, the primary way we could use it may be limited to query-by-sramp:uuid. But realistically, that's the most frequently used one anyway... -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 4 13:15:51 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-571) Support stored queries in UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-571: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > 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 > > 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) From issues at jboss.org Wed Mar 4 13:15:51 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-320) Artifacts Page - add multi-select with Actions drop-down In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-320: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Artifacts Page - add multi-select with Actions drop-down > -------------------------------------------------------- > > Key: ARTIF-320 > URL: https://issues.jboss.org/browse/ARTIF-320 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Currently artifacts cannot be selected. We need to support multi-select. Once that is done, the actions drop-down should be restored and implemented (e.g. Download, Delete, etc...) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 4 13:15:51 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-319) Implement the Actions drop-down on the Artifact Details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-319: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Implement the Actions drop-down on the Artifact Details page > ------------------------------------------------------------ > > Key: ARTIF-319 > URL: https://issues.jboss.org/browse/ARTIF-319 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > This functionality is currently hidden - but the Actions drop-down should be re-enabled and implemented. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 4 13:15:51 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-311) Add support for comments associated with an Artifact In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-311: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > 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 > > 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) From issues at jboss.org Wed Mar 4 13:15:52 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:52 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-310) Import Artifact dialog - only enable submit button once a file is selected In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-310: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > 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: Eric Wittmann > > 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.11#6341) From issues at jboss.org Wed Mar 4 13:15:52 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:52 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-307) Enable/disable Import button based on file selection status (Import Artifact modal dialog) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-307: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Enable/disable Import button based on file selection status (Import Artifact modal dialog) > ------------------------------------------------------------------------------------------ > > Key: ARTIF-307 > URL: https://issues.jboss.org/browse/ARTIF-307 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 4 13:15:52 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 13:15:52 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-305) Improve inline editing of properties (new UX spec) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-305: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Improve inline editing of properties (new UX spec) > -------------------------------------------------- > > Key: ARTIF-305 > URL: https://issues.jboss.org/browse/ARTIF-305 > Project: Artificer > Issue Type: Enhancement > Components: UI > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Attachments: GovernanceUI-In-lineeditingspecification.pdf > > > The inline editing on the Artifact Details page should be improved. > - The hover effect doesn't quite work properly (doesn't always go away) > - Editing the value opens a modal dialog > - A new visual spec was received from UX (see attached) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 4 14:52:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 14:52:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-656: --------------------------------- Summary: 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 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.11#6341) From issues at jboss.org Wed Mar 4 14:53:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 14:53:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046369#comment-13046369 ] Brett Meyer commented on ARTIF-656: ----------------------------------- Once fixed, uncomment the test in JCRRelationshipQueryTest and re-test the derived-artifacts demo. > 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 > > 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.11#6341) From issues at jboss.org Wed Mar 4 15:14:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 15:14:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046374#comment-13046374 ] Brett Meyer commented on ARTIF-656: ----------------------------------- https://developer.jboss.org/message/920583 > 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 > > 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.11#6341) From issues at jboss.org Wed Mar 4 16:34:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 16:34:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046395#comment-13046395 ] Brett Meyer commented on ARTIF-575: ----------------------------------- Needs clarified in the spec. On hold for https://issues.oasis-open.org/browse/SRAMP-73 > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > From the Atom Binding spec, 3.3.1: > {quote} > Stored Query Entry documents MAY also be used as templates, allowing simple substitution of client specified parameter values during execution. The syntax for parameter substitution follows the XPath2 style to represent a variable within the query filter: > > $\{var-name\} > > A value for the var-name can then be specified as part of the query invocation. Default values are not supported. > {quote} > {code}s-ramp/serviceImplementation/ServiceInstance[@version >= ${MINVERSION}]>{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 4 16:36:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Mar 2015 16:36:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-500) Improve the S-RAMP demo README files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-500. ----------------------------- Resolution: Won't Fix For now, closing. I'm less concerned about the READMEs and more concerned about the readability of the demo code itself. > Improve the S-RAMP demo README files > ------------------------------------ > > Key: ARTIF-500 > URL: https://issues.jboss.org/browse/ARTIF-500 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > > From David via his 0.5.0.Beta1 Testing: > S-ramp DEMO README files. The majority of them are a copy/paste (not always). Here what can happen to user is that as you realized about the copy paste, then you do not read the README files, and they are not useful. I think we could explain little bit more in detail what the test is doing in terms of: > - 2 files are uploaded: specify the names. > - Then a query that checks the property name 'xxx' is executed... > This can give more value to the good tests we have, and the user would read the README file. That for me is very important. > A good example of Test Output is the s-ramp-demos-simple-client: > {code} > Uploading some XML schemas... > Uploading artifact ws-humantask.xsd...done. > Updating meta-data for artifact ws-humantask.xsd...done. > Uploading artifact ws-humantask-context.xsd...done. > Updating meta-data for artifact ws-humantask-context.xsd...done. > Uploading artifact ws-humantask-policy.xsd...done. > Updating meta-data for artifact ws-humantask-policy.xsd...done. > Uploading artifact ws-humantask-types.xsd...done. > Updating meta-data for artifact ws-humantask-types.xsd...done. > Uploading artifact ws-humantask-leantask-api.wsdl...done. > Updating meta-data for artifact ws-humantask-leantask-api.wsdl...done. > Uploading artifact ws-humantask-protocol.wsdl...done. > Updating meta-data for artifact ws-humantask-protocol.wsdl...done. > Querying the S-RAMP repository for Schemas...success: 11 Schemas found: > * address.xsd (b885aebb-9f84-424d-af1e-84e335163be7) > * person.xsd (895719d6-0daa-448b-87c8-6085021e29ba) > * ws-humantask-context.xsd (fb253cc7-d576-4127-b331-cc384218bc06) > * ws-humantask-policy.xsd (2eebffe7-2e02-4985-b04f-24e6025489c3) > * ws-humantask-types.xsd (cfa90bea-c27c-49bb-8ac2-604f2a3763f3) > * ws-humantask.xsd (a3bc7c9f-54fa-489e-845c-a328ab968bd9) > * wsrm-1.1-schema-200702.xsd (54731483-c7d1-40d6-b152-f332bebf17d1) > * wsrmp-1.2-schema-200702.xsd (f3007bee-353e-4e1b-a79d-0aea85c7b1ed) > * wss-wssecurity-secext-1.0.xsd (8cef7a73-e284-411e-9af9-9b1ada31f623) > * wss-wssecurity-utility-1.0.xsd (cee6023f-e26f-4240-baa6-594d1eea4928) > * wstx-wsba-1.1-schema-200701.xsd (30246422-dc4e-4bc6-8317-8d58a73e3c64) > {code} > It gives explanations about the files uploaded and the queries done. In other tests just it is said 2 files uploaded, and then query done sucessfully. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Mar 6 14:05:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 6 Mar 2015 14:05:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-657) updateContent may not be recreating relationships correctly In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-657: --------------------------------- Summary: updateContent may not be recreating relationships correctly Key: ARTIF-657 URL: https://issues.jboss.org/browse/ARTIF-657 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer 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.11#6341) From issues at jboss.org Mon Mar 9 12:13:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Mar 2015 12:13:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-575: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > From the Atom Binding spec, 3.3.1: > {quote} > Stored Query Entry documents MAY also be used as templates, allowing simple substitution of client specified parameter values during execution. The syntax for parameter substitution follows the XPath2 style to represent a variable within the query filter: > > $\{var-name\} > > A value for the var-name can then be specified as part of the query invocation. Default values are not supported. > {quote} > {code}s-ramp/serviceImplementation/ServiceInstance[@version >= ${MINVERSION}]>{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 9 13:17:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Mar 2015 13:17:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048240#comment-13048240 ] Brett Meyer commented on ARTIF-260: ----------------------------------- [~rhauch], any thoughts/caveats on this? We're interested in full-text search, both for node properties as well as file content. But, concerned about scalability, as we have a few Artificer uses on the table that involve 10+ million primary artifacts, the bulk of which would have binary content. 1.) Am I correct that MS 4 does not currently support a query index on the file content itself? 2.) Would we be better off using a combination of MS full-text queries on metadata, then an external Lucene/ElasticSearch instance on the file contents (we use the filesystem for binary storage)? Would we be able to use the file's binary storage pathname (looks to be a UUID) to then lookup the associated nodes that reference it? > 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.Alpha1 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 9 13:17:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Mar 2015 13:17:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > 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.Alpha1 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 9 14:51:18 2015 From: issues at jboss.org (Randall Hauch (JIRA)) Date: Mon, 9 Mar 2015 14:51:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048319#comment-13048319 ] Randall Hauch commented on ARTIF-260: ------------------------------------- I agree that full-text search performance is currently an issue with MS 4.x. Someone in the ModeShape community is working on a Lucene index provider, so you could ask and collaborate. We sure could use the help. > 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.Alpha1 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:06:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:06:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.2.0 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-658: --------------------------------- Summary: Upgrade to ModeShape 4.2.0 Key: ARTIF-658 URL: https://issues.jboss.org/browse/ARTIF-658 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:20:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:20:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-658: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Upgrade to ModeShape 4.2.0 > -------------------------- > > Key: ARTIF-658 > URL: https://issues.jboss.org/browse/ARTIF-658 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:20:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:20:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048641#comment-13048641 ] Brett Meyer commented on ARTIF-658: ----------------------------------- On hold. The WF8 distro is only available in MS 4.0. Check on 4.2 plans. > Upgrade to ModeShape 4.2.0 > -------------------------- > > Key: ARTIF-658 > URL: https://issues.jboss.org/browse/ARTIF-658 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:22:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:22:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-659: --------------------------------- Summary: 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) From issues at jboss.org Tue Mar 10 11:30:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:30:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > 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 > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:31:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:31:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: 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.1.0.Final > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:32:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:32:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-659: ------------------------------ Fix Version/s: 1.1.0.Final > 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 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:32:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:32:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048649#comment-13048649 ] Brett Meyer commented on ARTIF-260: ----------------------------------- https://docs.jboss.org/author/display/MODE/Full+text+search https://docs.jboss.org/author/display/MODE/Built-in+text+extractors > 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.1.0.Final > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 10 11:33:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Mar 2015 11:33:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048649#comment-13048649 ] Brett Meyer edited comment on ARTIF-260 at 3/10/15 11:32 AM: ------------------------------------------------------------- https://docs.jboss.org/author/display/MODE/Full+text+search https://docs.jboss.org/author/display/MODE/JCR-SQL2#JCR-SQL2-Fulltextsearchconstraint https://docs.jboss.org/author/display/MODE/Built-in+text+extractors was (Author: brmeyer): https://docs.jboss.org/author/display/MODE/Full+text+search https://docs.jboss.org/author/display/MODE/Built-in+text+extractors > 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.1.0.Final > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:55:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:55:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-604) Show relationships targeting the current artifact in the UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-604. ----------------------------- > Show relationships targeting the current artifact in the UI > ----------------------------------------------------------- > > Key: ARTIF-604 > URL: https://issues.jboss.org/browse/ARTIF-604 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Great idea from [~eric.wittmann] on an email thread: > {quote} > I also think there is room in the UI for some way to show all artifacts > that point to the current artifact by a specific relationship. So > perhaps an editable drop-down control allowing the user to select a > common relationship or type their own, which would result in this query: > /s-ramp//[[@uuid = ]] > The , , and values come from the currently selected > artifact. The comes from the dropdown. Populate a table > with the results! > {quote} > Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/\{uuid\}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:55:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:55:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-610. ----------------------------- > 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) From issues at jboss.org Wed Mar 11 13:55:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:55:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-632) Deprecate Tomcat support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-632. ----------------------------- > Deprecate Tomcat support > ------------------------ > > Key: ARTIF-632 > URL: https://issues.jboss.org/browse/ARTIF-632 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Until KEYCLOAK-932, deprecate Tomcat support. We could require the use of the standalone Keycloak appliance, external to the Tomcat instance, but it'll be work to configure/support and is probably not worth it. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:55:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:55:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-654) ModeShape query indexing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-654. ----------------------------- > ModeShape query indexing > ------------------------ > > Key: ARTIF-654 > URL: https://issues.jboss.org/browse/ARTIF-654 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > ModeShape query indexing needs setup: https://docs.jboss.org/author/display/MODE40/Query+and+search#Queryandsearch-Usingindexes > MS local filesystem index is currently limited to single columns. So, the primary way we could use it may be limited to query-by-sramp:uuid. But realistically, that's the most frequently used one anyway... -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-517) Support Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-517. ----------------------------- > Support Wildfly > --------------- > > Key: ARTIF-517 > URL: https://issues.jboss.org/browse/ARTIF-517 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-573. ----------------------------- > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-396. ----------------------------- > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. > Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java > Many commands could be replaced by aesh-extensions: https://github.com/aeshell/aesh-extensions/tree/master/src/main/java/org/jboss/aesh/extensions -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-509) Unify s-ramp maven code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-644) Remove the Maven Wagon module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-644. ----------------------------- > Remove the Maven Wagon module > ----------------------------- > > Key: ARTIF-644 > URL: https://issues.jboss.org/browse/ARTIF-644 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > After the rest of ARTIF-581 is finished, remove the Maven Wagon module (and docs) completely. Convert the demos to use the facade. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-582) Create Maven Facade unit/integration test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-582. ----------------------------- > Create Maven Facade unit/integration test > ----------------------------------------- > > Key: ARTIF-582 > URL: https://issues.jboss.org/browse/ARTIF-582 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > Fix For: 1.0.0.Alpha1 > > > This should be the priority and done before any other sub-task. Create extensive unit/integration tests to provide adequate coverage of all Maven Facade functionality. Due to the Facade's potential complexity, it should be developed with a test-first approach. > See SrampWagonTest for some inspiration. Some of it may be directly applicable. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-462) S-RAMP 1.0 spec compliance and TCK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-462. ----------------------------- > S-RAMP 1.0 spec compliance and TCK > ---------------------------------- > > Key: ARTIF-462 > URL: https://issues.jboss.org/browse/ARTIF-462 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Parent task for tracking all S-RAMP 1.0 spec support and TCK development. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-554) Improve the UI search capabilities and query syntax support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-637) Upgrade IP BOM to 6.0.0.CR22 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-637. ----------------------------- > Upgrade IP BOM to 6.0.0.CR22 > ---------------------------- > > Key: ARTIF-637 > URL: https://issues.jboss.org/browse/ARTIF-637 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-581) Finish the Maven Facade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-581. ----------------------------- > Finish the Maven Facade > ----------------------- > > Key: ARTIF-581 > URL: https://issues.jboss.org/browse/ARTIF-581 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The vision for the Maven Facade is the eventual replacement of the Maven Wagon, in addition to several interesting use cases. > - deployment repository > - dependency repository > - Nexus Proxy support -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-625) Support Target#otherAttributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-612) Exceptions cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-612. ----------------------------- > 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) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-630. ----------------------------- > SRAMP-626 broke the ability to pull from the S-RAMP wagon > --------------------------------------------------------- > > Key: ARTIF-630 > URL: https://issues.jboss.org/browse/ARTIF-630 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-619) Remove the Overlord UI header In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-619. ----------------------------- > Remove the Overlord UI header > ----------------------------- > > Key: ARTIF-619 > URL: https://issues.jboss.org/browse/ARTIF-619 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-402. ----------------------------- > S-RAMP Shell New Commands > ------------------------- > > Key: ARTIF-402 > URL: https://issues.jboss.org/browse/ARTIF-402 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Some new commands to be added: > - s-ramp:clear: clean the current s-ramp session. > - ontology:status: will work as the s-ramp:status command, but it applies to ontology. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-647) Combine repository-jcr and repository-jcr-modeshape In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-647. ----------------------------- > Combine repository-jcr and repository-jcr-modeshape > --------------------------------------------------- > > Key: ARTIF-647 > URL: https://issues.jboss.org/browse/ARTIF-647 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Combine repository-jcr and repository-jcr-modeshape into one single module. Although I understand the intention behind the abstraction, it introduces quite a bit of needless complexity. There are *a lot* of optimizations that could be made if Modeshape-only is assumed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-400. ----------------------------- > Client requests missing providers for most Exceptions > ----------------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > This task started out as: > {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} > However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-643) Tune Infinispan eviction and locking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-643. ----------------------------- > Tune Infinispan eviction and locking > ------------------------------------ > > Key: ARTIF-643 > URL: https://issues.jboss.org/browse/ARTIF-643 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Ideas: > https://developer.jboss.org/message/916833 > https://docs.jboss.org/author/display/MODE40/Configuration -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-629) Convert auth to Keycloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-629. ----------------------------- > Convert auth to Keycloak > ------------------------ > > Key: ARTIF-629 > URL: https://issues.jboss.org/browse/ARTIF-629 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-627) Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-627. ----------------------------- > Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM > -------------------------------------------------------------- > > Key: ARTIF-627 > URL: https://issues.jboss.org/browse/ARTIF-627 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: > /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] > Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. > Attempt to use ModeShape's JCR-JQOM: > https://docs.jboss.org/author/display/MODE40/JCR-JQOM > ModeShape also has a builder class, but it's not public and may pose additional issues. > {quote} > (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 > (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-203) Ensure the not() function works with classifiers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-203. ----------------------------- > 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: Brett Meyer > 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) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-628) Completely remove Fuse/Jetty/OSGi concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-628. ----------------------------- > Completely remove Fuse/Jetty/OSGi concepts > ------------------------------------------ > > Key: ARTIF-628 > URL: https://issues.jboss.org/browse/ARTIF-628 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: > 1.) completely remove the modules > 2.) remove all OSGi dependencies > 3.) remove Felix annotations > 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-401) S-RAMP Shell Improve the ontology list and s-ramp query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-401. ----------------------------- > S-RAMP Shell Improve the ontology list and s-ramp query > ------------------------------------------------------- > > Key: ARTIF-401 > URL: https://issues.jboss.org/browse/ARTIF-401 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > In the ontology list command and the s-ramp query command the uuid has to be displayed as a new column of the result set. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-640) Disable JMS support by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-640. ----------------------------- > Disable JMS support by default > ------------------------------ > > Key: ARTIF-640 > URL: https://issues.jboss.org/browse/ARTIF-640 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Make JMS support configurable, disabled by default. It's one of the worst hot spots in CPU profiling, mainly due to Jackson serialization. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-302) Artifact Details: core and custom properties share vertical space In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-302. ----------------------------- > Artifact Details: core and custom properties share vertical space > ----------------------------------------------------------------- > > Key: ARTIF-302 > URL: https://issues.jboss.org/browse/ARTIF-302 > Project: Artificer > Issue Type: Bug > Components: UI > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The Core Properties and Custom Properties are clearly inside the same "row" because they share vertical space. This means that if you have a lot of custom properties then the Classifiers and Description sections will get pushed down. > Perhaps Description should be moved up and Classifiers can share the same column as Core Properties. This *should* provide enough horizontal space for the list of classifiers (even though they are URLs). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-583) Consider completely removing the web-view support in the Maven Facade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-583. ----------------------------- > Consider completely removing the web-view support in the Maven Facade > --------------------------------------------------------------------- > > Key: ARTIF-583 > URL: https://issues.jboss.org/browse/ARTIF-583 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Although I understand the initial desire to have a web-view interface for the Maven Facade (similar to Nexus' ability to navigate the repo w/ a web browser), I think I'd recommend removing the capability entirely. The current implementation isn't complete and misses a few key areas. Overcoming every complex situation will be challenging and not worth the effort. > I would much rather require the use of the real S-RAMP UI. If there are specific use cases that the Facade view aimed for, implement them as improvements to the UI. > So, I'm advocating that we strip out the Facade view, JSPs, etc. entirely. Thoughts? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-641) Disable Auditing by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-641. ----------------------------- > Disable Auditing by default > --------------------------- > > Key: ARTIF-641 > URL: https://issues.jboss.org/browse/ARTIF-641 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Profiling shows auditing to be somewhat of a CPU hotspot (in addition to creating artifact child nodes). Disable by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-600) Support batch archive updates through PUT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-600. ----------------------------- > Support batch archive updates through PUT > ----------------------------------------- > > Key: ARTIF-600 > URL: https://issues.jboss.org/browse/ARTIF-600 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-638) Support interacting with Artificer through EJB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-638. ----------------------------- > Support interacting with Artificer through EJB > ---------------------------------------------- > > Key: ARTIF-638 > URL: https://issues.jboss.org/browse/ARTIF-638 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > For better integration with other apps (especially Hawkular), support interacting with Artificer through EJB, removing the need to hit its REST services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-646) Protect Maven Facade servlet In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-646. ----------------------------- > Protect Maven Facade servlet > ---------------------------- > > Key: ARTIF-646 > URL: https://issues.jboss.org/browse/ARTIF-646 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The servlet is not currently protected within the web.xml security-constraint, due to WFLY-4304. Once that's corrected, fix web.xml and re-test. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 13:56:22 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 13:56:22 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-636) Support EAP 6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-636. ----------------------------- > Support EAP 6.4 > --------------- > > Key: ARTIF-636 > URL: https://issues.jboss.org/browse/ARTIF-636 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1, 0.6.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 16:15:21 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 16:15:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-660) Embed ant in installer In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-660: --------------------------------- Summary: 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.1.0.Final To simplify the docker image, embed ant in the installer (similar to RTGov) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 17:17:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 17:17:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049146#comment-13049146 ] Brett Meyer commented on ARTIF-260: ----------------------------------- Asking for spec support in https://issues.oasis-open.org/browse/SRAMP-74 > 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.1.0.Final > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 11 17:45:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Mar 2015 17:45:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-260: ------------------------------ Description: 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.*')] was: The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. One need to use the S-RAMP Query language. https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage Would be nice to have a free text search capability to search for artifacts. > 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.1.0.Final > > > 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.11#6341) From issues at jboss.org Thu Mar 12 11:54:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 11:54:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-660) Embed ant in installer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-660: ------------------------------ Fix Version/s: 1.0.0.Alpha2 > 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.1.0.Final, 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.11#6341) From issues at jboss.org Thu Mar 12 11:54:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 11:54:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-660) Embed ant in installer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-660. ------------------------------- Resolution: Done > 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.1.0.Final, 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.11#6341) From issues at jboss.org Thu Mar 12 14:56:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 14:56:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049584#comment-13049584 ] Brett Meyer commented on ARTIF-260: ----------------------------------- Query syntax design discussion: https://developer.jboss.org/message/921248 > 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.1.0.Final > > > 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.11#6341) From issues at jboss.org Thu Mar 12 16:06:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 16:06:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-661) Add "create artifact" button to UI In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-661: --------------------------------- Summary: 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.1.0.Final 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.11#6341) From issues at jboss.org Thu Mar 12 21:48:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 21:48:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-661) Add "create artifact" button to UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-661: ------------------------------ Fix Version/s: 1.0.0.Alpha2 > 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.1.0.Final, 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.11#6341) From issues at jboss.org Thu Mar 12 21:48:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 21:48:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-661) Add "create artifact" button to UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-661. ------------------------------- Resolution: Done > 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.1.0.Final, 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.11#6341) From issues at jboss.org Thu Mar 12 21:50:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 21:50:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-310) Import Artifact dialog - only enable submit button once a file is selected In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-310: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > 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 > > 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.11#6341) From issues at jboss.org Thu Mar 12 21:51:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 21:51:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-307) Enable/disable Import button based on file selection status (Import Artifact modal dialog) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-307. ----------------------------- Resolution: Duplicate Issue > Enable/disable Import button based on file selection status (Import Artifact modal dialog) > ------------------------------------------------------------------------------------------ > > Key: ARTIF-307 > URL: https://issues.jboss.org/browse/ARTIF-307 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Mar 12 22:30:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 12 Mar 2015 22:30:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-310) Import Artifact dialog - only enable submit button once a file is selected In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-310. ------------------------------- Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 Resolution: Done > 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.1.0.Final, 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.11#6341) From issues at jboss.org Fri Mar 13 11:17:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 13 Mar 2015 11:17:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-467) UI: relationship visualizations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049927#comment-13049927 ] Brett Meyer commented on ARTIF-467: ----------------------------------- Ideas: Tinkerpop includes several visualization capabilities, but it would require a Blueprint API layer over the top of Artificer: https://github.com/tinkerpop/rexster/wiki https://raw.githubusercontent.com/tinkerpop/rexster/master/doc/images/rexster-dog-house-viz.png brmeyer, some time ago I was also playing with some JS graph libraries, namely: sigma js (https://jiri-kremser.github.io/JavaScriptPlayground/sigma.js/index.html) and arbor (https://jiri-kremser.github.io/JavaScriptPlayground/arbor-and-dat.GUI/index.html) > UI: relationship visualizations > ------------------------------- > > Key: ARTIF-467 > URL: https://issues.jboss.org/browse/ARTIF-467 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Mar 13 11:19:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 13 Mar 2015 11:19:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-309) Support a graphical view of the services and their relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-309. ----------------------------- Resolution: Duplicate Issue > Support a graphical view of the services and their relationships > ---------------------------------------------------------------- > > Key: ARTIF-309 > URL: https://issues.jboss.org/browse/ARTIF-309 > Project: Artificer > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Eric Wittmann > > Currently a user can navigate the graph of services and their relationships. However this does not easily enable the user to understand the overall picture of how their services and dependencies may be structured. > A graphical view could help to better understand this information, enabling the user to navigate from the nodes or links to gain further information about the individual items. > In terms of the visual presentation, some UML diagrams may provide a familiar look. However this is just styling, and any network/graph based representation could be used. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 16 15:42:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 15:42:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-467) UI: relationship visualizations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050657#comment-13050657 ] Brett Meyer commented on ARTIF-467: ----------------------------------- Thanks to [~rhauch] for suggesting http://d3js.org > UI: relationship visualizations > ------------------------------- > > Key: ARTIF-467 > URL: https://issues.jboss.org/browse/ARTIF-467 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 16 15:59:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 15:59:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-324) UI: Edit artifact relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-324: ------------------------------ Summary: UI: Edit artifact relationships (was: Artifact Details - Relationships (mutable)) > UI: Edit artifact relationships > ------------------------------- > > Key: ARTIF-324 > URL: https://issues.jboss.org/browse/ARTIF-324 > Project: Artificer > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > 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) From issues at jboss.org Mon Mar 16 15:59:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 15:59:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-324) UI: Edit artifact relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-324: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > 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 > > 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) From issues at jboss.org Mon Mar 16 15:59:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 15:59:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-324) UI: Edit artifact relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050666#comment-13050666 ] Brett Meyer commented on ARTIF-324: ----------------------------------- In addition to a simple form-based approach, experiment with mutable visualizations. For instance, http://bl.ocks.org/robschmuecker/7880033 supports drag-and-drop > 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 > > 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) From issues at jboss.org Mon Mar 16 16:27:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 16:27:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-467) UI: relationship visualizations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050673#comment-13050673 ] Brett Meyer commented on ARTIF-467: ----------------------------------- >From [~jowilson]: http://visjs.org/network_examples.html > UI: relationship visualizations > ------------------------------- > > Key: ARTIF-467 > URL: https://issues.jboss.org/browse/ARTIF-467 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 16 21:29:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 21:29:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-662) Upgrade to Aesh 0.58 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-662: --------------------------------- Summary: Upgrade to Aesh 0.58 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.1.0.Final, 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.11#6341) From issues at jboss.org Mon Mar 16 22:54:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 22:54:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-663) UI: Delete Artifact is broken In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-663: --------------------------------- Summary: UI: Delete Artifact is broken Key: ARTIF-663 URL: https://issues.jboss.org/browse/ARTIF-663 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Deleting an artifact, through the UI's artifact details view, is broken: "org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Unsupported Media Type" When correcting, think through how constraint violations should look. Maybe just throw it and let the error message come up? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 16 22:54:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 16 Mar 2015 22:54:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-663) UI: Delete Artifact is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-663: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 > UI: Delete Artifact is broken > ----------------------------- > > Key: ARTIF-663 > URL: https://issues.jboss.org/browse/ARTIF-663 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > > Deleting an artifact, through the UI's artifact details view, is broken: > "org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Unsupported Media Type" > When correcting, think through how constraint violations should look. Maybe just throw it and let the error message come up? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 17 21:46:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 17 Mar 2015 21:46:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-663) UI: Delete Artifact is broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-663. ------------------------------- Resolution: Done > UI: Delete Artifact is broken > ----------------------------- > > Key: ARTIF-663 > URL: https://issues.jboss.org/browse/ARTIF-663 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > > Deleting an artifact, through the UI's artifact details view, is broken: > "org.jboss.errai.enterprise.client.jaxrs.api.ResponseException: Unsupported Media Type" > When correcting, think through how constraint violations should look. Maybe just throw it and let the error message come up? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 17 23:26:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 17 Mar 2015 23:26:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-467) UI: relationship visualizations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051212#comment-13051212 ] Brett Meyer commented on ARTIF-467: ----------------------------------- A few D3 ideas: UNIDIRECTIONAL http://charts.animateddata.co.uk/datavistree & http://mbostock.github.io/d3/talk/20111018/tree.html http://bl.ocks.org/mbostock/1093025 http://bl.ocks.org/Neilos/584b9a5d44d5fe00f779 BIDIRECTIONAL http://www.redotheweb.com/DependencyWheel/ > UI: relationship visualizations > ------------------------------- > > Key: ARTIF-467 > URL: https://issues.jboss.org/browse/ARTIF-467 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 17 23:28:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 17 Mar 2015 23:28:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-467) UI: relationship visualizations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051212#comment-13051212 ] Brett Meyer edited comment on ARTIF-467 at 3/17/15 11:27 PM: ------------------------------------------------------------- A few ideas from the examples: UNIDIRECTIONAL http://charts.animateddata.co.uk/datavistree & http://mbostock.github.io/d3/talk/20111018/tree.html http://bl.ocks.org/mbostock/1093025 http://bl.ocks.org/Neilos/584b9a5d44d5fe00f779 http://visjs.org/examples/network/23_hierarchical_layout.html BIDIRECTIONAL http://www.redotheweb.com/DependencyWheel/ was (Author: brmeyer): A few D3 ideas: UNIDIRECTIONAL http://charts.animateddata.co.uk/datavistree & http://mbostock.github.io/d3/talk/20111018/tree.html http://bl.ocks.org/mbostock/1093025 http://bl.ocks.org/Neilos/584b9a5d44d5fe00f779 BIDIRECTIONAL http://www.redotheweb.com/DependencyWheel/ > UI: relationship visualizations > ------------------------------- > > Key: ARTIF-467 > URL: https://issues.jboss.org/browse/ARTIF-467 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 18 06:27:19 2015 From: issues at jboss.org (Michael Ilger (JIRA)) Date: Wed, 18 Mar 2015 06:27:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051273#comment-13051273 ] Michael Ilger commented on RTGOV-645: ------------------------------------- Hi Gary, Regarding your questions: Represent situations in a tree representing the resubmission failures: This could lead to usability problems, as the user has to do a lot of extra navigation to get the details of all situations. Additionally there are also bulk actions and filters to keep in mind. The root node shows the number of resubmits so far (this is equal to the number of child nodes): Showing the total of child nodes sounds like a reasonable approach to just give the user a feeling of the overall amount of data connected. Only the newest situation in a tree is allowed to be resubmitted: From our point of view the newest situation can always be retried (also multiple times, given that it stays the newest situation) [..]Either the tree is fully shown or hidden: This really depends on the definition of leaf node, and what we expect the tree to look like. Our assumption is that all resubmissions are immediate children of the original message, which gives us a tree of depth 1 with a lot of leaves. > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 18 08:37:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 18 Mar 2015 08:37:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051338#comment-13051338 ] Gary Brown commented on RTGOV-645: ---------------------------------- Hi Michael - thanks for the additional information. It might be best to take one point at a time - so firstly want to concentrate on the resubmission failure and what could occur. In your description I believe there is an assumption that failure of a resubmission will result in a single further situation - and therefore if this was the case, your description of only the 'newest' situation being resubmitted again makes sense. However what happens if when the resubmitted message fails it results in multiple further situations being created? And due to the async nature of the system, there is no guarantee in which order these new situations would be created? > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 18 09:10:19 2015 From: issues at jboss.org (Michael Ilger (JIRA)) Date: Wed, 18 Mar 2015 09:10:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051346#comment-13051346 ] Michael Ilger commented on RTGOV-645: ------------------------------------- Hi Gary, You are correct that our assumption is that only one single new situation would be created. I wonder if it would make sense to set up a quick call to discuss our requirements and map them to the generic requirements you see. Doing this in email or ticket comments would probably make this an unnecessarily long process. > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 18 21:14:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 18 Mar 2015 21:14:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-464) Docker image In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-464: ------------------------------ Git Pull Request: https://github.com/ArtificerRepo/artificer/pull/516 > 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 > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Mar 19 04:22:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 19 Mar 2015 04:22:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051653#comment-13051653 ] Gary Brown commented on RTGOV-645: ---------------------------------- It may be possible (for now) to just assume that only one situation will be created from resubmit failure, and if multiple get created, then only the most recent of those will be candidate for further resubmit. However that leaves one issue - if there is some way to show this list of child situations by expanding the root situation, then it means that to do a further resubmit the user needs to (a) expand the root node, and (b) locate the last situation in the list and navigate to it. Are you ok with this? Possibly the child situations should be in reverse order, so most recent first? > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Mar 19 15:32:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Mar 2015 15:32:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-464) Docker image In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-464. ------------------------------- Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 Resolution: Done Jorge's Docker test profile (in distro/assembly) is pushed to both master and 1.0. The real Docker image: https://github.com/ArtificerRepo/artificer-docker https://registry.hub.docker.com/u/artificer/wildfly82/ The image currently uses a 1.0.0-SNAPSHOT build. I'll update it with Alpha2 once released. > 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.1.0.Final, 1.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 23 07:42:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 23 Mar 2015 07:42:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-645: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/278 > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 23 07:42:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 23 Mar 2015 07:42:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-645: ----------------------------- Fix Version/s: 2.1.0.Beta2 (was: 2.2.0) > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 23 12:20:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 23 Mar 2015 12:20:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-645: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/278, https://github.com/Governance/rtgov/pull/279 (was: https://github.com/Governance/rtgov/pull/278) > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 23 12:21:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 23 Mar 2015 12:21:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-645. ------------------------------ Resolution: Done > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 23 22:10:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 23 Mar 2015 22:10:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-662) Upgrade to Aesh 0.59 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-662: ------------------------------ Summary: Upgrade to Aesh 0.59 (was: Upgrade to Aesh 0.58) > 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.1.0.Final, 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.11#6341) From issues at jboss.org Tue Mar 24 04:40:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 04:40:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-646) Error dialog window not being displayed In-Reply-To: References: Message-ID: Gary Brown created RTGOV-646: -------------------------------- Summary: Error dialog window not being displayed Key: RTGOV-646 URL: https://issues.jboss.org/browse/RTGOV-646 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta2 When an error occurs, or feedback is required, it is not being displayed in the UI. This appears to have stopped working when the change from GWT RPC to standard REST API calls was made. For example, if a resubmit fails it does not display the error. But also when bulk resubmit is performed, it used to display stats on how many resubmits and how many failed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 07:47:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 07:47:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-646) Error dialog window not being displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-646: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/280 > Error dialog window not being displayed > --------------------------------------- > > Key: RTGOV-646 > URL: https://issues.jboss.org/browse/RTGOV-646 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > When an error occurs, or feedback is required, it is not being displayed in the UI. This appears to have stopped working when the change from GWT RPC to standard REST API calls was made. > For example, if a resubmit fails it does not display the error. But also when bulk resubmit is performed, it used to display stats on how many resubmits and how many failed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 07:47:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 07:47:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-646) Error dialog window not being displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-646. ------------------------------ Resolution: Done > Error dialog window not being displayed > --------------------------------------- > > Key: RTGOV-646 > URL: https://issues.jboss.org/browse/RTGOV-646 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > When an error occurs, or feedback is required, it is not being displayed in the UI. This appears to have stopped working when the change from GWT RPC to standard REST API calls was made. > For example, if a resubmit fails it does not display the error. But also when bulk resubmit is performed, it used to display stats on how many resubmits and how many failed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 07:50:21 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 07:50:21 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-647) Resubmit parent not defined when using batch resubmit In-Reply-To: References: Message-ID: Gary Brown created RTGOV-647: -------------------------------- Summary: Resubmit parent not defined when using batch resubmit Key: RTGOV-647 URL: https://issues.jboss.org/browse/RTGOV-647 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta2 Individual resubmission sets up reference to be used in case failures occur, so any new Situations that are created will refer back to it. The same does not appear to occur for batch resubmission. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 08:10:19 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 08:10:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-647) Resubmit parent not defined when using batch resubmit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-647: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/281 > Resubmit parent not defined when using batch resubmit > ----------------------------------------------------- > > Key: RTGOV-647 > URL: https://issues.jboss.org/browse/RTGOV-647 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Individual resubmission sets up reference to be used in case failures occur, so any new Situations that are created will refer back to it. The same does not appear to occur for batch resubmission. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 08:10:20 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 08:10:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-647) Resubmit parent not defined when using batch resubmit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-647. ------------------------------ Resolution: Done > Resubmit parent not defined when using batch resubmit > ----------------------------------------------------- > > Key: RTGOV-647 > URL: https://issues.jboss.org/browse/RTGOV-647 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Individual resubmission sets up reference to be used in case failures occur, so any new Situations that are created will refer back to it. The same does not appear to occur for batch resubmission. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 08:11:18 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 08:11:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-648) Error notification displayed after doing batch delete but still seems to work In-Reply-To: References: Message-ID: Gary Brown created RTGOV-648: -------------------------------- Summary: Error notification displayed after doing batch delete but still seems to work Key: RTGOV-648 URL: https://issues.jboss.org/browse/RTGOV-648 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Notification shows error, but deletion appears to work fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 08:54:18 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 08:54:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-647) Resubmit parent not defined when using batch resubmit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-647: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/281, https://github.com/Governance/rtgov/pull/282 (was: https://github.com/Governance/rtgov/pull/281) > Resubmit parent not defined when using batch resubmit > ----------------------------------------------------- > > Key: RTGOV-647 > URL: https://issues.jboss.org/browse/RTGOV-647 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Individual resubmission sets up reference to be used in case failures occur, so any new Situations that are created will refer back to it. The same does not appear to occur for batch resubmission. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 10:01:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 24 Mar 2015 10:01:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-656. ------------------------------- Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 Resolution: Done > 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.1.0.Final, 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.11#6341) From issues at jboss.org Tue Mar 24 11:48:18 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 11:48:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-648) Error notification displayed after doing batch delete but still seems to work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-648: ----------------------------- Fix Version/s: 2.1.0.Beta2 Git Pull Request: https://github.com/Governance/rtgov/pull/283 > Error notification displayed after doing batch delete but still seems to work > ----------------------------------------------------------------------------- > > Key: RTGOV-648 > URL: https://issues.jboss.org/browse/RTGOV-648 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Notification shows error, but deletion appears to work fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 11:48:18 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 24 Mar 2015 11:48:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-648) Error notification displayed after doing batch delete but still seems to work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-648. ------------------------------ Resolution: Done > Error notification displayed after doing batch delete but still seems to work > ----------------------------------------------------------------------------- > > Key: RTGOV-648 > URL: https://issues.jboss.org/browse/RTGOV-648 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Notification shows error, but deletion appears to work fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Mar 24 15:48:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 24 Mar 2015 15:48:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-662) Upgrade to Aesh 0.59 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-662. ------------------------------- Resolution: Done > 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.1.0.Final, 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.11#6341) From issues at jboss.org Wed Mar 25 11:02:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 11:02:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-260. ------------------------------- Resolution: Done > 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.1.0.Final > > > 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.11#6341) From issues at jboss.org Wed Mar 25 14:58:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 14:58:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-664: --------------------------------- Summary: Queries with relationship predicates fail on EAP 6.2-6.4 Key: ARTIF-664 URL: https://issues.jboss.org/browse/ARTIF-664 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Example: /s-ramp[expandedFromDocument] JCR-SQL2: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE artifact1.[jcr:uuid] IN (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC {code} The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 14:58:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 14:58:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-664: ------------------------------ Description: Example: {code} /s-ramp[expandedFromDocument] {code} JCR-SQL2: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE artifact1.[jcr:uuid] IN (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC {code} The query simply returns nothing. Works perfectly for Wildfly 8 was: Example: /s-ramp[expandedFromDocument] JCR-SQL2: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE artifact1.[jcr:uuid] IN (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC {code} The query simply returns nothing. Works perfectly for Wildfly 8 > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 15:30:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 15:30:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053455#comment-13053455 ] Brett Meyer commented on ARTIF-664: ----------------------------------- [~rhauch] & [~hchiorean], I know I've been bothering you guys a lot -- apologies! In the thick of beta testing... Is there anything obvious in that query that wouldn't be supported by 3.8.1? It works great on 4.0. I've narrowed down the specific commit that broke the relationship support, and that query structure is the only runtime delta. I've been looking through JIRAs, etc. and can't find anything that sticks out. > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 15:31:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 15:31:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-664: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 15:39:18 2015 From: issues at jboss.org (Horia Chiorean (JIRA)) Date: Wed, 25 Mar 2015 15:39:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053460#comment-13053460 ] Horia Chiorean commented on ARTIF-664: -------------------------------------- [~brmeyer]: the query engine (not necessarily the query parser) is radically different between ModeShape 3 and ModeShape 4: ModeShape 3 uses Lucene & Hibernate search, ModeShape 4 uses a custom, in-house query engine. If you can build a test case we can run locally in ModeShape 3.x (even if it uses artificer CND but with actual nodes & values) to reproduce the issue, feel free to log a BZ and we'll investigate this for DV 6.2. You can look at our [query tests|https://github.com/ModeShape/modeshape/blob/3.x/modeshape-jcr/src/test/java/org/modeshape/jcr/JcrQueryManagerTest.java] for such examples. > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 15:49:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 15:49:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-634. ----------------------------- Resolution: Out of Date > Automate Keycloak setup during integration tests > ------------------------------------------------ > > Key: ARTIF-634 > URL: https://issues.jboss.org/browse/ARTIF-634 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: > - Automate the realm import > - Automate the EAP/Wildfly admin user password > - Re-enable the server install/configure ant tasks > - Re-enable Jenkins integration test jobs > - Add job for Wildfly -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 16:00:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:00:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-202: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 > 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) From issues at jboss.org Wed Mar 25 16:01:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:01:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-140: ------------------------------ Fix Version/s: 1.1.0.Final > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.1.0.Final > > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 16:01:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:01:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-117) Add caching of ontologies to JCR persistence layer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-117. ----------------------------- Resolution: Won't Fix > Add caching of ontologies to JCR persistence layer > -------------------------------------------------- > > Key: ARTIF-117 > URL: https://issues.jboss.org/browse/ARTIF-117 > Project: Artificer > Issue Type: Task > Components: Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > The getOntologies method should return a cached version of the ontologies rather than reading the JCR nodes each time. The cache should be invalidated when ontology nodes are changed. This can be done by hooking into the JCR eventing feature. The eventing feature of JCR may or may not be supported by the JCR impl - so only cache if eventing is available. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 16:02:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:02:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-16: ----------------------------- Fix Version/s: 1.1.0.Final > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: ARTIF-16 > URL: https://issues.jboss.org/browse/ARTIF-16 > Project: Artificer > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0.Final > Reporter: Kurt Stam > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > Attachments: UIMockup.gliffy, UImockup.gliffy > > > Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful. > One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 16:02:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:02:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-502) Upgrade arquillian-tomcat-managed-7 to 1.0.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-502. ----------------------------- Resolution: Out of Date > Upgrade arquillian-tomcat-managed-7 to 1.0.0.Final > -------------------------------------------------- > > Key: ARTIF-502 > URL: https://issues.jboss.org/browse/ARTIF-502 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Once arquillian-tomcat-managed-7 1.0.0.Final is out, upgrade it in s-ramp-test. (If SRAMP-431 is not yet merged, update brmeyer's integration-test branch.) > Note that the following line can then be removed in arquillian.xml: > target/apache-tomcat-7.0.54 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Mar 25 16:03:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:03:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-324) UI: Edit artifact relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 25 16:03:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:03:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-311) Add support for comments associated with an Artifact In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 25 16:09:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:09:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-571) Support stored queries in UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 25 16:17:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 16:17:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 25 17:04:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 17:04:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Mar 25 17:04:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 17:04:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053480#comment-13053480 ] 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) From issues at jboss.org Wed Mar 25 17:07:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 17:07:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053481#comment-13053481 ] 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) From issues at jboss.org Wed Mar 25 17:49:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 17:49:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053486#comment-13053486 ] 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) From issues at jboss.org Wed Mar 25 17:50:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 25 Mar 2015 17:50:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Thu Mar 26 09:49:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 09:49:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-665) Add additional Tika text extractors for full-text searching In-Reply-To: References: Message-ID: 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) From issues at jboss.org Thu Mar 26 10:08:19 2015 From: issues at jboss.org (Christian Sadilek (JIRA)) Date: Thu, 26 Mar 2015 10:08:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053672#comment-13053672 ] Christian Sadilek commented on ARTIF-659: ----------------------------------------- Hi, I definitely recommend upgrading to Errai 3.1.2.Final or higher and GWT 2.7. You will get lots of performance improvements (faster refreshes) and the new SuperDevMode and incremental compiler. Also, it will set you up for upgrading to GWT 2.8 when it's ready. Then you can use Java 8 Lambdas on the client. > 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) From issues at jboss.org Thu Mar 26 12:03:24 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 12:03:24 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-666) Experiment with ModeShape's "score" capability to rank results by relevancy In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-666: --------------------------------- Summary: Experiment with ModeShape's "score" capability to rank results by relevancy Key: ARTIF-666 URL: https://issues.jboss.org/browse/ARTIF-666 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Mar 26 12:06:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 12:06:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-667) Allow search results to be exported (CSV, etc.) In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-667: --------------------------------- Summary: Allow search results to be exported (CSV, etc.) Key: ARTIF-667 URL: https://issues.jboss.org/browse/ARTIF-667 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Mar 26 13:05:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 13:05:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-668) Upgrade to Errai 3.1 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-668: --------------------------------- Summary: Upgrade to Errai 3.1 Key: ARTIF-668 URL: https://issues.jboss.org/browse/ARTIF-668 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) From issues at jboss.org Thu Mar 26 13:07:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 13:07:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: 1.0.0.Alpha2 > 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.1.0.Final, 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.11#6341) From issues at jboss.org Thu Mar 26 16:12:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 16:12:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-659. ----------------------------- Resolution: Won't Fix > 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) From issues at jboss.org Thu Mar 26 16:12:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 16:12:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053804#comment-13053804 ] Brett Meyer commented on ARTIF-659: ----------------------------------- Thanks Christian. Upgraded Errai in ARTIF-668. But, it looks like GWT won't support Java 8 until at least GWT 3.0. Closing this, for now... > 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) From issues at jboss.org Thu Mar 26 16:14:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 16:14:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-668) Upgrade to Errai 3.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-668. ------------------------------- Resolution: Done > Upgrade to Errai 3.1 > -------------------- > > Key: ARTIF-668 > URL: https://issues.jboss.org/browse/ARTIF-668 > 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) From issues at jboss.org Thu Mar 26 16:14:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 16:14:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-668) Upgrade to Errai 3.1.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-668: ------------------------------ Summary: Upgrade to Errai 3.1.2 (was: Upgrade to Errai 3.1) > Upgrade to Errai 3.1.2 > ---------------------- > > Key: ARTIF-668 > URL: https://issues.jboss.org/browse/ARTIF-668 > 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) From issues at jboss.org Thu Mar 26 17:29:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 17:29:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-324) UI: Edit artifact relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053822#comment-13053822 ] Brett Meyer commented on ARTIF-324: ----------------------------------- One other idea for the UI: utilize the full artifacts view to select relationship targets. If editing an artifact, presumably they're be a create relationships area with an "add targets" button. When hit, it sets the entire UI in an "editing relationship X" state. All search results would have an "Add Target" link next to them. At the top, have a "Finished Adding Targets" button that goes back to artifact details. This seems a bit convoluted, but I'd like to have the entire range and benefits of the artifact filters available. Rather than reproduce, simply re-use. > 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) From issues at jboss.org Thu Mar 26 17:42:18 2015 From: issues at jboss.org (Christian Sadilek (JIRA)) Date: Thu, 26 Mar 2015 17:42:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053825#comment-13053825 ] Christian Sadilek commented on ARTIF-659: ----------------------------------------- Where did you get that info from? I think that's outdated. To my knowledge 2.8 will have support for Java 8. In fact, you can already use a JDK8 now as long as you don't use features that won't translate to JS. > 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) From issues at jboss.org Thu Mar 26 22:57:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 22:57:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053856#comment-13053856 ] Brett Meyer commented on ARTIF-659: ----------------------------------- [~csa], compilation flat out failed early -- the error message stated that GWT 2.7 requires the 1.6 or 1.7 compiler. I had read a few reports saying that Java 8 support was slated for GWT 3, but hadn't heard about 2.8. I'll keep an eye on it... > 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) From issues at jboss.org Thu Mar 26 22:57:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Mar 2015 22:57:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-659) Test and support Java 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reopened ARTIF-659: ------------------------------- > 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) From issues at jboss.org Fri Mar 27 11:35:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Mar 2015 11:35:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-645) Allow users to supply extensions through a new plugin architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054086#comment-13054086 ] Brett Meyer commented on ARTIF-645: ----------------------------------- In a demo with Teiid/JDV, they had a great thought about why this would be important. It would allow extensions to provide their own JCR CNDs and configurations for existing, external data sources. The custom contract implementations would know what to do with the data, providing integration with Artificer without having to port all artifacts into Artificer-specific models. > Allow users to supply extensions through a new plugin architecture > ------------------------------------------------------------------ > > Key: ARTIF-645 > URL: https://issues.jboss.org/browse/ARTIF-645 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: > - extension contract impls (ArtifactBuilder, TypeDetector, etc.) > - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] > - UI elements (custom metadata displays, custom actions, etc.) > - endpoint bindings (again, /s-ramp/model/type) > Eric's demo: https://bluejeans.com/s/82tW/ -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Mar 27 11:51:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Mar 2015 11:51:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-664: ------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha2) > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Beta1 > > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 30 09:48:19 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 30 Mar 2015 09:48:19 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-669) Document bulk operations through S-RAMP archives In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-669: --------------------------------- Summary: Document bulk operations through S-RAMP archives Key: ARTIF-669 URL: https://issues.jboss.org/browse/ARTIF-669 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final, 1.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 30 10:05:20 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 30 Mar 2015 10:05:20 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-657) updateContent may not be recreating relationships correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054561#comment-13054561 ] Brett Meyer commented on ARTIF-657: ----------------------------------- Idea: add a config option and/or a new API method that would allow updates/deletes with an automatic *orphan* (relationships, derived artifacts, etc.) removal. But by default, continue to block. > updateContent may not be recreating relationships correctly > ----------------------------------------------------------- > > Key: ARTIF-657 > URL: https://issues.jboss.org/browse/ARTIF-657 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > 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.11#6341) From issues at jboss.org Mon Mar 30 17:34:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 30 Mar 2015 17:34:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-670) Support both "Move to Trash" and "Permanently Delete" In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-670: --------------------------------- Summary: Support both "Move to Trash" and "Permanently Delete" Key: ARTIF-670 URL: https://issues.jboss.org/browse/ARTIF-670 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Use deleteArtifact, in its current form, as "move to trash" (and state so on the interfaces). Add in a way to permanently delete an artifact. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 30 21:07:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 30 Mar 2015 21:07:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-671) Add relationships filter to UI artifacts view In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-671: --------------------------------- Summary: Add relationships filter to UI artifacts view Key: ARTIF-671 URL: https://issues.jboss.org/browse/ARTIF-671 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Mar 30 21:17:18 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 30 Mar 2015 21:17:18 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-672) UI: Edit Ontology dialog for entire ontology In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-672: --------------------------------- Summary: UI: Edit Ontology dialog for entire ontology Key: ARTIF-672 URL: https://issues.jboss.org/browse/ARTIF-672 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final Currently, only the individual nodes can be edited. Allow the entire ontology to be edited, including the namespace. See AddOntologyDialog -- This message was sent by Atlassian JIRA (v6.3.11#6341)