April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-681) Versioning support

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-681?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-681: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Beta1 > Versioning support > ------------------ > > Key: ARTIF-681 > URL: https://issues.jboss.org/browse/ARTIF-681 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Beta1 > > > Tracker for adding proper OOTB "versioning" support to the server and all interfaces -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-541) Tighten the restrictions on artifact content updates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-541?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-541: ----------------------------------- All, FYI, please see the discussion on ARTIF-657, most notably: {quote} In the end, I think I'm going to go back to completely disabling updateContent. First off, there are numerous technical challenges with that approach. Secondly, and most importantly, I think it's detrimental to what we're trying to accomplish. Instead, ARTIF-679 will add numerous capabilities to auditing and ARTIF-681 will add full-blown artifact versioning. Note that ARTIF-678 added a "force delete" option that helps in some edge cases. {quote} updateContent should be removed. Instead, focus on fully supporting auditing and versioning, OOTB. > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: ARTIF-541 > URL: https://issues.jboss.org/browse/ARTIF-541 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-657) Remove updateContent capability

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-657: ----------------------------------- In the end, I think I'm going to go back to completely disabling updateContent. First off, there are numerous technical challenges with that approach. Secondly, and most importantly, I think it's detrimental to what we're trying to accomplish. Instead, ARTIF-679 will add numerous capabilities to auditing and ARTIF-681 will add full-blown artifact versioning. Note that ARTIF-678 added a "force delete" option that helps in some edge cases. > Remove updateContent capability > ------------------------------- > > 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.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-325) Actions - Add new version of artifact

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-325?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-325: ------------------------------ Parent: ARTIF-681 Issue Type: Sub-task (was: Task) > Actions - Add new version of artifact > -------------------------------------- > > Key: ARTIF-325 > URL: https://issues.jboss.org/browse/ARTIF-325 > Project: Artificer > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > We need a separate gesture in the UI for uploading a new version of an existing artifact. This should probably happen from the artifact details page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-681) Versioning support

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-681?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-681: ------------------------------ Description: Tracker for adding proper OOTB "versioning" support to the server and all interfaces > Versioning support > ------------------ > > Key: ARTIF-681 > URL: https://issues.jboss.org/browse/ARTIF-681 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Tracker for adding proper OOTB "versioning" support to the server and all interfaces -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-681) Versioning support

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-681: --------------------------------- Summary: Versioning support Key: ARTIF-681 URL: https://issues.jboss.org/browse/ARTIF-681 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-657) Remove updateContent capability

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-657: ------------------------------ Summary: Remove updateContent capability (was: updateContent may not be recreating relationships correctly) > Remove updateContent capability > ------------------------------- > > 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.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-680) Audit relationship changes

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-680: --------------------------------- Summary: Audit relationship changes Key: ARTIF-680 URL: https://issues.jboss.org/browse/ARTIF-680 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Audit relationship changes on an artifact, including in the reverse -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-313) Implement Audit History page

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-313?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-313: ------------------------------ Parent: ARTIF-679 Issue Type: Sub-task (was: Feature Request) > Implement Audit History page > ---------------------------- > > Key: ARTIF-313 > URL: https://issues.jboss.org/browse/ARTIF-313 > Project: Artificer > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Implement the Audit History (Activity Stream?) page for artifacts in the s-ramp ui. It should be a page that hangs off of the artifact details page and shows the same content that we currently show in the dtgov ui for deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-679) Complete the auditing capabilities

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-679: --------------------------------- Summary: Complete the auditing capabilities Key: ARTIF-679 URL: https://issues.jboss.org/browse/ARTIF-679 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer This tracks several steps needed to "fully complete" the auditing capability, including making it useful across all interfaces. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2015