September 2014 - shrinkwrap-issues

[JBoss JIRA] (SHRINKRES-204) Broken filtering of archives via MavenImporter on Windows

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-204: ------------------------------------- Summary: Broken filtering of archives via MavenImporter on Windows Key: SHRINKRES-204 URL: https://issues.jboss.org/browse/SHRINKRES-204 Project: ShrinkWrap Resolvers Issue Type: Bug Components: impl-maven Affects Versions: 2.2.0-alpha-2 Reporter: Karel Piwko MavenImporter ignores resource filtering - inclusions are not a part of resulting archives on Windows platform. It is unclear whether this is a bug in implementation or in test bed. To be investigated. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-203) Maven Plugin cannot be compiled with Maven 3.2.3

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-203: ------------------------------------- Summary: Maven Plugin cannot be compiled with Maven 3.2.3 Key: SHRINKRES-203 URL: https://issues.jboss.org/browse/SHRINKRES-203 Project: ShrinkWrap Resolvers Issue Type: Bug Components: maven-plugin Affects Versions: 2.2.0-alpha-2 Reporter: Karel Piwko Verify goal fails during dependency:tree execution via Maven Invoker plugin when Maven 3.2.3 is used to build the project. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-202) withClassPathResolution method in ConfigurableMavenResolverSystemImpl ignores parameter

by Daniele Gaffuri (JIRA)

Daniele Gaffuri created SHRINKRES-202: ----------------------------------------- Summary: withClassPathResolution method in ConfigurableMavenResolverSystemImpl ignores parameter Key: SHRINKRES-202 URL: https://issues.jboss.org/browse/SHRINKRES-202 Project: ShrinkWrap Resolvers Issue Type: Bug Components: impl-maven Affects Versions: 2.1.1 Reporter: Daniele Gaffuri Priority: Minor The implementation of withClassPathResolution in org.jboss.shrinkwrap.resolver.impl.maven.ConfigurableMavenResolverSystemImpl ignores its parameter and always disables resolution {code} public ConfigurableMavenResolverSystem withClassPathResolution(boolean useClassPathResolution) { getMavenWorkingSession().disableClassPathWorkspaceReader(); return this; } {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[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 resolved SHRINKRES-166. ----------------------------------- Resolution: Incomplete Description I'm closing this issue as I'm not able to reproduce the bug and instruction are not complete. > org.jboss.shrinkwrap.resolver.api.NoResolvedResultException > ----------------------------------------------------------- > > Key: SHRINKRES-166 > URL: https://issues.jboss.org/browse/SHRINKRES-166 > Project: ShrinkWrap Resolvers > Issue Type: Bug > 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.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-201) Allow Gradle import from custom build location

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-201?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-201: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 2.2.0-alpha-3 Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/25d253a5db0a52f8204a8f1ff35... > Allow Gradle import from custom build location > ---------------------------------------------- > > Key: SHRINKRES-201 > URL: https://issues.jboss.org/browse/SHRINKRES-201 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-alpha-3 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-201) Allow Gradle import from custom build location

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-201?page=com.atlassian.jira.plu... ] Michal Matloka updated SHRINKRES-201: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/shrinkwrap/resolver/pull/74 > Allow Gradle import from custom build location > ---------------------------------------------- > > Key: SHRINKRES-201 > URL: https://issues.jboss.org/browse/SHRINKRES-201 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-201) Allow Gradle import from custom build location

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-201?page=com.atlassian.jira.plu... ] Michal Matloka updated SHRINKRES-201: ------------------------------------- Summary: Allow Gradle import from custom build location (was: Allow import from custom build location) > Allow Gradle import from custom build location > ---------------------------------------------- > > Key: SHRINKRES-201 > URL: https://issues.jboss.org/browse/SHRINKRES-201 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-201) Allow import from custom build location

by Michal Matloka (JIRA)

Michal Matloka created SHRINKRES-201: ---------------------------------------- Summary: Allow import from custom build location Key: SHRINKRES-201 URL: https://issues.jboss.org/browse/SHRINKRES-201 Project: ShrinkWrap Resolvers Issue Type: Sub-task Reporter: Michal Matloka Assignee: Michal Matloka -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-181?page=com.atlassian.jira.plu... ] Michal Matloka updated SHRINKRES-181: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/shrinkwrap/resolver/pull/73 > 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: Michal Matloka > 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.3.1#6329)

9 years, 7 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-181?page=com.atlassian.jira.plu... ] Michal Matloka reassigned SHRINKRES-181: ---------------------------------------- Assignee: Michal Matloka > 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: Michal Matloka > 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.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues September 2014