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 resolved SHRINKRES-174. ----------------------------------- Resolution: Done > 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.1.1, 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-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 edited comment on SHRINKRES-182 at 5/28/14 4:40 AM: ---------------------------------------------------------------- Fix pushed upstream in https://github.com/shrinkwrap/resolver/commit/6cb6d9d82f8ebe25d0bfc5b4a6c... was (Author: kpiwko): Fix pushed upstream in https://github.com/kpiwko/resolver/commit/6cb6d9d82f8ebe25d0bfc5b4a6c803a... > 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, 2.2.0-alpha-3 > > > 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-162) Resolved file extension returned instead of packaging type in MavenResolvedArtifact

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-162?page=com.atlassian.jira.plu... ] Karel Piwko edited comment on SHRINKRES-162 at 5/28/14 4:40 AM: ---------------------------------------------------------------- Pushed upstream in https://github.com/shrinkwrap/resolver/commit/6cb6d9d82f8ebe25d0bfc5b4a6c... was (Author: kpiwko): Pushed upstream in https://github.com/kpiwko/resolver/commit/6cb6d9d82f8ebe25d0bfc5b4a6c803a.... > Resolved file extension returned instead of packaging type in MavenResolvedArtifact > ----------------------------------------------------------------------------------- > > Key: SHRINKRES-162 > URL: https://issues.jboss.org/browse/SHRINKRES-162 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Johan Evelönn > Assignee: Karel Piwko > Fix For: 2.1.1, 2.2.0-alpha-3 > > > When declaring a dependency in a pom.xml with the type EJB and then resolving it into a MavenResolvedArtifact the method getCoordinate().getPackagingType() returns PackagingType.JAR instead of PackagingType.EJB. So it seems like it sets the PackagingType to the extension of the resolved file. It works fine when a dependency has type war, since type and extension is the same. -- 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.2.0-alpha-3 > 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, 2.2.0-alpha-3 > > > 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 Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-182?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-182. ----------------------------------- Resolution: Done Fix pushed upstream in https://github.com/kpiwko/resolver/commit/6cb6d9d82f8ebe25d0bfc5b4a6c803a... > 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, 2.2.0-alpha-3 > > > 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-162) Resolved file extension returned instead of packaging type in MavenResolvedArtifact

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-162?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-162. ----------------------------------- Resolution: Done > Resolved file extension returned instead of packaging type in MavenResolvedArtifact > ----------------------------------------------------------------------------------- > > Key: SHRINKRES-162 > URL: https://issues.jboss.org/browse/SHRINKRES-162 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Johan Evelönn > Assignee: Karel Piwko > Fix For: 2.1.1, 2.2.0-alpha-3 > > > When declaring a dependency in a pom.xml with the type EJB and then resolving it into a MavenResolvedArtifact the method getCoordinate().getPackagingType() returns PackagingType.JAR instead of PackagingType.EJB. So it seems like it sets the PackagingType to the extension of the resolved file. It works fine when a dependency has type war, since type and extension is the same. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-162) Resolved file extension returned instead of packaging type in MavenResolvedArtifact

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-162?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-162: --------------------------------------- Pushed upstream in https://github.com/kpiwko/resolver/commit/6cb6d9d82f8ebe25d0bfc5b4a6c803a.... > Resolved file extension returned instead of packaging type in MavenResolvedArtifact > ----------------------------------------------------------------------------------- > > Key: SHRINKRES-162 > URL: https://issues.jboss.org/browse/SHRINKRES-162 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Johan Evelönn > Assignee: Karel Piwko > Fix For: 2.1.1, 2.2.0-alpha-3 > > > When declaring a dependency in a pom.xml with the type EJB and then resolving it into a MavenResolvedArtifact the method getCoordinate().getPackagingType() returns PackagingType.JAR instead of PackagingType.EJB. So it seems like it sets the PackagingType to the extension of the resolved file. It works fine when a dependency has type war, since type and extension is the same. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-162) Resolved file extension returned instead of packaging type in MavenResolvedArtifact

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-162?page=com.atlassian.jira.plu... ] Karel Piwko reassigned SHRINKRES-162: ------------------------------------- Assignee: Karel Piwko (was: Andrew Rubinger) > Resolved file extension returned instead of packaging type in MavenResolvedArtifact > ----------------------------------------------------------------------------------- > > Key: SHRINKRES-162 > URL: https://issues.jboss.org/browse/SHRINKRES-162 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Johan Evelönn > Assignee: Karel Piwko > Fix For: 2.1.1, 2.2.0-alpha-3 > > > When declaring a dependency in a pom.xml with the type EJB and then resolving it into a MavenResolvedArtifact the method getCoordinate().getPackagingType() returns PackagingType.JAR instead of PackagingType.EJB. So it seems like it sets the PackagingType to the extension of the resolved file. It works fine when a dependency has type war, since type and extension is the same. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-162) Resolved file extension returned instead of packaging type in MavenResolvedArtifact

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-162?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-162: ---------------------------------- Fix Version/s: 2.1.1 2.2.0-alpha-3 > Resolved file extension returned instead of packaging type in MavenResolvedArtifact > ----------------------------------------------------------------------------------- > > Key: SHRINKRES-162 > URL: https://issues.jboss.org/browse/SHRINKRES-162 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.0.1 > Reporter: Johan Evelönn > Assignee: Andrew Rubinger > Fix For: 2.1.1, 2.2.0-alpha-3 > > > When declaring a dependency in a pom.xml with the type EJB and then resolving it into a MavenResolvedArtifact the method getCoordinate().getPackagingType() returns PackagingType.JAR instead of PackagingType.EJB. So it seems like it sets the PackagingType to the extension of the resolved file. It works fine when a dependency has type war, since type and extension is the same. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[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 updated SHRINKRES-174: ---------------------------------- Fix Version/s: 2.1.1 > 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, 2.1.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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues May 2014