August 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-691) Create an S-RAMP import/export utility

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-691?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-691. ----------------------------- Resolution: Out of Date > Create an S-RAMP import/export utility > -------------------------------------- > > Key: ARTIF-691 > URL: https://issues.jboss.org/browse/ARTIF-691 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > > Create an Atom API client utility that allows import/export between S-RAMP implementations. This will be helpful in general. But currently important, it will allow migration to the new backend. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-697) Support Gluster for file storage

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-697?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-697: ------------------------------ Parent: (was: ARTIF-695) Issue Type: Feature Request (was: Sub-task) > Support Gluster for file storage > -------------------------------- > > Key: ARTIF-697 > URL: https://issues.jboss.org/browse/ARTIF-697 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-696) Support Ceph for file storage

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-696?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-696: ------------------------------ Parent: (was: ARTIF-695) Issue Type: Feature Request (was: Sub-task) > Support Ceph for file storage > ----------------------------- > > Key: ARTIF-696 > URL: https://issues.jboss.org/browse/ARTIF-696 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.s... ] Brett Meyer commented on ARTIF-16: ---------------------------------- Work in progress: https://github.com/brmeyer/s-ramp/tree/ide. Needs switched to an approach similar to https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts > 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 > 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.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-214) When uploading a jar - include the output of jar tvf as metadata

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-214: ----------------------------------- I take part of that back. Instead, after ARTIF-694, parse the output and include as additional metadata on the java artifact, but it's probably better to use multiple fields. > When uploading a jar - include the output of jar tvf as metadata > ---------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > > 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 tvf and include as artifact metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-214) When uploading a jar - include the output of jar tvf as metadata

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-214: ------------------------------ Description: 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 tvf and include as artifact metadata (was: 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 tvf > jar-content.txt file and upload that to s-ramp too) > When uploading a jar - include the output of jar tvf as metadata > ---------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > > 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 tvf and include as artifact metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-214) When uploading a jar - include the output of jar tvf as metadata

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-214: ------------------------------ Summary: When uploading a jar - include the output of jar tvf as metadata (was: When uploading a jar - upload a text file with the output of jar tvf) > When uploading a jar - include the output of jar tvf as metadata > ---------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > > 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 tvf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-306) Make Artifact Details page consistent with dtgov Deployment Details page

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-306?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-306. ----------------------------- Resolution: Out of Date > Make Artifact Details page consistent with dtgov Deployment Details page > ------------------------------------------------------------------------ > > Key: ARTIF-306 > URL: https://issues.jboss.org/browse/ARTIF-306 > Project: Artificer > Issue Type: Enhancement > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > > The deployment details page in dtgov-ui uses links to additional pages rather than tabs for things like Deployment History and Deployment Contents. We should change the Artifact Details to take the same approach. I'd like to minimize tabs if possible. > This should simplify the Artifact Details page implementation a lot, but removing the tab logic (e.g. the source and history tabs). It should also make it easier to create mobile versions and IE compatible versions (IE sometimes has issues with the tabs). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-706) Create DerivedExtendedArtifactType

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-706?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-706: ------------------------------ Parent: ARTIF-694 Issue Type: Sub-task (was: Feature Request) > Create DerivedExtendedArtifactType > ---------------------------------- > > Key: ARTIF-706 > URL: https://issues.jboss.org/browse/ARTIF-706 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > > Having "relatedDocument" in an artifact's relationships list requires some stupid logic to deal with (see ArtifactVerifier#verifyNames). Instead, we should rely solely on the real #relatedDocument field. Unfortunately, that's only on DerivedArtifactType. If a derived artifact is an *extended* artifact, there's no access to that field, hence the need to use the general relationship. Re-work that structure to be more useful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-694) Create a new data model

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-694?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-694: ------------------------------ Summary: Create a new data model (was: Create a new data model for restful services) > Create a new data model > ----------------------- > > Key: ARTIF-694 > URL: https://issues.jboss.org/browse/ARTIF-694 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2015