February 2017 - shrinkwrap-issues

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

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-264?page=com.atlassian.jira.plu... ] Matous Jobanek closed SHRINKRES-264. ------------------------------------ Assignee: Matous Jobanek Resolution: Cannot Reproduce Bug I'm closing this issue as it cannot be reproduced (it's not an issue in ShwinkWrap). Feel free to reopen it if you don't agree > 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 > Assignee: Matous Jobanek > > 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-267) Network Proxy configuration for Wildfly swarm

by Abel Salgado Romero (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-267?page=com.atlassian.jira.plu... ] Abel Salgado Romero updated SHRINKRES-267: ------------------------------------------ Summary: Network Proxy configuration for Wildfly swarm (was: Network Proxy configuration for Wilsfly ) > Network Proxy configuration for Wildfly swarm > ---------------------------------------------- > > Key: SHRINKRES-267 > URL: https://issues.jboss.org/browse/SHRINKRES-267 > Project: ShrinkWrap Resolvers > Issue Type: Clarification > Components: maven > Environment: Maven Resolver > Reporter: Abel Salgado Romero > Priority: Minor > > Maven Resolver does not take the proxy configuration from the default settings.xml. > Note the version used is captured from the wildfly bom 2017.1.1. > When running this example: https://github.com/abelsromero/wildfly-swarm-poc/blob/master/src/test/jav..., for first time you must be in an open network so that Arquillian can download some jboss/wildfly dependencies. > Once it is is done, you can go back to your "normal" corporate network behind a proxy. > There are some options like manually adding the dependencies (http://stackoverflow.com/questions/6291146/arquillian-shrinkwrap-mavendep...) so that they are downloaded from maven, but this is not practical. > Also, some googling shows mentions of a method to configure the settings.xml file directly in the resolver, however this method is not available in the version used. > I open this as a "clarification" since it seems to me I am missing something being the proxy configuration something basic. However, I have tried several options and nothing works. > Note that I have several other applications running without issues, maven, gradle, shells, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-267) Network Proxy configuration for Wilsfly

by Abel Salgado Romero (JIRA)

Abel Salgado Romero created SHRINKRES-267: --------------------------------------------- Summary: Network Proxy configuration for Wilsfly Key: SHRINKRES-267 URL: https://issues.jboss.org/browse/SHRINKRES-267 Project: ShrinkWrap Resolvers Issue Type: Clarification Components: maven Environment: Maven Resolver Reporter: Abel Salgado Romero Priority: Minor Maven Resolver does not take the proxy configuration from the default settings.xml. Note the version used is captured from the wildfly bom 2017.1.1. When running this example: https://github.com/abelsromero/wildfly-swarm-poc/blob/master/src/test/jav..., for first time you must be in an open network so that Arquillian can download some jboss/wildfly dependencies. Once it is is done, you can go back to your "normal" corporate network behind a proxy. There are some options like manually adding the dependencies (http://stackoverflow.com/questions/6291146/arquillian-shrinkwrap-mavendep...) so that they are downloaded from maven, but this is not practical. Also, some googling shows mentions of a method to configure the settings.xml file directly in the resolver, however this method is not available in the version used. I open this as a "clarification" since it seems to me I am missing something being the proxy configuration something basic. However, I have tried several options and nothing works. Note that I have several other applications running without issues, maven, gradle, shells, etc. -- 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 closed SHRINKRES-265. ------------------------------------ Resolution: Done in 2.2.x stream https://github.com/shrinkwrap/resolver/commit/c9a4d3e4346f528a9adc956986e... > 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, 2.2.6 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 2.2.7, 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: ------------------------------------- Fix Version/s: 2.2.7 > 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, 2.2.6 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 3.0.0-alpha-4, 2.2.7 > > -- 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 reopened SHRINKRES-265: -------------------------------------- > 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, 2.2.6 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 3.0.0-alpha-4, 2.2.7 > > -- 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: 2.2.6 > 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, 2.2.6 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 3.0.0-alpha-4, 2.2.7 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-266) Change directory name of extracted Maven binaries (EmbeddedMaven)

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-266?page=com.atlassian.jira.plu... ] Matous Jobanek closed SHRINKRES-266. ------------------------------------ Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/8155fcf32b3aa352923e091bb87... > Change directory name of extracted Maven binaries (EmbeddedMaven) > ----------------------------------------------------------------- > > Key: SHRINKRES-266 > URL: https://issues.jboss.org/browse/SHRINKRES-266 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: maven > Affects Versions: 3.0.0-alpha-3 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 3.0.0-alpha-4 > > > Currently, there in SWR the Maven binary files extracted from downloaded archives are stored in directories named by {{UUID.randomUUID()}}. These directories are then linked with the archive files using md5hash. This hash is stored in a file {{resolver_maven_binary_zip_md5_hash_file}} in the extracted directory. > This approach is neither nice nor intuitive and nor effective. > Change the logic so the hash is used as a name of the new directory instead of using UUID. Related Java class is [DistributionStageImpl|https://github.com/MatousJobanek/resolver/blob/mast...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-266) Change directory name of extracted Maven binaries (EmbeddedMaven)

by Matous Jobanek (JIRA)

Matous Jobanek created SHRINKRES-266: ---------------------------------------- Summary: Change directory name of extracted Maven binaries (EmbeddedMaven) Key: SHRINKRES-266 URL: https://issues.jboss.org/browse/SHRINKRES-266 Project: ShrinkWrap Resolvers Issue Type: Enhancement Components: maven Affects Versions: 3.0.0-alpha-3 Reporter: Matous Jobanek Assignee: Dipak Pawar Fix For: 3.0.0-alpha-4 Currently, there in SWR the Maven binary files extracted from downloaded archives are stored in directories named by {{UUID.randomUUID()}}. These directories are then linked with the archive files using md5hash. This hash is stored in a file {{resolver_maven_binary_zip_md5_hash_file}} in the extracted directory. This approach is neither nice nor intuitive and nor effective. Change the logic so the hash is used as a name of the new directory instead of using UUID. Related Java class is [DistributionStageImpl|https://github.com/MatousJobanek/resolver/blob/mast...] -- 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 closed SHRINKRES-265. ------------------------------------ Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/2ee670a6d5b8fa80a1ee7cfe5bf... > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues February 2017