[JBoss JIRA] (SHRINKWRAP-492) addPackages method not ever succeeds
by Luca Stancapiano (JIRA)
[ https://issues.jboss.org/browse/SHRINKWRAP-492?page=com.atlassian.jira.pl... ]
Luca Stancapiano commented on SHRINKWRAP-492:
---------------------------------------------
so I think the issue must be resolved by the h2 team. I created an issue in the h2 github: https://github.com/h2database/h2database/issues/167
> addPackages method not ever succeeds
> ------------------------------------
>
> Key: SHRINKWRAP-492
> URL: https://issues.jboss.org/browse/SHRINKWRAP-492
> Project: ShrinkWrap
> Issue Type: Bug
> Components: impl-base
> Environment: shrinkwrap-impl-base 1.2.2
> Reporter: Luca Stancapiano
>
> there are cases where the addPackages method doesn't succeed to load the packages also if they are in the current classloader. An example can be the com.h2database library. This library is registered as resource in the classloader with the name com.h2database and ambigously it contains the package org.h2.
> If I try to include the library in my shrinkwrap java archive with the expression addPackages(true, "com") or with the expression addPackages(true, "org") , the h2 packages are not loaded because shrinkwrap need the name of the resource starting with the same name of the package.
> So seems that shrinkwrap can load only something as a resource called com.h2database combined with the package com.h2 or a resource called org.h2database combined with the package org.h2.
> I presume this ambiguous name should be managed in shrinkwrap
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (SHRINKRES-229) Fix the javadoc to meet JDK 8 requirements
by Matous Jobanek (JIRA)
Matous Jobanek created SHRINKRES-229:
----------------------------------------
Summary: Fix the javadoc to meet JDK 8 requirements
Key: SHRINKRES-229
URL: https://issues.jboss.org/browse/SHRINKRES-229
Project: ShrinkWrap Resolvers
Issue Type: Bug
Affects Versions: 2.2.0-beta-2
Reporter: Matous Jobanek
Assignee: Matous Jobanek
Fix For: 2.2.0
JDK8 and Javadoc has become very strict, maybe to much, but it would be good to go through and fix the main problems before the final release.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (SHRINKWRAP-492) addPackages method not ever succeeds
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/SHRINKWRAP-492?page=com.atlassian.jira.pl... ]
Aslak Knutsen edited comment on SHRINKWRAP-492 at 8/26/15 7:52 PM:
-------------------------------------------------------------------
The root cause seems to be that the h2.jar is packged without 'folder' entires in the zip file. With no folder/directory/package entries Classloader.getResources("org/h2") returns no found which means ShrinkWrap won't see the h2.jar as a possible target for 'deep' scanning.
As en example if you print the entries in the jars
drools.jar:
org/drools/core/event/rule/
org/drools/core/event/rule/impl/
org/drools/core/event/rule/impl/ActivationCancelledEventImpl.class
\h2.jar:
org/h2/bnf/Sentence.java
org/h2/command/Command.java
org/h2/command/CommandContainer.java
org/h2/command/CommandInterface.java
org/h2/command/CommandList.java
org/h2/command/CommandRemote.java
org/h2/command/ddl/AlterIndexRename.java
Not 100% sure how to deal with it yet.. but that's at least the cause :)
A workaround would be to use ShrinkWrap Resolver to resolve the whole h2.jar directly instead of attempting to repackage it
was (Author: aslak):
The root cause seems to be that the h2.jar is packged without 'folder' entires in the zip file. With no folder/directory/package entries Classloader.getResources("org/h2") returns no found which means ShrinkWrap won't see the h2.jar as a possible target for 'deep' scanning.
As en example if you print the entries in the jars
drools.jar:
org/drools/core/event/rule/
org/drools/core/event/rule/impl/
org/drools/core/event/rule/impl/ActivationCancelledEventImpl.class
h2.jar:
org/h2/bnf/Sentence.java
org/h2/command/Command.java
org/h2/command/CommandContainer.java
org/h2/command/CommandInterface.java
org/h2/command/CommandList.java
org/h2/command/CommandRemote.java
org/h2/command/ddl/AlterIndexRename.java
Not 100% sure how to deal with it yet.. but that's at least the cause :)
A workaround would be to use ShrinkWrap Resolver to resolve the whole h2.jar directly instead of attempting to repackage it
> addPackages method not ever succeeds
> ------------------------------------
>
> Key: SHRINKWRAP-492
> URL: https://issues.jboss.org/browse/SHRINKWRAP-492
> Project: ShrinkWrap
> Issue Type: Bug
> Components: impl-base
> Environment: shrinkwrap-impl-base 1.2.2
> Reporter: Luca Stancapiano
>
> there are cases where the addPackages method doesn't succeed to load the packages also if they are in the current classloader. An example can be the com.h2database library. This library is registered as resource in the classloader with the name com.h2database and ambigously it contains the package org.h2.
> If I try to include the library in my shrinkwrap java archive with the expression addPackages(true, "com") or with the expression addPackages(true, "org") , the h2 packages are not loaded because shrinkwrap need the name of the resource starting with the same name of the package.
> So seems that shrinkwrap can load only something as a resource called com.h2database combined with the package com.h2 or a resource called org.h2database combined with the package org.h2.
> I presume this ambiguous name should be managed in shrinkwrap
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (SHRINKWRAP-492) addPackages method not ever succeeds
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/SHRINKWRAP-492?page=com.atlassian.jira.pl... ]
Aslak Knutsen commented on SHRINKWRAP-492:
------------------------------------------
The root cause seems to be that the h2.jar is packged without 'folder' entires in the zip file. With no folder/directory/package entries Classloader.getResources("org/h2") returns no found which means ShrinkWrap won't see the h2.jar as a possible target for 'deep' scanning.
As en example if you print the entries in the jars
drools.jar:
org/drools/core/event/rule/
org/drools/core/event/rule/impl/
org/drools/core/event/rule/impl/ActivationCancelledEventImpl.class
h2.jar:
org/h2/bnf/Sentence.java
org/h2/command/Command.java
org/h2/command/CommandContainer.java
org/h2/command/CommandInterface.java
org/h2/command/CommandList.java
org/h2/command/CommandRemote.java
org/h2/command/ddl/AlterIndexRename.java
Not 100% sure how to deal with it yet.. but that's at least the cause :)
A workaround would be to use ShrinkWrap Resolver to resolve the whole h2.jar directly instead of attempting to repackage it
> addPackages method not ever succeeds
> ------------------------------------
>
> Key: SHRINKWRAP-492
> URL: https://issues.jboss.org/browse/SHRINKWRAP-492
> Project: ShrinkWrap
> Issue Type: Bug
> Components: impl-base
> Environment: shrinkwrap-impl-base 1.2.2
> Reporter: Luca Stancapiano
>
> there are cases where the addPackages method doesn't succeed to load the packages also if they are in the current classloader. An example can be the com.h2database library. This library is registered as resource in the classloader with the name com.h2database and ambigously it contains the package org.h2.
> If I try to include the library in my shrinkwrap java archive with the expression addPackages(true, "com") or with the expression addPackages(true, "org") , the h2 packages are not loaded because shrinkwrap need the name of the resource starting with the same name of the package.
> So seems that shrinkwrap can load only something as a resource called com.h2database combined with the package com.h2 or a resource called org.h2database combined with the package org.h2.
> I presume this ambiguous name should be managed in shrinkwrap
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (SHRINKWRAP-492) addPackages method not ever succeeds
by Luca Stancapiano (JIRA)
[ https://issues.jboss.org/browse/SHRINKWRAP-492?page=com.atlassian.jira.pl... ]
Luca Stancapiano commented on SHRINKWRAP-492:
---------------------------------------------
here a sample:
https://github.com/flashboss/add-packages-test
you can use:
mvn test
The test will start to include two different libraries: drools and h2 with the addPackages("org") method
the first assert succeeds because drools is loaded correctly but the second fails because h2 is not correctly loaded
> addPackages method not ever succeeds
> ------------------------------------
>
> Key: SHRINKWRAP-492
> URL: https://issues.jboss.org/browse/SHRINKWRAP-492
> Project: ShrinkWrap
> Issue Type: Bug
> Components: impl-base
> Environment: shrinkwrap-impl-base 1.2.2
> Reporter: Luca Stancapiano
>
> there are cases where the addPackages method doesn't succeed to load the packages also if they are in the current classloader. An example can be the com.h2database library. This library is registered as resource in the classloader with the name com.h2database and ambigously it contains the package org.h2.
> If I try to include the library in my shrinkwrap java archive with the expression addPackages(true, "com") or with the expression addPackages(true, "org") , the h2 packages are not loaded because shrinkwrap need the name of the resource starting with the same name of the package.
> So seems that shrinkwrap can load only something as a resource called com.h2database combined with the package com.h2 or a resource called org.h2database combined with the package org.h2.
> I presume this ambiguous name should be managed in shrinkwrap
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (SHRINKWRAP-492) addPackages method not ever succeeds
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/SHRINKWRAP-492?page=com.atlassian.jira.pl... ]
Aslak Knutsen moved ARQ-1974 to SHRINKWRAP-492:
-----------------------------------------------
Project: ShrinkWrap (was: Arquillian)
Key: SHRINKWRAP-492 (was: ARQ-1974)
Component/s: impl-base
(was: Deployable Containers SPI)
> addPackages method not ever succeeds
> ------------------------------------
>
> Key: SHRINKWRAP-492
> URL: https://issues.jboss.org/browse/SHRINKWRAP-492
> Project: ShrinkWrap
> Issue Type: Bug
> Components: impl-base
> Environment: shrinkwrap-impl-base 1.2.2
> Reporter: Luca Stancapiano
>
> there are cases where the addPackages method doesn't succeed to load the packages also if they are in the current classloader. An example can be the com.h2database library. This library is registered as resource in the classloader with the name com.h2database and ambigously it contains the package org.h2.
> If I try to include the library in my shrinkwrap java archive with the expression addPackages(true, "com") or with the expression addPackages(true, "org") , the h2 packages are not loaded because shrinkwrap need the name of the resource starting with the same name of the package.
> So seems that shrinkwrap can load only something as a resource called com.h2database combined with the package com.h2 or a resource called org.h2database combined with the package org.h2.
> I presume this ambiguous name should be managed in shrinkwrap
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (SHRINKRES-227) ShrinkWrap Maven Resolver doesn't support env vars in settings.xml
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-227?page=com.atlassian.jira.plu... ]
Matous Jobanek commented on SHRINKRES-227:
------------------------------------------
Hi James,
I've tried it (env vars in settings.xml) and it worked in my case.
There are represented two different errors in the stacktraces you've observed - the first one starting with:
{panel}
at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSecurityDispatcher.getMaster(MavenSecurityDispatcher.java:171)
{panel}
is related to missing {{settings-security.xml}} file. You don't have it on your computer either, that's the reason you are observing this error.
When you put it into the Jenkins instance, the error changed to the second one - starting with:
{panel}
at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.decryptPasswords(MavenSettingsBuilder.java:234)
{panel}
this is related to decrypting passwords - this can be caused by many things such as: wrong master password or wrong encrypted version of your password,...
Have you tried to put the values (username and password) directly into the settings.xml?
Have you followed the steps for password encryption? https://maven.apache.org/guides/mini/guide-encryption.html
> ShrinkWrap Maven Resolver doesn't support env vars in settings.xml
> ------------------------------------------------------------------
>
> Key: SHRINKRES-227
> URL: https://issues.jboss.org/browse/SHRINKRES-227
> Project: ShrinkWrap Resolvers
> Issue Type: Feature Request
> Components: maven
> Reporter: James Rawlings
>
> I get the stacktrace below when using this code on a jenkins instance that uses env vars in the settings.xml
> {code}
> return ShrinkWrap.create(WebArchive.class)
> .addClasses(StringToURL.class, URLToConnection.class, NestingFactoryBean.class, ServiceStringBean.class, ServiceUrlBean.class, ClientProducer.class)
> .addClasses(DeltaspikeTestBase.getDeltaSpikeHolders())
> .addAsWebInfResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml"))
> .addAsLibraries(Maven.resolver().loadPomFromFile("pom.xml")
> .resolve(
> "org.apache.deltaspike.core:deltaspike-core-impl",
> "com.google.mockwebserver:mockwebserver"
> )
> .withTransitivity().as(File.class));
> {code}
> Stacktrace..
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running io.fabric8.cdi.weld.ExtensionTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.51 sec <<< FAILURE! - in io.fabric8.cdi.weld.ExtensionTest
> io.fabric8.cdi.weld.ExtensionTest Time elapsed: 0.51 sec <<< ERROR!
> java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive io.fabric8.cdi.weld.ExtensionTest.createDeployment()
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSecurityDispatcher.getMaster(MavenSecurityDispatcher.java:171)
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSecurityDispatcher.decrypt(MavenSecurityDispatcher.java:96)
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSettingsDecrypter.decrypt(MavenSettingsDecrypter.java:92)
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSettingsDecrypter.decrypt(MavenSettingsDecrypter.java:60)
> at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.decryptPasswords(MavenSettingsBuilder.java:223)
> at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.buildSettings(MavenSettingsBuilder.java:186)
> at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.buildDefaultSettings(MavenSettingsBuilder.java:113)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.<init>(MavenWorkingSessionImpl.java:136)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenResolverSystemImpl.<init>(MavenResolverSystemImpl.java:44)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:244)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstances(SpiServiceLoader.java:208)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.all(SpiServiceLoader.java:79)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.onlyOne(SpiServiceLoader.java:85)
> at org.jboss.shrinkwrap.resolver.spi.loader.ServiceRegistry.onlyOne(ServiceRegistry.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.shrinkwrap.resolver.api.Invokable.invokeMethod(Invokable.java:100)
> at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:91)
> at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:53)
> at org.jboss.shrinkwrap.resolver.api.Resolvers.use(Resolvers.java:68)
> at org.jboss.shrinkwrap.resolver.api.maven.Maven.resolver(Maven.java:36)
> at io.fabric8.cdi.weld.ExtensionTest.createDeployment(ExtensionTest.java:49)
> {code}
> This error is similar to issue https://issues.jboss.org/browse/SHRINKRES-145 however I cannot escape the values in my settings.xml as they need to resolve to env vars.
> Example snippet of my settings.xml..
> {code:xml}
> <servers>
> <server>
> <id>local-nexus</id>
> <username>${env.NEXUS_USERNAME}</username>
> <password>${env.NEXUS_PASSWORD}</password>
> </server>
> <server>
> <id>nexus</id>
> <username>${env.NEXUS_USERNAME}</username>
> <password>${env.NEXUS_PASSWORD}</password>
> </server>
> <server>
> <id>docker-registry</id>
> <username>${env.DOCKER_REGISTRY_USERNAME}</username>
> <password>${env.DOCKER_REGISTRY_PASSWORD}</password>
> </server>
> </servers>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (SHRINKRES-227) ShrinkWrap Maven Resolver doesn't support env vars in settings.xml
by James Rawlings (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-227?page=com.atlassian.jira.plu... ]
James Rawlings commented on SHRINKRES-227:
------------------------------------------
Hi Matous, I tried adding a settings-security.xml file but I still had issues, a similar one to before.
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running io.fabric8.cdi.weld.ExtensionTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.551 sec <<< FAILURE! - in io.fabric8.cdi.weld.ExtensionTest
io.fabric8.cdi.weld.ExtensionTest Time elapsed: 0.551 sec <<< ERROR!
java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive io.fabric8.cdi.weld.ExtensionTest.createDeployment()
at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.decryptPasswords(MavenSettingsBuilder.java:234)
at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.buildSettings(MavenSettingsBuilder.java:186)
at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.buildDefaultSettings(MavenSettingsBuilder.java:113)
at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.<init>(MavenWorkingSessionImpl.java:136)
at org.jboss.shrinkwrap.resolver.impl.maven.MavenResolverSystemImpl.<init>(MavenResolverSystemImpl.java:44)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:244)
at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstances(SpiServiceLoader.java:208)
at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.all(SpiServiceLoader.java:79)
at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.onlyOne(SpiServiceLoader.java:85)
at org.jboss.shrinkwrap.resolver.spi.loader.ServiceRegistry.onlyOne(ServiceRegistry.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.shrinkwrap.resolver.api.Invokable.invokeMethod(Invokable.java:100)
at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:91)
at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:53)
at org.jboss.shrinkwrap.resolver.api.Resolvers.use(Resolvers.java:68)
at org.jboss.shrinkwrap.resolver.api.maven.Maven.resolver(Maven.java:36)
at io.fabric8.cdi.weld.ExtensionTest.createDeployment(ExtensionTest.java:49)
{code}
Are you sure env vars are supported? I just recreated the issue locally by adding the below to my own settings.xml..
{code:xml}
<server>
<id>nexus</id>
<username>${env.NEXUS_USERNAME}</username>
<password>${env.NEXUS_PASSWORD}</password>
</server>
{code}
Which gave me the stacktrace..
{code}
java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive io.fabric8.cdi.weld.ExtensionTest.createDeployment()
at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSecurityDispatcher.getMaster(MavenSecurityDispatcher.java:171)
{code}
Now if I escape the curly brackets the test passes but the env vars are not set properly and therefore I cannot deploy artifacts to nexus.
{code:xml}
<server>
<id>nexus</id>
<username>$\{env.NEXUS_USERNAME\}</username>
<password>$\{env.NEXUS_PASSWORD\}</password>
</server>
{code}
> ShrinkWrap Maven Resolver doesn't support env vars in settings.xml
> ------------------------------------------------------------------
>
> Key: SHRINKRES-227
> URL: https://issues.jboss.org/browse/SHRINKRES-227
> Project: ShrinkWrap Resolvers
> Issue Type: Feature Request
> Components: maven
> Reporter: James Rawlings
>
> I get the stacktrace below when using this code on a jenkins instance that uses env vars in the settings.xml
> {code}
> return ShrinkWrap.create(WebArchive.class)
> .addClasses(StringToURL.class, URLToConnection.class, NestingFactoryBean.class, ServiceStringBean.class, ServiceUrlBean.class, ClientProducer.class)
> .addClasses(DeltaspikeTestBase.getDeltaSpikeHolders())
> .addAsWebInfResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml"))
> .addAsLibraries(Maven.resolver().loadPomFromFile("pom.xml")
> .resolve(
> "org.apache.deltaspike.core:deltaspike-core-impl",
> "com.google.mockwebserver:mockwebserver"
> )
> .withTransitivity().as(File.class));
> {code}
> Stacktrace..
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running io.fabric8.cdi.weld.ExtensionTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.51 sec <<< FAILURE! - in io.fabric8.cdi.weld.ExtensionTest
> io.fabric8.cdi.weld.ExtensionTest Time elapsed: 0.51 sec <<< ERROR!
> java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive io.fabric8.cdi.weld.ExtensionTest.createDeployment()
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSecurityDispatcher.getMaster(MavenSecurityDispatcher.java:171)
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSecurityDispatcher.decrypt(MavenSecurityDispatcher.java:96)
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSettingsDecrypter.decrypt(MavenSettingsDecrypter.java:92)
> at org.jboss.shrinkwrap.resolver.impl.maven.internal.decrypt.MavenSettingsDecrypter.decrypt(MavenSettingsDecrypter.java:60)
> at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.decryptPasswords(MavenSettingsBuilder.java:223)
> at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.buildSettings(MavenSettingsBuilder.java:186)
> at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.buildDefaultSettings(MavenSettingsBuilder.java:113)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.<init>(MavenWorkingSessionImpl.java:136)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenResolverSystemImpl.<init>(MavenResolverSystemImpl.java:44)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:244)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstances(SpiServiceLoader.java:208)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.all(SpiServiceLoader.java:79)
> at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.onlyOne(SpiServiceLoader.java:85)
> at org.jboss.shrinkwrap.resolver.spi.loader.ServiceRegistry.onlyOne(ServiceRegistry.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.shrinkwrap.resolver.api.Invokable.invokeMethod(Invokable.java:100)
> at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:91)
> at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:53)
> at org.jboss.shrinkwrap.resolver.api.Resolvers.use(Resolvers.java:68)
> at org.jboss.shrinkwrap.resolver.api.maven.Maven.resolver(Maven.java:36)
> at io.fabric8.cdi.weld.ExtensionTest.createDeployment(ExtensionTest.java:49)
> {code}
> This error is similar to issue https://issues.jboss.org/browse/SHRINKRES-145 however I cannot escape the values in my settings.xml as they need to resolve to env vars.
> Example snippet of my settings.xml..
> {code:xml}
> <servers>
> <server>
> <id>local-nexus</id>
> <username>${env.NEXUS_USERNAME}</username>
> <password>${env.NEXUS_PASSWORD}</password>
> </server>
> <server>
> <id>nexus</id>
> <username>${env.NEXUS_USERNAME}</username>
> <password>${env.NEXUS_PASSWORD}</password>
> </server>
> <server>
> <id>docker-registry</id>
> <username>${env.DOCKER_REGISTRY_USERNAME}</username>
> <password>${env.DOCKER_REGISTRY_PASSWORD}</password>
> </server>
> </servers>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months