July 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf

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

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tvf

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 > jar-content.txt file and upload that to s-ramp too (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 tf > jar-content.txt file and upload that to s-ramp too) > When uploading a jar - upload a text file with the output of jar tvf > -------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-214) When uploading a jar - upload a text file with the output of jar tf

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 - upload a text file with the output of jar tf (was: When uploading a jar - upload a text file with the output of jar tv) > When uploading a jar - upload a text file with the output of jar tf > ------------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > Assignee: Brett Meyer > > 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 tf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-23) Statically validate a parsed S-RAMP Query

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-23?page=com.atlassian.jira.plugin.s... ] Brett Meyer commented on ARTIF-23: ---------------------------------- I'd argue that this may be better built into the grammar parser itself, paired with adequate/unique Exception messages. > Statically validate a parsed S-RAMP Query > ----------------------------------------- > > Key: ARTIF-23 > URL: https://issues.jboss.org/browse/ARTIF-23 > Project: Artificer > Issue Type: Feature Request > Components: Core > Affects Versions: 0.6.0.Final > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > Implement a validator that can take an S-RAMP Query and ensure that it is valid (does not violate any of the restrictions imposed by the S-RAMP Query API specification). > The result should simply be a validator that accepts a parsed S-RAMP Query and throws an exception if the Query is invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-648) New artifact type: DDL

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-648?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-648: ----------------------------------- Initially, keep it simple. 2 extended types: SQLScript DDLSQLScript (assume this is the case if any 'create table' exists) > New artifact type: DDL > ---------------------- > > Key: ARTIF-648 > URL: https://issues.jboss.org/browse/ARTIF-648 > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-670) Support "forced deletes" (no constraint checks) in the UIs

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-670?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-670: ------------------------------ Summary: Support "forced deletes" (no constraint checks) in the UIs (was: Support both "Move to Trash" and "Permanently Delete" in the UIs) > Support "forced deletes" (no constraint checks) in the UIs > ---------------------------------------------------------- > > Key: ARTIF-670 > URL: https://issues.jboss.org/browse/ARTIF-670 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > ARTIF-678 created "forced deletes". Once role-based access is in place (ARTIF-163), support the capability in the UIs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-741) Automatically create "deployment" artifacts from Wildfly events (DMR or MBean)

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-741: --------------------------------- Summary: Automatically create "deployment" artifacts from Wildfly events (DMR or MBean) Key: ARTIF-741 URL: https://issues.jboss.org/browse/ARTIF-741 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-740) Automatically create "deployment" artifacts from Fabric8 events

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-740: --------------------------------- Summary: Automatically create "deployment" artifacts from Fabric8 events Key: ARTIF-740 URL: https://issues.jboss.org/browse/ARTIF-740 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-675) Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-675: ------------------------------ Description: Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits) - "Deployment" - "RESTFulApplication" was: Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits) > Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" > ------------------------------------------------------------------------------------ > > Key: ARTIF-675 > URL: https://issues.jboss.org/browse/ARTIF-675 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. > Ideas (from various sources): > - Provides a catalog of information, what services exist and are available for use > - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. > - Provides information about the version of the services > - Allows you to record and retrieve multiple versions of the same service > - Allows you to dynamically refer to the latest version of the service > - Allows dynamically at runtime to search and select end-point chosen service > - Collects information who and what services are used > - Provides information that services are repeatedly used and which are not > - Determining the impact of changes the services to existing dependent services > - Providing information to consumers of the services about ongoing or planned changes to of the services > - Identify the environments (OS, app server, etc.) supported by the artifact > - Differentiate between front and back end artifacts > - Security: what version of SSL is used, etc. (extremely valuable for security audits) > - "Deployment" > - "RESTFulApplication" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-739) Upgrade Keycloak to 1.3.x

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-739: --------------------------------- Summary: Upgrade Keycloak to 1.3.x Key: ARTIF-739 URL: https://issues.jboss.org/browse/ARTIF-739 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 -- 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