February 2017 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-265) Missing test scope in junit dependencies

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-265?page=com.atlassian.jira.plu... ] Matous Jobanek reassigned SHRINKRES-265: ---------------------------------------- Assignee: Dipak Pawar > Missing test scope in junit dependencies > ---------------------------------------- > > Key: SHRINKRES-265 > URL: https://issues.jboss.org/browse/SHRINKRES-265 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 3.0.0-alpha-3 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 3.0.0-alpha-4 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-265) Missing test scope in junit dependencies

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-265?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-265: ------------------------------------- Affects Version/s: 3.0.0-alpha-3 > Missing test scope in junit dependencies > ---------------------------------------- > > Key: SHRINKRES-265 > URL: https://issues.jboss.org/browse/SHRINKRES-265 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 3.0.0-alpha-3 > Reporter: Matous Jobanek > Fix For: 3.0.0-alpha-4 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-265) Missing test scope in junit dependencies

by Matous Jobanek (JIRA)

Matous Jobanek created SHRINKRES-265: ---------------------------------------- Summary: Missing test scope in junit dependencies Key: SHRINKRES-265 URL: https://issues.jboss.org/browse/SHRINKRES-265 Project: ShrinkWrap Resolvers Issue Type: Bug Reporter: Matous Jobanek Fix For: 3.0.0-alpha-4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-132) MavenImport should have different name

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-132?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-132: ------------------------------------- Fix Version/s: 3.0.0 (was: 3.0.0-alpha-3) > MavenImport should have different name > -------------------------------------- > > Key: SHRINKRES-132 > URL: https://issues.jboss.org/browse/SHRINKRES-132 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: maven > Affects Versions: 2.0.0 > Reporter: Karel Piwko > Assignee: Matous Jobanek > Priority: Minor > Fix For: 3.0.0 > > > MavenImporter is now able to build the project from pom.xml. This means that MavenImporter name is no longer valid, as it does not promote the fact that project will be build from scratch. > It might be MavenBuilder instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-228) Re-enable maven integration tests module

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-228?page=com.atlassian.jira.plu... ] Matous Jobanek updated SHRINKRES-228: ------------------------------------- Fix Version/s: 3.0.0 (was: 3.0.0-alpha-3) > Re-enable maven integration tests module > ---------------------------------------- > > Key: SHRINKRES-228 > URL: https://issues.jboss.org/browse/SHRINKRES-228 > Project: ShrinkWrap Resolvers > Issue Type: Task > Components: maven > Reporter: Karel Piwko > Assignee: Matous Jobanek > Fix For: 3.0.0 > > > Re-enable Maven integration tests module in pom.xml aggregator file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-145) Provide a ManifestBuilder

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-145?page=com.atlassian.jira.pl... ] Thomas Diesler resolved SHRINKDESC-145. --------------------------------------- Resolution: Out of Date > Provide a ManifestBuilder > ------------------------- > > Key: SHRINKDESC-145 > URL: https://issues.jboss.org/browse/SHRINKDESC-145 > Project: ShrinkWrap Descriptors > Issue Type: Task > Reporter: Thomas Diesler > > WildFly has a dependency on [jbosgi-metadata|https://github.com/tdiesler/jbosgi-metadata] because of frequent usage of it's [ManifestBuilder|https://github.com/tdiesler/jbosgi-metadata/blob/master/s...] > Please also consider moving the [OSGiManifestBuilder|https://github.com/tdiesler/jbosgi-metadata/blob/mast...] to shrinkwrap. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-278) WebArchive.setManifest() results in WEB-INF/classes/META-INF/MANIFEST.MF

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-278?page=com.atlassian.jira.pl... ] Thomas Diesler resolved SHRINKWRAP-278. --------------------------------------- Resolution: Out of Date > WebArchive.setManifest() results in WEB-INF/classes/META-INF/MANIFEST.MF > ------------------------------------------------------------------------ > > Key: SHRINKWRAP-278 > URL: https://issues.jboss.org/browse/SHRINKWRAP-278 > Project: ShrinkWrap > Issue Type: Bug > Affects Versions: 1.0.0-alpha-11 > Reporter: Thomas Diesler > > WebArchive.setManifest() results in WEB-INF/classes/META-INF/MANIFEST.MF > I believe > WebArchive.setManifest() should result in META-INF/MANIFEST.MF -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-264) addPackages does not include package-private classes in child package when called recursively

by ebuzer taha kanat (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-264?page=com.atlassian.jira.plu... ] ebuzer taha kanat commented on SHRINKRES-264: --------------------------------------------- Apologise, TypeNotPresentExceptionProxy exception cause is not from suspected package-private classes ignored. When unrelated issue solved arquillian cruiser clearly shows that recursive package add works as expected. False alarm. > addPackages does not include package-private classes in child package when called recursively > ---------------------------------------------------------------------------------------------- > > Key: SHRINKRES-264 > URL: https://issues.jboss.org/browse/SHRINKRES-264 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api > Reporter: ebuzer taha kanat > > With package structure of a.b.root.child when arquillian test class is in a.b.root at the phase of deployment archive creation > {code:java} > archive.addPackages(true, "a.b.root"); > {code} > does not includes package-private classes in a.b.root.child or possible other child packages. Thus creates class dependency related problems for arquillian testing such as cdi errors in wildfly-arquillian-container-remote . > Package-private classes should not be directly usable out of package we know that but they should be addable to deployment for indirect dependency reasons. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-264) addPackages does not include package-private classes in child package when called recursively

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-264?page=com.atlassian.jira.plu... ] Karel Piwko moved SHRINKWRAP-513 to SHRINKRES-264: -------------------------------------------------- Project: ShrinkWrap Resolvers (was: ShrinkWrap) Key: SHRINKRES-264 (was: SHRINKWRAP-513) Component/s: api (was: api) Affects Version/s: (was: 1.2.6) > addPackages does not include package-private classes in child package when called recursively > ---------------------------------------------------------------------------------------------- > > Key: SHRINKRES-264 > URL: https://issues.jboss.org/browse/SHRINKRES-264 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: api > Reporter: ebuzer taha kanat > > With package structure of a.b.root.child when arquillian test class is in a.b.root at the phase of deployment archive creation > {code:java} > archive.addPackages(true, "a.b.root"); > {code} > does not includes package-private classes in a.b.root.child or possible other child packages. Thus creates class dependency related problems for arquillian testing such as cdi errors in wildfly-arquillian-container-remote . > Package-private classes should not be directly usable out of package we know that but they should be addable to deployment for indirect dependency reasons. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-513) addPackages does not include package-private classes in child package when called recursively

by ebuzer taha kanat (JIRA)

ebuzer taha kanat created SHRINKWRAP-513: -------------------------------------------- Summary: addPackages does not include package-private classes in child package when called recursively Key: SHRINKWRAP-513 URL: https://issues.jboss.org/browse/SHRINKWRAP-513 Project: ShrinkWrap Issue Type: Bug Components: api Affects Versions: 1.2.6 Reporter: ebuzer taha kanat With package structure of a.b.root.child when arquillian test class is in a.b.root at the phase of deployment archive creation {code:java} archive.addPackages(true, "a.b.root"); {code} does not includes package-private classes in a.b.root.child or possible other child packages. Thus creates class dependency related problems for arquillian testing such as cdi errors in wildfly-arquillian-container-remote . Package-private classes should not be directly usable out of package we know that but they should be addable to deployment for indirect dependency reasons. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues February 2017