July 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-737) Execute batch persist in single transaction

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-737?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-737. ------------------------------- Resolution: Done > Execute batch persist in single transaction > ------------------------------------------- > > Key: ARTIF-737 > URL: https://issues.jboss.org/browse/ARTIF-737 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > If any piece of a batch (and therefore, expanded archives, etc.) persist fails, the entire thing should be rolled back. Currently, each artifact in the batch is persisted in its own transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-732) Allow nested artifact expansion

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-732?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-732: ------------------------------ Description: Ex: A distro ZIP that contains multiple WARs. 1.) Do we want to allow those WARs to become primary artifacts? Currently, nested archives are not supported -- they'll be ignored. 2.) If yes to #1, any restrictions, or should that happen by default? 3.) If yes to #1, should those nested archives also be expanded themselves? My gut says "no" to all of them. But, if someone has a reason why nested archives should be supported, I'm all ears. was:Ex: Upload a dist ZIP which contains two WARs. Currently, the root ZIP will be the "expandedFromArchive" target for all artifacts, even the artifacts expanded from the WARs. Instead, ArtifactServiceImpl#upload should allow nested expansion, where each level of "expandedFromArchive" relationship creates an expansion chain. > Allow nested artifact expansion > ------------------------------- > > Key: ARTIF-732 > URL: https://issues.jboss.org/browse/ARTIF-732 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Ex: A distro ZIP that contains multiple WARs. 1.) Do we want to allow those WARs to become primary artifacts? Currently, nested archives are not supported -- they'll be ignored. 2.) If yes to #1, any restrictions, or should that happen by default? 3.) If yes to #1, should those nested archives also be expanded themselves? > My gut says "no" to all of them. But, if someone has a reason why nested archives should be supported, I'm all ears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-732) Allow nested archive expansion

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-732?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-732: ------------------------------ Summary: Allow nested archive expansion (was: Allow nested artifact expansion) > Allow nested archive expansion > ------------------------------ > > Key: ARTIF-732 > URL: https://issues.jboss.org/browse/ARTIF-732 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Ex: A distro ZIP that contains multiple WARs. 1.) Do we want to allow those WARs to become primary artifacts? Currently, nested archives are not supported -- they'll be ignored. 2.) If yes to #1, any restrictions, or should that happen by default? 3.) If yes to #1, should those nested archives also be expanded themselves? > My gut says "no" to all of them. But, if someone has a reason why nested archives should be supported, I'm all ears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-732) Allow nested artifact expansion

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-732?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-732: ------------------------------ Fix Version/s: (was: 1.0.0.Beta3) > Allow nested artifact expansion > ------------------------------- > > Key: ARTIF-732 > URL: https://issues.jboss.org/browse/ARTIF-732 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Ex: Upload a dist ZIP which contains two WARs. Currently, the root ZIP will be the "expandedFromArchive" target for all artifacts, even the artifacts expanded from the WARs. Instead, ArtifactServiceImpl#upload should allow nested expansion, where each level of "expandedFromArchive" relationship creates an expansion chain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-738) Make filesystem content storage the default

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-738?page=com.atlassian.jira.plugin.... ] Brett Meyer deleted ARTIF-738: ------------------------------ > Make filesystem content storage the default > ------------------------------------------- > > Key: ARTIF-738 > URL: https://issues.jboss.org/browse/ARTIF-738 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Blob as the default is already causing heap space issues (Hibernate uses a lot to write out the Blob, etc.). I think it makes a lot more sense to use the filesystem as the default. Update the docs as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-738) Make filesystem content storage the default

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-738: --------------------------------- Summary: Make filesystem content storage the default Key: ARTIF-738 URL: https://issues.jboss.org/browse/ARTIF-738 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 Blob as the default is already causing heap space issues (Hibernate uses a lot to write out the Blob, etc.). I think it makes a lot more sense to use the filesystem as the default. Update the docs as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-737) Execute batch persist in single transaction

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-737: --------------------------------- Summary: Execute batch persist in single transaction Key: ARTIF-737 URL: https://issues.jboss.org/browse/ARTIF-737 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta3 If any piece of a batch (and therefore, expanded archives, etc.) persist fails, the entire thing should be rolled back. Currently, each artifact in the batch is persisted in its own transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-735) Archive uploads do not create JMS events

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-735?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-735. ------------------------------- Resolution: Done > Archive uploads do not create JMS events > ---------------------------------------- > > Key: ARTIF-735 > URL: https://issues.jboss.org/browse/ARTIF-735 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > Currently, JMS events are sent only for single uploads. They're entirely skipped for artifacts expanded from within an archive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-728) Add upload endpoint that takes a local file path

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-728?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-728. ------------------------------- Resolution: Done > Add upload endpoint that takes a local file path > ------------------------------------------------ > > Key: ARTIF-728 > URL: https://issues.jboss.org/browse/ARTIF-728 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > On the server and all clients, add a new upload endpoint that takes a local file path, instead of an InputStream/byte[]. If the file is available on/to the server's machine, there should be no reason why we can't simply use it, rather than pass it through the web service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (ARTIF-728) Add upload endpoint that takes a local file path

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-728?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-728: ------------------------------ Fix Version/s: 1.0.0.Beta3 > Add upload endpoint that takes a local file path > ------------------------------------------------ > > Key: ARTIF-728 > URL: https://issues.jboss.org/browse/ARTIF-728 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta3 > > > On the server and all clients, add a new upload endpoint that takes a local file path, instead of an InputStream/byte[]. If the file is available on/to the server's machine, there should be no reason why we can't simply use it, rather than pass it through the web service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

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