July 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-140) Create unit tests for shell commands

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-140: ----------------------------------- We already fully cover (or should be fully covering) the Java client through integration tests. So for the CLI tests, I'm making them true *unit* tests by using Mockito to mock out the Java client and assert calls made to it. > 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.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-140) Create unit tests for shell commands

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-140: ----------------------------------- For now, use aesh-extension's AeshTestCommons as the backbone. See any of the extension command's tests for examples. > 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.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-225) CLI Query: option to print the next page in a query

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-225?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-225. ------------------------------- Fix Version/s: 1.1.0.Final Resolution: Done > CLI Query: option to print the next page in a query > --------------------------------------------------- > > Key: ARTIF-225 > URL: https://issues.jboss.org/browse/ARTIF-225 > Project: Artificer > Issue Type: Enhancement > Components: Shell > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > The CLI query command currently prints the first 100 items from the query results. It would be nice to have an option to show the next page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-225) CLI Query: option to print the next page in a query

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-225?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-225: ----------------------------------- Adding full paging support: {code} @Option(name = "startIndex", hasValue = true, required = false, description = "Paging: start index (begins at 0)") private Integer startIndex; @Option(name = "count", hasValue = true, required = false, description = "Paging: count (# to include on page)") private Integer count; @Option(name = "page", hasValue = true, required = false, description = "Paging: page # (assumes 0 startIndex and 100 count, unless startIndex/count provided now or in the past)") private Integer page; @Option(name = "orderBy", hasValue = true, required = false, description = "Sort by this field (defaults to uuid)", defaultValue = "uuid") private String orderBy; @Option(name = "ascending", hasValue = false, required = false, description = "Sort ascending (default)") private Boolean ascending; @Option(name = "descending", hasValue = false, required = false, description = "Sort descending") private Boolean descending; {code} > CLI Query: option to print the next page in a query > --------------------------------------------------- > > Key: ARTIF-225 > URL: https://issues.jboss.org/browse/ARTIF-225 > Project: Artificer > Issue Type: Enhancement > Components: Shell > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The CLI query command currently prints the first 100 items from the query results. It would be nice to have an option to show the next page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-225) CLI Query: option to print the next page in a query

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-225?page=com.atlassian.jira.plugin.... ] Work on ARTIF-225 started by Brett Meyer. ----------------------------------------- > CLI Query: option to print the next page in a query > --------------------------------------------------- > > Key: ARTIF-225 > URL: https://issues.jboss.org/browse/ARTIF-225 > Project: Artificer > Issue Type: Enhancement > Components: Shell > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The CLI query command currently prints the first 100 items from the query results. It would be nice to have an option to show the next page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-575: ----------------------------------- Just went with what I suggested on the spec: query/{queryName}/results?param1=value&param2=value > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > 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.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-575. ------------------------------- Fix Version/s: 1.1.0.Final Resolution: Done > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > > 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.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-518) dev-server 404's the UI root context

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-518?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-518: ------------------------------ Summary: dev-server 404's the UI root context (was: s-ramp-dev-server 404's the UI root context) > dev-server 404's the UI root context > ------------------------------------ > > Key: ARTIF-518 > URL: https://issues.jboss.org/browse/ARTIF-518 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Optional > Fix For: 1.1.0.Final > > > 404: http://localhost:8080/s-ramp-ui > works: http://localhost:8080/s-ramp-ui/index.html > Really, really low priority, but we could probably make the root context work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-518) s-ramp-dev-server 404's the UI root context

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-518?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-518. ------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) Fix Version/s: 1.1.0.Final Resolution: Done > s-ramp-dev-server 404's the UI root context > ------------------------------------------- > > Key: ARTIF-518 > URL: https://issues.jboss.org/browse/ARTIF-518 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Optional > Fix For: 1.1.0.Final > > > 404: http://localhost:8080/s-ramp-ui > works: http://localhost:8080/s-ramp-ui/index.html > Really, really low priority, but we could probably make the root context work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-750) Create artifact "Staging" concept

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-750: --------------------------------- Summary: Create artifact "Staging" concept Key: ARTIF-750 URL: https://issues.jboss.org/browse/ARTIF-750 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Similar to Nexus, allow artifact uploads to be staged (optionally) for inspection, prior to releasing. Staged artifacts could be dropped (deleted permanently), rather than trashing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues July 2015