[JBoss JIRA] (SHRINKRES-166) org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-166?page=com.atlassian.jira.plu... ]
Karel Piwko commented on SHRINKRES-166:
---------------------------------------
Hi [~abhijitvikash] , what version of ShrinkWrap Resolvers are you using? What Maven version are you using? I'm not able to reproduce the bug, looking for more details.
Thanks,
Karel
> org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> -----------------------------------------------------------
>
> Key: SHRINKRES-166
> URL: https://issues.jboss.org/browse/SHRINKRES-166
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Jboss EAP 6.5, ShrinkWrap, Arquillian, Teiid
> Reporter: Abhijit Vikash
> Priority: Critical
>
> Feb 10, 2014 4:01:18 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogRepositoryListener artifactDescriptorInvalid
> WARNING: Invalid artifact descriptor for org.jboss.teiid:teiid-client:jar:8.2.0.Final: 4 problems were encountered while building the effective model for org.jboss.teiid:teiid-client:8.2.0.Final
> [ERROR] Invalid packaging for parent POM org.jboss.teiid:teiid-parent:8.2.0.Final, must be "pom" but is "jar" @ org.jboss.teiid:teiid-parent:8.2.0.Final
> [ERROR] 'dependencies.dependency.version' for org.jboss.teiid:teiid-common-core:jar is missing. @
> [ERROR] 'dependencies.dependency.version' for org.jboss.teiid:teiid-common-core:test-jar is missing. @
> [ERROR] 'dependencies.dependency.version' for org.jboss.modules:jboss-modules:jar is missing. @
> org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to collect/resolve dependency tree for a resulution due to: The following artifacts could not be resolved: org.hibernate:hibernate-core:jar:4.2.0.Final-redhat-1, org.hibernate:hibernate-entitymanager:jar:4.2.0.Final-redhat-1: Could not transfer artifact org.hibernate:hibernate-core:jar:4.2.0.Final-redhat-1 from/to jboss-ip-repository (http://maven.repository.redhat.com/techpreview/ip6/6.0.0.Beta/maven-repos...): No connector available to access repository jboss-ip-repository (http://maven.repository.redhat.com/techpreview/ip6/6.0.0.Beta/maven-repos...) of type default using the available factories WagonRepositoryConnectorFactory, caused by: No connector available to access repository jboss-ip-repository (http://maven.repository.redhat.com/techpreview/ip6/6.0.0.Beta/maven-repos...) of type default using the available factories WagonRepositoryConnectorFactory
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.wrapException(MavenWorkingSessionImpl.java:497)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.resolveDependencies(MavenWorkingSessionImpl.java:262)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.using(MavenStrategyStageBaseImpl.java:67)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:49)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:38)
> at com.nielsen.engineering.mediaworks.dataservices.services.test.ejb.PanelInfoServiceBeanTest.createArchive(PanelInfoServiceBeanTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:57)
> at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:103)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
> at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1125)
> at org.testng.TestRunner.privateRun(TestRunner.java:749)
> at org.testng.TestRunner.run(TestRunner.java:600)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274)
> at org.testng.SuiteRunner.run(SuiteRunner.java:223)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:995)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:920)
> at org.testng.TestNG.run(TestNG.java:856)
> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:72)
> at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:88)
> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:101)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at $Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> 2014-02-10 16:01:19,285 ERROR [connection:105].handleException(): JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
> Tests run: 15, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 66.118 sec <<< FAILURE!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (SHRINKWRAP-487) Maven Enforcer Dependency Convergence error
by Jakub Narloch (JIRA)
Jakub Narloch created SHRINKWRAP-487:
----------------------------------------
Summary: Maven Enforcer Dependency Convergence error
Key: SHRINKWRAP-487
URL: https://issues.jboss.org/browse/SHRINKWRAP-487
Project: ShrinkWrap
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ext-resolver
Reporter: Jakub Narloch
Priority: Minor
I've got this error when running Maven Enforcer Dependency Convergence rule:
{code}
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Failed while enforcing releasability the error(s) are [
Dependency convergence error for org.apache.maven:maven-model-builder:3.2.1 paths to dependency are:
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-aether-provider:3.2.1
+-org.apache.maven:maven-model-builder:3.2.1
and
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-model-builder:3.1.1
,
Dependency convergence error for org.apache.maven:maven-repository-metadata:3.2.1 paths to dependency are:
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-aether-provider:3.2.1
+-org.apache.maven:maven-repository-metadata:3.2.1
and
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-repository-metadata:3.1.1
]
{code}
Apparently there are two depedencies that were declared in two different versions.
Could you think of any workaround for the current Arquiilain version?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (SHRINKWRAP-486) Maven Enforcer Dependency Convergence error
by Jakub Narloch (JIRA)
Jakub Narloch created SHRINKWRAP-486:
----------------------------------------
Summary: Maven Enforcer Dependency Convergence error
Key: SHRINKWRAP-486
URL: https://issues.jboss.org/browse/SHRINKWRAP-486
Project: ShrinkWrap
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ext-resolver
Reporter: Jakub Narloch
Priority: Minor
I've got this error when running Maven Enforcer Dependency Convergence rule:
{code}
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Failed while enforcing releasability the error(s) are [
Dependency convergence error for org.apache.maven:maven-model-builder:3.2.1 paths to dependency are:
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-aether-provider:3.2.1
+-org.apache.maven:maven-model-builder:3.2.1
and
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-model-builder:3.1.1
,
Dependency convergence error for org.apache.maven:maven-repository-metadata:3.2.1 paths to dependency are:
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-aether-provider:3.2.1
+-org.apache.maven:maven-repository-metadata:3.2.1
and
+-org.springframework.boot:spring-boot-starter-arquillian:1.1.2.BUILD-SNAPSHOT
+-org.jboss.arquillian.extension:arquillian-service-integration-spring-inject:1.0.0.Beta3
+-org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:2.1.0
+-org.apache.maven:maven-repository-metadata:3.1.1
]
{code}
Apparently there are two depedencies that were declared in two different versions.
Could you think of any workaround for the current Arquiilain version?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (SHRINKWRAP-480) Fix order of entries in exported zip file
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/SHRINKWRAP-480?page=com.atlassian.jira.pl... ]
Stefan Bunciak commented on SHRINKWRAP-480:
-------------------------------------------
There was serial processing of Zip entries (which caused failures when trying to create a dir which already existed), however it was already fixed in that library, so my case is fine now. The question is whether this could cause similar errors for other users. It's up to you to decide ;-)
> Fix order of entries in exported zip file
> -----------------------------------------
>
> Key: SHRINKWRAP-480
> URL: https://issues.jboss.org/browse/SHRINKWRAP-480
> Project: ShrinkWrap
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: impl-base
> Affects Versions: 1.2.2
> Reporter: Stefan Bunciak
> Assignee: Michal Matloka
>
> ZipExporter from ShwinkWrap 1.0.1 created zip file with the following structure:
> {code}
> Archive: s-ramp-exporter.jar
> Length Method Size Cmpr Date Time CRC-32 Name
> -------- ------ ------- ---- ---------- ----- -------- ----
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 META-INF/
> 3847 Defl:N 898 77% 03-31-2014 13:36 b04e8666 META-INF/switchyard.xml
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 META-INF/beans.xml
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 org/
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 org/jboss/
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 org/jboss/arquillian/
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 org/jboss/arquillian/container/
> 0 Defl:N 2 0% 03-31-2014 13:36 00000000 org/jboss/arquillian/container/sramp/
> 1881 Defl:N 875 54% 03-31-2014 13:36 21ed2654 org/jboss/arquillian/container/sramp/DeploymentTest.class
> -------- ------- --- -------
> 5728 1787 69% 9 files
> {code}
> Newer versions on ShrinkWrap gave me:
> {code}
> Archive: s-ramp-resource.jar
> Length Method Size Cmpr Date Time CRC-32 Name
> -------- ------ ------- ---- ---------- ----- -------- ----
> 3847 Defl:N 898 77% 03-30-2014 17:45 b04e8666 META-INF/switchyard.xml
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 org/jboss/
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 META-INF/beans.xml
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 org/jboss/arquillian/container/
> 1790 Defl:N 842 53% 03-30-2014 17:45 7a7ed211 org/jboss/arquillian/container/sramp/DeploymentTest.class
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 org/jboss/arquillian/container/sramp/
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 META-INF/
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 org/jboss/arquillian/
> 0 Defl:N 2 0% 03-30-2014 17:45 00000000 org/
> -------- ------- --- -------
> 5637 1754 69% 9 files
> {code}
> Would it be possible to provide users with both exporting mechanisms (single & multi threaded)? By default use the multi-threaded approach.
> I assume this behavior is result of https://issues.jboss.org/browse/SHRINKWRAP-434. It's not against ZIP standard, afaik, however due to such structure I had to revert to older version of ShrinkWrap (I need zip file for further processing by 3rd party library)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (SHRINKRES-188) Support installation of an artifact to a local repository
by Andrew Rubinger (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-188?page=com.atlassian.jira.plu... ]
Andrew Rubinger commented on SHRINKRES-188:
-------------------------------------------
The use cases you mention seem entirely reasonable for local (but not remote) installations. Thank you for raising them. I'd love to hear how [~kpiwko] would approach solving them, as well: in SWR or through some other mechanism.
> Support installation of an artifact to a local repository
> ---------------------------------------------------------
>
> Key: SHRINKRES-188
> URL: https://issues.jboss.org/browse/SHRINKRES-188
> Project: ShrinkWrap Resolvers
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: impl-maven
> Affects Versions: 2.2.0-alpha-2
> Reporter: Tomas Rohovsky
>
> It would be a nice feature to provide installation of an artifact to a local repository.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months
[JBoss JIRA] (SHRINKRES-188) Support installation of an artifact to a local repository
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-188?page=com.atlassian.jira.plu... ]
Stefan Bunciak commented on SHRINKRES-188:
------------------------------------------
Hi [~alrubinger] !
I will just add my use/test case, which consist of deploying Shrinkwrap archive into S-RAMP repository, where this archive is further processed by DTGov. S-RAMP can stand as a maven repository. For the whole test I use Arquillian+Shrinkwrap+Drone, and would be great if wouldn't be forced to use workaround Tomas mentioned (Runtime.getRuntime().exec(...)) and implement the whole use case with Arquilllian framework.
> Support installation of an artifact to a local repository
> ---------------------------------------------------------
>
> Key: SHRINKRES-188
> URL: https://issues.jboss.org/browse/SHRINKRES-188
> Project: ShrinkWrap Resolvers
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: impl-maven
> Affects Versions: 2.2.0-alpha-2
> Reporter: Tomas Rohovsky
>
> It would be a nice feature to provide installation of an artifact to a local repository.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 9 months