May 2014 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-174) Missleading Exception message when sonatype and eclipse Aether found on classpath

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-174?page=com.atlassian.jira.plu... ] Karel Piwko reopened SHRINKRES-174: ----------------------------------- Reopened to add fix version. > Missleading Exception message when sonatype and eclipse Aether found on classpath > --------------------------------------------------------------------------------- > > Key: SHRINKRES-174 > URL: https://issues.jboss.org/browse/SHRINKRES-174 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Aslak Knutsen > Assignee: Karel Piwko > Fix For: 2.2.0-alpha-1 > > > "Unable to boostrap Aether repository system. Make sure you're running Maven 3.1.0 or newer." > The build is running Maven 3.1.0. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... > Dependency:tree > https://gist.github.com/alesj/9891834#file-gistfile1-txt-L43 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Karel Piwko reopened SHRINKRES-177: ----------------------------------- > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: 2.2.0-alpha-2, 2.1.1 > > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-175) Aether fails to instantiate RepositorySystem if SLF4J < 1.6 is on CP

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-175?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-175: ---------------------------------- Fix Version/s: 2.1.1 > Aether fails to instantiate RepositorySystem if SLF4J < 1.6 is on CP > -------------------------------------------------------------------- > > Key: SHRINKRES-175 > URL: https://issues.jboss.org/browse/SHRINKRES-175 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Critical > Fix For: 2.2.0-alpha-1, 2.1.1 > > > Aether fails to instantiate repository service, because it identifies that factory is on classpath and tries to use it. > LoggingFactory is a required component for Aether. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-177. --------------------------------- > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: 2.2.0-alpha-2, 2.1.1 > > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-177. ----------------------------------- Resolution: Done > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: 2.1.1, 2.2.0-alpha-2 > > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-177: ---------------------------------- Fix Version/s: 2.1.1 > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: 2.2.0-alpha-2, 2.1.1 > > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Karel Piwko reopened SHRINKRES-177: ----------------------------------- Reopened to add fix version. > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: 2.2.0-alpha-2 > > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-483) shrinkwrap-resolver-depchain cannot be used in src/main/java

by MINNA HU (JIRA)

MINNA HU created SHRINKWRAP-483: ----------------------------------- Summary: shrinkwrap-resolver-depchain cannot be used in src/main/java Key: SHRINKWRAP-483 URL: https://issues.jboss.org/browse/SHRINKWRAP-483 Project: ShrinkWrap Issue Type: Enhancement Reporter: MINNA HU In our project, I want to make some utility classes based on ShrinkWrap maven solver, and we put the utility classes under src/main/java. However, after we added maven dependency into pom.xml, mvn build always complained compilation error. Only after I put the classes into src/test/java, shrinkwrap-resolver-depchain dependency can be used in compilation. pom.xml has the following dependency: <dependency> <groupId>org.jboss.shrinkwrap.resolver</groupId> <artifactId>shrinkwrap-resolver-depchain</artifactId> <type>pom</type> </dependency> Even I added <scope>compile</scope> to shrinkwrap-resolver-depchain dependency, classes in src/main/java still cannot compile. Is shrinkwrap-resolver-depchain hard-coded to only work in mvn test-compile? Could you make it available for mvn compile? Thank you~ -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-182) ShrinkWrap Resolver sometimes can't resolve a dependency with EJB packaging

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-182?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-182: ---------------------------------- Fix Version/s: 2.1.1 > ShrinkWrap Resolver sometimes can't resolve a dependency with EJB packaging > --------------------------------------------------------------------------- > > Key: SHRINKRES-182 > URL: https://issues.jboss.org/browse/SHRINKRES-182 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Ron Šmeral > Assignee: Karel Piwko > Fix For: 2.1.1 > > > Several Seam example integration tests fail when creating the deployment for testing, due to an exception in resoution of the {{org.jboss.seam:jboss-seam}} artifact, which is an artifact with EJB packaging. > {noformat} > java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive org.jboss.seam.example.booking.test.BookingTest.createDeployment() > ... > Caused by: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to collect/resolve dependency tree for a resolution due to: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > ... > Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > ... > Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > ... > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > {noformat} > It is quite suspicious, that SWR tries to download a file with an {{ejb}} extension, which would be obviously wrong: > {noformat} > WARNING: Failed downloading org/jboss/seam/jboss-seam/2.3.4.Final-redhat-1/jboss-seam-2.3.4.Final-redhat-1.ejb from file:///qa/hudson_workspace/workspace/wfk-2.x-seam-2.3-eap6-itest/dc63a4c9/wfk-qa/build/configuration/../../../jboss-wfk-2.6.0-maven-repository/. > {noformat} > This behaviour is seemingly not consistent, but is deterministic - it happens only in some projects, but in those, it happens every time. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-182) ShrinkWrap Resolver sometimes can't resolve a dependency with EJB packaging

by Ron Šmeral (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-182?page=com.atlassian.jira.plu... ] Ron Šmeral commented on SHRINKRES-182: -------------------------------------- Possibly related to SHRINKRES-162, but it doesn't seem to be the sole cause. > ShrinkWrap Resolver sometimes can't resolve a dependency with EJB packaging > --------------------------------------------------------------------------- > > Key: SHRINKRES-182 > URL: https://issues.jboss.org/browse/SHRINKRES-182 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Ron Šmeral > Assignee: Karel Piwko > > Several Seam example integration tests fail when creating the deployment for testing, due to an exception in resoution of the {{org.jboss.seam:jboss-seam}} artifact, which is an artifact with EJB packaging. > {noformat} > java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive org.jboss.seam.example.booking.test.BookingTest.createDeployment() > ... > Caused by: org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to collect/resolve dependency tree for a resolution due to: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > ... > Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > ... > Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > ... > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.jboss.seam:jboss-seam:ejb:2.3.4.Final-redhat-1 in wfk2-enterprise-repository > {noformat} > It is quite suspicious, that SWR tries to download a file with an {{ejb}} extension, which would be obviously wrong: > {noformat} > WARNING: Failed downloading org/jboss/seam/jboss-seam/2.3.4.Final-redhat-1/jboss-seam-2.3.4.Final-redhat-1.ejb from file:///qa/hudson_workspace/workspace/wfk-2.x-seam-2.3-eap6-itest/dc63a4c9/wfk-qa/build/configuration/../../../jboss-wfk-2.6.0-maven-repository/. > {noformat} > This behaviour is seemingly not consistent, but is deterministic - it happens only in some projects, but in those, it happens every time. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues May 2014