October 2014 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-211) java.lang.NoClassDefFoundError: com/google/protobuf/GeneratedMessage

by Antimo Di Comite (JIRA)

Antimo Di Comite created SHRINKRES-211: ------------------------------------------ Summary: java.lang.NoClassDefFoundError: com/google/protobuf/GeneratedMessage Key: SHRINKRES-211 URL: https://issues.jboss.org/browse/SHRINKRES-211 Project: ShrinkWrap Resolvers Issue Type: Bug Components: maven Affects Versions: 2.1.0 Environment: Windows 7 Reporter: Antimo Di Comite I'm having trouble creating a JUnit test using a pom.xml dependency. The test are being run with Arquillian @RunWith(Arquillian.class) In this method @Deployment public static JavaArchive createDeployment() { First, I create a JavaArchive with the package of the project I'm testing JavaArchive merge = ShrinkWrap.create(JavaArchive.class). addPackages(true, "migrazioneGeaPersistenzaTampone", "migrazioneGeaPersistenza", "it.**.mistral.importGEA4.task", "migrazioneGeaPersistenzaAccess" ). addClasses(java.sql.Connection.class) .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); Then when I launch the test, there are some missing dependencies Unable to resolve any beans for Types: [class it.**.**.be.service.EnvironmentRootService] present in this dependency <dependency> <groupId>it.**.mistral</groupId> <artifactId>mistral-be</artifactId> <version>0.1.0</version> <scope>compile</scope> </dependency> I have tried lots of different things to add these dependencies, the best one seems to be using the ShrinkWrap Resolvers (https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc, particullarry this paragraph https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc#resolu...) a) JavaArchive[] archives = Maven.resolver().loadPomFromFile(path_to_pom_file). importDependencies(ScopeType.TEST,ScopeType.COMPILE). resolve().withTransitivity().as(JavaArchive.class); or Maven.resolver().loadPomFromFile("/path/to/pom.xml").importRuntimeDependencies() .resolve().withTransitivity().asFile(); The dependency is ignored in either way (i'm missing something?) b) JavaArchive[] mistral_be = Maven.configureResolver().workOffline(). resolve("it.**.mistral:mistral-be:0.1.0").withTransitivity().as(JavaArchive.class); for (int i = 0; i < mistral_be.length ; i++) { merge = merge.merge(mistral_be[i]); } With a simple System.out.println(merge.toString(true)); I can see that all files from dependencies are present! Anyway I use local repository workoffline() Maybe I am missing some dependencies? But exiting the method with a return merge; throws a "java.lang.NoClassDefFoundError: com/google/protobuf/GeneratedMessage....Caused by: java.lang.ClassNotFoundException: com.google.protobuf.GeneratedMessage" error. Adding another dependencies to protobuf : // Trym'g to add protobuf dependencies JavaArchive[] prtoo_buf = Maven.configureResolver().withMavenCentralRepo(true).resolve("com.google.protobuf:protobuf-java:2.3.0").withTransitivity().as(JavaArchive.class); for (int i = 0; i < prto_buf.length ; i++) { projectPackages = projectPackages.merge(proto_buf[i]); } Keep ending with the same error throws a "java.lang.NoClassDefFoundError: com/google/protobuf/GeneratedMessage -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-210) Dependency management with scopes are not resolved correctly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-210?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-210: ---------------------------------- Affects Version/s: 2.2.0-beta-1 > Dependency management with scopes are not resolved correctly > ------------------------------------------------------------ > > Key: SHRINKRES-210 > URL: https://issues.jboss.org/browse/SHRINKRES-210 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-1 > Reporter: Emond Papegaaij > > If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem: > https://github.com/papegaaij/resolve-dep > This testcase resolves the dependencies using: > {code} > File[] jars = Maven.configureResolver().workOffline() > .loadPomFromFile("pom.xml") > .importCompileAndRuntimeDependencies().resolve() > .withTransitivity().as(File.class); > {code} > The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-210) Dependency management with scopes are not resolved correctly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-210?page=com.atlassian.jira.plu... ] Karel Piwko commented on SHRINKRES-210: --------------------------------------- I'll check it with 2.2.0-beta-1 implementation. > Dependency management with scopes are not resolved correctly > ------------------------------------------------------------ > > Key: SHRINKRES-210 > URL: https://issues.jboss.org/browse/SHRINKRES-210 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-1 > Reporter: Emond Papegaaij > > If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem: > https://github.com/papegaaij/resolve-dep > This testcase resolves the dependencies using: > {code} > File[] jars = Maven.configureResolver().workOffline() > .loadPomFromFile("pom.xml") > .importCompileAndRuntimeDependencies().resolve() > .withTransitivity().as(File.class); > {code} > The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-210) Dependency management with scopes are not resolved correctly

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-210?page=com.atlassian.jira.plu... ] Karel Piwko moved SHRINKWRAP-488 to SHRINKRES-210: -------------------------------------------------- Project: ShrinkWrap Resolvers (was: ShrinkWrap) Key: SHRINKRES-210 (was: SHRINKWRAP-488) Affects Version/s: (was: 1.2.2) Component/s: maven (was: ext-resolver) > Dependency management with scopes are not resolved correctly > ------------------------------------------------------------ > > Key: SHRINKRES-210 > URL: https://issues.jboss.org/browse/SHRINKRES-210 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Reporter: Emond Papegaaij > > If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem: > https://github.com/papegaaij/resolve-dep > This testcase resolves the dependencies using: > {code} > File[] jars = Maven.configureResolver().workOffline() > .loadPomFromFile("pom.xml") > .importCompileAndRuntimeDependencies().resolve() > .withTransitivity().as(File.class); > {code} > The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-209) Remove extra debug output from ArchiveFilteringUtils

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-209?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-209. ----------------------------------- Resolution: Done Landed in https://github.com/shrinkwrap/resolver/commit/85d24c2bb70520de3a4d80c686e... > Remove extra debug output from ArchiveFilteringUtils > ---------------------------------------------------- > > Key: SHRINKRES-209 > URL: https://issues.jboss.org/browse/SHRINKRES-209 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: maven > Affects Versions: 2.2.0-beta-1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.2.0-cr-1 > > > For Maven archive packaging 2.2.0-beta-1 you have a println in the delivered code. > Please plan to remove it for the next release. > Thank you. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-207) Update jboss-parent to version 15

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-207?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-207. ----------------------------------- Resolution: Done Landed in https://github.com/shrinkwrap/resolver/commit/c6ea35da55040bca6f27ec5a991... > Update jboss-parent to version 15 > --------------------------------- > > Key: SHRINKRES-207 > URL: https://issues.jboss.org/browse/SHRINKRES-207 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: api > Affects Versions: 2.2.0-beta-1 > Reporter: Karel Piwko > Fix For: 2.2.0-cr-1 > > > JBoss parent needs update because enforcer rule does not respect source jdk version, see - https://github.com/jboss/jboss-parent-pom/commit/c460de0c8df4bf4cbb5cfaea... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-209) Remove extra debug output from ArchiveFilteringUtils

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-209: ------------------------------------- Summary: Remove extra debug output from ArchiveFilteringUtils Key: SHRINKRES-209 URL: https://issues.jboss.org/browse/SHRINKRES-209 Project: ShrinkWrap Resolvers Issue Type: Bug Components: maven Affects Versions: 2.2.0-beta-1 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 2.2.0-cr-1 For Maven archive packaging 2.2.0-beta-1 you have a println in the delivered code. Please plan to remove it for the next release. Thank you. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-158) create descriptor for javax.enterprise.inject.spi.Extension

by Mathieu Lachance (JIRA)

Mathieu Lachance created SHRINKDESC-158: ------------------------------------------- Summary: create descriptor for javax.enterprise.inject.spi.Extension Key: SHRINKDESC-158 URL: https://issues.jboss.org/browse/SHRINKDESC-158 Project: ShrinkWrap Descriptors Issue Type: Feature Request Affects Versions: 2.0.0-alpha-5 Reporter: Mathieu Lachance like beans.xml I often want to activate, deactivate, play with the ordering of CDI extension depending on the test. Having a descriptor for META-INF/services/"javax.enterprise.inject.spi.Extension" (which contains only a list of fully qualified classname each separated with a line separator) would be a little nice addition. Right now I'm simply using the following java8 snippet to create my resource: {code} new StringAsset( Stream.of(MyTestClass.class, ....) .map(Object::toString) .collect(Collectors.joining(System.lineSeparator()))); {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-488) Dependency management with scopes are not resolved correctly

by Emond Papegaaij (JIRA)

Emond Papegaaij created SHRINKWRAP-488: ------------------------------------------ Summary: Dependency management with scopes are not resolved correctly Key: SHRINKWRAP-488 URL: https://issues.jboss.org/browse/SHRINKWRAP-488 Project: ShrinkWrap Issue Type: Bug Components: ext-resolver Affects Versions: 1.2.2 Reporter: Emond Papegaaij If the scope of an indirect dependency is changed in the dependencyManagement of your pom, this scope is not correctly taken into account when resolving compileAndRuntimeDependencies. I've created a very minimal testcase to demonstrate this problem: https://github.com/papegaaij/resolve-dep This testcase resolves the dependencies using: {code} File[] jars = Maven.configureResolver().workOffline() .loadPomFromFile("pom.xml") .importCompileAndRuntimeDependencies().resolve() .withTransitivity().as(File.class); {code} The pom only defines 1 compile dependency (shrinkwrap-impl-base), which depends on 2 others (shrinkwrap-api and shrinkwrap-spi). shrinkwrap-api has a dependencyManagement with scope provided, so I expect this resolution to yield 2 files (base and spi), but it yields all 3. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues October 2014