October 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-106) Support S-RAMP classifications

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-106?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-106. ----------------------------- Fix Version/s: 0.1.0 - Milestone 3 (Workflow and Relationships) Resolution: Done > Support S-RAMP classifications > ------------------------------ > > Key: SRAMP-106 > URL: https://issues.jboss.org/browse/SRAMP-106 > Project: S-RAMP > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.1.0 - Milestone 3 (Workflow and Relationships) > > > This is a parent task for all of the individual bits of work needed to be done related to supporting S-RAMP classifications. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-94) Handle fine-grained Atom view for relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-94?page=com.atlassian.jira.plugin.s... ] Brett Meyer commented on SRAMP-94: ---------------------------------- Converting to separate Feature Request. Fine-grained views are optional in the spec. > Handle fine-grained Atom view for relationships > ----------------------------------------------- > > Key: SRAMP-94 > URL: https://issues.jboss.org/browse/SRAMP-94 > Project: S-RAMP > Issue Type: Feature Request > Components: Atom Binding > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > Relationships have their own separate Atom API endpoints. For example, you can get a feed of just the relationships for an artifact. In addition, you cn add (and I believe delete) individual relationships directly via this mechanism. This task should probably result in a new RelationshipResource RESTEasy class. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-94) Handle fine-grained Atom view for relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-94?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-94: ----------------------------- Parent: (was: SRAMP-90) Issue Type: Feature Request (was: Sub-task) > Handle fine-grained Atom view for relationships > ----------------------------------------------- > > Key: SRAMP-94 > URL: https://issues.jboss.org/browse/SRAMP-94 > Project: S-RAMP > Issue Type: Feature Request > Components: Atom Binding > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > Relationships have their own separate Atom API endpoints. For example, you can get a feed of just the relationships for an artifact. In addition, you cn add (and I believe delete) individual relationships directly via this mechanism. This task should probably result in a new RelationshipResource RESTEasy class. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-110) Implement fine-grained classification view in the Atom API

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-110?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-110: ----------------------------------- Converting to separate Feature Request. Fine-grained views are optional in the spec. > Implement fine-grained classification view in the Atom API > ---------------------------------------------------------- > > Key: SRAMP-110 > URL: https://issues.jboss.org/browse/SRAMP-110 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > The spec defines fine-grained views, including one for the classifications. This allows clients to get a manipulate (add, delete, get feed) the classifications for an artifact in the S-RAMP repository directly, removing the need to deal with the whole artifact at once. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-110) Implement fine-grained classification view in the Atom API

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-110?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-110: ------------------------------ Parent: (was: SRAMP-106) Issue Type: Feature Request (was: Sub-task) > Implement fine-grained classification view in the Atom API > ---------------------------------------------------------- > > Key: SRAMP-110 > URL: https://issues.jboss.org/browse/SRAMP-110 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > The spec defines fine-grained views, including one for the classifications. This allows clients to get a manipulate (add, delete, get feed) the classifications for an artifact in the S-RAMP repository directly, removing the need to deal with the whole artifact at once. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-167?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-167: ------------------------------ Fix Version/s: 0.7.0.Final > Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc) > ------------------------------------------------------------------------------------- > > Key: SRAMP-167 > URL: https://issues.jboss.org/browse/SRAMP-167 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a document). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-167?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-167. ------------------------------- Resolution: Done "Completed", with the caveat that the pull request has several TODOs due to issues with the spec schemas. Once those have been addressed with S-RAMP 1.1 (hopefully), re-visit. > Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc) > ------------------------------------------------------------------------------------- > > Key: SRAMP-167 > URL: https://issues.jboss.org/browse/SRAMP-167 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > > We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a document). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-167?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-167: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/500 > Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc) > ------------------------------------------------------------------------------------- > > Key: SRAMP-167 > URL: https://issues.jboss.org/browse/SRAMP-167 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > > We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a document). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-544) SNAPSHOT artifacts can no longer be pulled from S-RAMP

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-544?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-544: ----------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1146617|https://bugzilla.redhat.com/show_bug.cgi?id=1146617] from NEW to MODIFIED > SNAPSHOT artifacts can no longer be pulled from S-RAMP > ------------------------------------------------------ > > Key: SRAMP-544 > URL: https://issues.jboss.org/browse/SRAMP-544 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Critical > Fix For: 0.6.0.Final > > > If a project uses the Wagon or facade as a dependency repo, SRAMP-507 breaks the ability to pull SNAPSHOT artifacts. Since we append the timestamp, simply using the original GAV no longer works. To duplicate, run the new multimodule webapp demo. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-117) Pull Fabric profile tasks out of overlord-commons-dist-fuse6 and into a new overlord-commons-dist-fabric-profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-117?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on OVERLORD-117: -------------------------------------------------- Brett Meyer <brmeyer(a)redhat.com> changed the Status of [bug 1146591|https://bugzilla.redhat.com/show_bug.cgi?id=1146591] from NEW to MODIFIED > Pull Fabric profile tasks out of overlord-commons-dist-fuse6 and into a new overlord-commons-dist-fabric-profile > ---------------------------------------------------------------------------------------------------------------- > > Key: OVERLORD-117 > URL: https://issues.jboss.org/browse/OVERLORD-117 > Project: Overlord > Issue Type: Task > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Similar to S-RAMP, DTGov, and RTGov, pull the Fabric profiles into a separate dist within overlord-commons. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2014