February 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-584) Test and document Nexus Proxy support

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-584?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-584. ----------------------------- Fix Version/s: (was: 1.0.0.Alpha1) Resolution: Won't Fix This may not be possible, since Nexus does not appear to support sending basic auth on its GET requests. > Test and document Nexus Proxy support > ------------------------------------- > > Key: ARTIF-584 > URL: https://issues.jboss.org/browse/ARTIF-584 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > > Once the Facade is "finished", verify that it can be used as a Nexus Proxy. Then, document this use case: "gain S-RAMP without losing your existing enterprise repo!" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-646) Protect Maven Facade servlet

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-646?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-646. ------------------------------- Resolution: Done > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-396: ------------------------------ Description: 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/... was: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 > 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/... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 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 reassigned ARTIF-140: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Sub-task > 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)

9 years, 10 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 updated ARTIF-140: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Feature Request) > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: David virgil naranjo > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-396: ------------------------------ Description: 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 (was: This task is composed of a set of subtask that will improve the new aesh shell console. Some existing bugs will be fixed. Some new features to the existing commands will be added. Some new commands will be added.) > 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 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-396: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > 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: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > This task is composed of a set of subtask that will improve the new aesh shell console. > Some existing bugs will be fixed. > Some new features to the existing commands will be added. > Some new commands will be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.... ] Brett Meyer reassigned ARTIF-396: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > 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 > > > This task is composed of a set of subtask that will improve the new aesh shell console. > Some existing bugs will be fixed. > Some new features to the existing commands will be added. > Some new commands will be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-396: ------------------------------ Summary: Re-work the Artificer CLI (was: S-RAMP Shell improvements and new capabilities) > 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: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > This task is composed of a set of subtask that will improve the new aesh shell console. > Some existing bugs will be fixed. > Some new features to the existing commands will be added. > Some new commands will be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-465) Investigate alternative methods for relationship resolution

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-465?page=com.atlassian.jira.plugin.... ] Brett Meyer edited comment on ARTIF-465 at 2/9/15 11:37 AM: ------------------------------------------------------------ Relevant (from the S-RAMP spec): 2.3.5.3.1 Resolving Internal References Some documents have dependencies on other documents. From our earlier scenario, a WSDL document might import an XSD document. When the WSDL document was published to the repository, the XSD document would have been published as well, but the original WSDL document published would not typically have the correct import statement to reference the XSD file which is actually persisted in the repository. More likely, it would be a local reference based on the development environment from which both files originated. It is important that the repository support the capability for tooling to resolve these dependencies to the correct version of the document which is actually published in the repository. S-RAMP provides two implementation choices for achieving this. Compliant implementations SHALL support at least one of them. 1. When returning a requested document, the repository MAY dynamically re-write the document’s references to other documents to correctly reference the appropriate file(s) stored in the repository. The actual document stored in the repository is unaffected. Only the serialized content returned in a GET is altered as the content is returned. 2. When the URL of a document containing dependent links is requested, the repository MAY instead redirect to another URL of its own creation, against which all relative path references to dependent documents will resolve properly with the redirected URL as a base. S-RAMP does not describe how such an implementation is done, only the REQUIRED behavior when implementations choose to support this option. Regardless of which option is implemented, its activation is achieved by adding the type=relative query string to the URL in the request (a sample URL format is shown here): /s-ramp/<artifactModel>/<artifactType>/{uuid:artifactDocument}/media?type=relative was (Author: brmeyer): Relevant (from the S-RAMP spec): 2.3.5.3.1 Resolving Internal References Some documents have dependencies on other documents. From our earlier scenario, a WSDL document might import an XSD document. When the WSDL document was published to the repository, the XSD document would have been published as well, but the original WSDL document published would not typically have the correct import statement to reference the XSD file which is actually persisted in the repository. More likely, it would be a local reference based on the development environment from which both files originated. It is important that the repository support the capability for tooling to resolve these dependencies to the correct version of the document which is actually published in the repository. S-RAMP provides two implementation choices for achieving this. Compliant implementations SHALL support at least one of them. When returning a requested document, the repository MAY dynamically re-write the document’s references to other documents to correctly reference the appropriate file(s) stored in the repository. The actual document stored in the repository is unaffected. Only the serialized content returned in a GET is altered as the content is returned. When the URL of a document containing dependent links is requested, the repository MAY instead redirect to another URL of its own creation, against which all relative path references to dependent documents will resolve properly with the redirected URL as a base. S-RAMP does not describe how such an implementation is done, only the REQUIRED behavior when implementations choose to support this option. Regardless of which option is implemented, its activation is achieved by adding the type=relative query string to the URL in the request (a sample URL format is shown here): /s-ramp/<artifactModel>/<artifactType>/{uuid:artifactDocument}/media?type=relative > Investigate alternative methods for relationship resolution > ----------------------------------------------------------- > > Key: ARTIF-465 > URL: https://issues.jboss.org/browse/ARTIF-465 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Investigate increased automatic artifact relationships (ie, service A depends on service B), useful for impact analysis. Possibly include Java-specific improvements, such as custom annotations (and scanning). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2015