May 2014 - shrinkwrap-issues - Jboss List Archives

[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 updated SHRINKRES-182: --------------------------------- Steps to Reproduce: Reproducer in WFK2-629 (was: Run {{mvn clean verify -Darquillian=jbossas-managed-7}} in the attached seampay example project with the current WFK2+EAP6 repositories.) > 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

[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 updated SHRINKRES-182: --------------------------------- Affects Version/s: 2.1.0 > 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

[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 moved WFK2-632 to SHRINKRES-182: ------------------------------------------- Project: ShrinkWrap Resolvers (was: JBoss WFK 2) Key: SHRINKRES-182 (was: WFK2-632) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: impl-maven (was: Arquillian) Security: (was: Public) Target Release: (was: 2.6.0.GA) > 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

[JBoss JIRA] (SHRINKRES-176) MavenImporter archive name

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-176?page=com.atlassian.jira.plu... ] Karel Piwko reassigned SHRINKRES-176: ------------------------------------- Assignee: Karel Piwko (was: Andrew Rubinger) > MavenImporter archive name > -------------------------- > > Key: SHRINKRES-176 > URL: https://issues.jboss.org/browse/SHRINKRES-176 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Michael Irwin > Assignee: Karel Piwko > Fix For: 2.2.0-alpha-3 > > > When using the MavenImporter, the archiveName property is ignored. > {code} > WebArchive archive = ShrinkWrap.create(MavenImporter.class, "test.war") > .loadPomFromFile("pom.xml") > .importBuildOutput() > .as(WebArchive.class); > System.out.println(archive.getName()); > {code} > The archive name will be whatever the name of the Maven artifact is, which is usually [artifactId]-[version]. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-176) MavenImporter archive name

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-176?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-176: ---------------------------------- Fix Version/s: 2.2.0-alpha-3 > MavenImporter archive name > -------------------------- > > Key: SHRINKRES-176 > URL: https://issues.jboss.org/browse/SHRINKRES-176 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Michael Irwin > Assignee: Andrew Rubinger > Fix For: 2.2.0-alpha-3 > > > When using the MavenImporter, the archiveName property is ignored. > {code} > WebArchive archive = ShrinkWrap.create(MavenImporter.class, "test.war") > .loadPomFromFile("pom.xml") > .importBuildOutput() > .as(WebArchive.class); > System.out.println(archive.getName()); > {code} > The archive name will be whatever the name of the Maven artifact is, which is usually [artifactId]-[version]. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-180) transitive dependencies updated from provided to compile

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-180?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-180: --------------------------------------- Hi Markus, I believe that we always include provided - as MavenImporter needs to them in order to compile java code. However, I'll try to split compilation resolution from archive composition. The other part is to check whether we are propagating *provided* scope correctly. Would you be able to just load the pom.xml (not using importer but just Maven.resolver() and resolve hibernate-search to see whether hibernate-core will be downloaded? > transitive dependencies updated from provided to compile > -------------------------------------------------------- > > Key: SHRINKRES-180 > URL: https://issues.jboss.org/browse/SHRINKRES-180 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.2.0-alpha-2 > Reporter: Markus Schulz > Assignee: Andrew Rubinger > Fix For: 2.2.0-alpha-3 > > Attachments: deptree.txt, MavenResolverTest.java, transitivetest-pom.xml > > > i have a pom with something like: > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search</artifactId> > <version>4.2.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-core</artifactId> > <scope>provided</scope> > </dependency> > hibernate-search internally dependes on hibernate-core (scope compile). But in don't want to get hbernate-core in my deployment, therefore it's forced to provided. > But: > File[] testLibs = Maven.configureResolver() > .workOffline() > .loadPomFromClassLoaderResource("transitivetest-pom.xml") > .importRuntimeDependencies() > .resolve() > .withTransitivity() > .asFile(); > still contains hibernate-core.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-180) transitive dependencies updated from provided to compile

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-180?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-180: ---------------------------------- Fix Version/s: 2.2.0-alpha-3 > transitive dependencies updated from provided to compile > -------------------------------------------------------- > > Key: SHRINKRES-180 > URL: https://issues.jboss.org/browse/SHRINKRES-180 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.2.0-alpha-2 > Reporter: Markus Schulz > Assignee: Andrew Rubinger > Fix For: 2.2.0-alpha-3 > > Attachments: deptree.txt, MavenResolverTest.java, transitivetest-pom.xml > > > i have a pom with something like: > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-search</artifactId> > <version>4.2.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-core</artifactId> > <scope>provided</scope> > </dependency> > hibernate-search internally dependes on hibernate-core (scope compile). But in don't want to get hbernate-core in my deployment, therefore it's forced to provided. > But: > File[] testLibs = Maven.configureResolver() > .workOffline() > .loadPomFromClassLoaderResource("transitivetest-pom.xml") > .importRuntimeDependencies() > .resolve() > .withTransitivity() > .asFile(); > still contains hibernate-core.jar -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-181) MavenArtifactInfo is missing <optional> info

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-181?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-181: ---------------------------------- Fix Version/s: 2.2.0-alpha-3 (was: 2.1.1) > MavenArtifactInfo is missing <optional> info > -------------------------------------------- > > Key: SHRINKRES-181 > URL: https://issues.jboss.org/browse/SHRINKRES-181 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: api-maven > Affects Versions: 2.2.0-alpha-2 > Reporter: Ales Justin > Assignee: Andrew Rubinger > Fix For: 2.2.0-alpha-3 > > > There is no way to tell if MavenArtifactInfo is optional, > if not using custom strategy. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-181) MavenArtifactInfo is missing <optional> info

by Ales Justin (JIRA)

Ales Justin created SHRINKRES-181: ------------------------------------- Summary: MavenArtifactInfo is missing <optional> info Key: SHRINKRES-181 URL: https://issues.jboss.org/browse/SHRINKRES-181 Project: ShrinkWrap Resolvers Issue Type: Feature Request Components: api-maven Affects Versions: 2.2.0-alpha-2 Reporter: Ales Justin Assignee: Andrew Rubinger Fix For: 2.1.1 There is no way to tell if MavenArtifactInfo is optional, if not using custom strategy. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-155) Missing methods in generated common parents

by Ralf Battenfeld (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-155?page=com.atlassian.jira.pl... ] Ralf Battenfeld commented on SHRINKDESC-155: -------------------------------------------- The missing paramname methods are now available. Thanks for reporting. > Missing methods in generated common parents > ------------------------------------------- > > Key: SHRINKDESC-155 > URL: https://issues.jboss.org/browse/SHRINKDESC-155 > Project: ShrinkWrap Descriptors > Issue Type: Feature Request > Components: api-javaee > Affects Versions: 2.0.0-alpha-6 > Reporter: George Gastaldi > Assignee: Ralf Battenfeld > > Some common parents generated from SHRINKDESC-151 do not have all the required methods declared in the common interface. > For example: > - JavaeeServletMappingCommonType > -- see https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > - WebAppCommonDescriptor > -- see https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > Other parent interfaces might be missing methods as well, they should be reviewed and have the common methods created. -- 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