May 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-138) MavenSettingsBuilder throws "StringIndexOutOfBoundsException: String index out of range: 1" in static initializers due to regexp in String.replaceAll()

by Torsten Juergeleit (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-138?page=com.atlassian.jira.plu... ] Torsten Juergeleit commented on SHRINKRES-138: ---------------------------------------------- I forgot to mention that we're using only the (global) "settings.xml" from the Maven installation (via env var "M2_HOME"). So we need the fix for [SHRINKRES-127|https://issues.jboss.org/browse/SHRINKRES-127]. > MavenSettingsBuilder throws "StringIndexOutOfBoundsException: String index out of range: 1" in static initializers due to regexp in String.replaceAll() > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-138 > URL: https://issues.jboss.org/browse/SHRINKRES-138 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-beta-4 > Environment: Windows7, Oracle JDK 1.7.0_21 > Reporter: Torsten Juergeleit > Assignee: Andrew Rubinger > Priority: Blocker > > Using ShrinkWrap Maven Resolver 2.0.0-beta-4 on Windows (with File.seperator = "backslash") causes "StringIndexOutOfBoundsException: String index out of range: 1" in static initializers of [MavenSettingsBuilder (line 98)|https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/mai...] due to usage of "String.replaceAll()" (which uses regexp): > {noformat} > java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.acme.vk.service.interfaces.produkt.ProduktsucheServiceLocalEjbIT.createDeployment() > at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160) > 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.apache.openejb.arquillian.openejb.TestObserver.observes(TestObserver.java:55) > 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.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.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > Caused by: java.lang.reflect.InvocationTargetException > 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) > ... 57 more > Caused by: java.lang.RuntimeException: Could not create object from user view > at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:95) > at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:54) > at org.jboss.shrinkwrap.resolver.api.Resolvers.use(Resolvers.java:67) > at org.jboss.shrinkwrap.resolver.api.maven.Maven.resolver(Maven.java:37) > at com.acme.vk.service.interfaces.produkt.ProduktsucheServiceLocalEjbIT.createDeployment(ProduktsucheServiceLocalEjbIT.java:73) > ... 62 more > Caused by: java.lang.reflect.InvocationTargetException > 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.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:91) > ... 66 more > Caused by: java.lang.RuntimeException: Could not create new service instance > at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:240) > at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstances(SpiServiceLoader.java:200) > 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) > ... 71 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:236) > ... 75 more > Caused by: java.lang.ExceptionInInitializerError > at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.<init>(MavenWorkingSessionImpl.java:123) > at org.jboss.shrinkwrap.resolver.impl.maven.MavenResolverSystemImpl.<init>(MavenResolverSystemImpl.java:43) > ... 80 more > Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 1 > at java.lang.String.charAt(String.java:658) > at java.util.regex.Matcher.appendReplacement(Matcher.java:762) > at java.util.regex.Matcher.replaceAll(Matcher.java:906) > at java.lang.String.replaceAll(String.java:2162) > at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.<clinit>(MavenSettingsBuilder.java:98) > ... 82 more > {noformat} > The bloody details fr the reason of this exception can be found [here|http://stackoverflow.com/questions/13714722/replaceall-with-file-sep...] or [here|http://stackoverflow.com/questions/1049103/why-am-i-getting-a-string...] or [here|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6523151]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-138) MavenSettingsBuilder throws "StringIndexOutOfBoundsException: String index out of range: 1" in static initializers due to regexp in String.replaceAll()

by Torsten Juergeleit (JIRA)

Torsten Juergeleit created SHRINKRES-138: -------------------------------------------- Summary: MavenSettingsBuilder throws "StringIndexOutOfBoundsException: String index out of range: 1" in static initializers due to regexp in String.replaceAll() Key: SHRINKRES-138 URL: https://issues.jboss.org/browse/SHRINKRES-138 Project: ShrinkWrap Resolvers Issue Type: Bug Components: impl-maven Affects Versions: 2.0.0-beta-4 Environment: Windows7, Oracle JDK 1.7.0_21 Reporter: Torsten Juergeleit Assignee: Andrew Rubinger Priority: Blocker Using ShrinkWrap Maven Resolver 2.0.0-beta-4 on Windows (with File.seperator = "backslash") causes "StringIndexOutOfBoundsException: String index out of range: 1" in static initializers of [MavenSettingsBuilder (line 98)|https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/mai...] due to usage of "String.replaceAll()" (which uses regexp): {noformat} java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.acme.vk.service.interfaces.produkt.ProduktsucheServiceLocalEjbIT.createDeployment() at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160) 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.apache.openejb.arquillian.openejb.TestObserver.observes(TestObserver.java:55) 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.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.junit.Arquillian$2.evaluate(Arquillian.java:182) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.reflect.InvocationTargetException 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) ... 57 more Caused by: java.lang.RuntimeException: Could not create object from user view at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:95) at org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:54) at org.jboss.shrinkwrap.resolver.api.Resolvers.use(Resolvers.java:67) at org.jboss.shrinkwrap.resolver.api.maven.Maven.resolver(Maven.java:37) at com.acme.vk.service.interfaces.produkt.ProduktsucheServiceLocalEjbIT.createDeployment(ProduktsucheServiceLocalEjbIT.java:73) ... 62 more Caused by: java.lang.reflect.InvocationTargetException 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.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:91) ... 66 more Caused by: java.lang.RuntimeException: Could not create new service instance at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:240) at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstances(SpiServiceLoader.java:200) 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) ... 71 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.jboss.shrinkwrap.resolver.spi.loader.SpiServiceLoader.createInstance(SpiServiceLoader.java:236) ... 75 more Caused by: java.lang.ExceptionInInitializerError at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.<init>(MavenWorkingSessionImpl.java:123) at org.jboss.shrinkwrap.resolver.impl.maven.MavenResolverSystemImpl.<init>(MavenResolverSystemImpl.java:43) ... 80 more Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 1 at java.lang.String.charAt(String.java:658) at java.util.regex.Matcher.appendReplacement(Matcher.java:762) at java.util.regex.Matcher.replaceAll(Matcher.java:906) at java.lang.String.replaceAll(String.java:2162) at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenSettingsBuilder.<clinit>(MavenSettingsBuilder.java:98) ... 82 more {noformat} The bloody details fr the reason of this exception can be found [here|http://stackoverflow.com/questions/13714722/replaceall-with-file-sep...] or [here|http://stackoverflow.com/questions/1049103/why-am-i-getting-a-string...] or [here|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6523151]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-16) Write purpose statement and key goals document for Resolvers

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-16?page=com.atlassian.jira.plug... ] Andrew Rubinger resolved SHRINKRES-16. -------------------------------------- Fix Version/s: (was: 2.0.0-beta-4) Resolution: Rejected Rejecting simply to dis-associate this issue from a particular release version, though the beginnings of a User Guide covering these issues are in place in the "Continuous Enterprise Development in Java" book and will be soon making their way to Arquillian.org as well. https://github.com/arquillian/continuous-enterprise-development/commit/23... > Write purpose statement and key goals document for Resolvers > ------------------------------------------------------------ > > Key: SHRINKRES-16 > URL: https://issues.jboss.org/browse/SHRINKRES-16 > Project: ShrinkWrap Resolvers > Issue Type: Task > Affects Versions: 1.1.0-alpha-2 > Reporter: Dan Allen > Assignee: Andrew Rubinger > > Write a purpose statement and key goals for Resolvers. > This are "alpha"-stage documentation that serves two purposes: > 1. makes sure you know where you are aiming, so you don't lose your way > 2. allows other people to know what you are going for so they can help > The text should remain fairly high-level. In a sense they are the requirements transcribed into purpose. > Try to answer the following questions while writing it: > 1. Why are you creating this software? What is the need? > 2. How does the software plan to address this need? (e.g., fluent api for resolving artifacts, focusing initially on Maven resolution facility) > 3. What stage is the software in? Where is it headed? > To keep this task as lightweight as possible, the text can be drafted in a lightweight markup language such as markdown (though reStructuredText is preferred). > The github repository wiki for ShrinkWrap Resolvers is preferred for hosting the draft (can be managed via the web UI or as a git repository). > https://github.com/shrinkwrap/resolver/wiki > The wiki supports just about all the lightweight markup languages, one of them being reStructuredText. See reference here: http://docutils.sourceforge.net/docs/user/rst/quickref.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-136) System scoped dependencies shouldn't be added to WAR

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-136?page=com.atlassian.jira.plu... ] Andrew Rubinger resolved SHRINKRES-136. --------------------------------------- Resolution: Done Resolved alongside SHRINKRES-112 > System scoped dependencies shouldn't be added to WAR > ---------------------------------------------------- > > Key: SHRINKRES-136 > URL: https://issues.jboss.org/browse/SHRINKRES-136 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.0.0-beta-3 > Reporter: Ron Šmeral > Assignee: Karel Piwko > Fix For: 2.0.0-beta-4 > > > When resolving dependencies with {{importRuntimeDependencies}} and adding them to an archive as in > {code} > File[] libs = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeDependencies().asFile(); > ShrinkWrap.create(WebArchive.class, "seam-blog.war").addAsLibraries(libs); > {code} > system-scoped dependencies are resolved and added to the archive as well. > This should not happen and should be aligned with the behaviour of the maven war plugin, as described in this issue: https://jira.codehaus.org/browse/MWAR-23. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-112) MavenImporter ignores AcceptScopesStrategy for dependency inclusion

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-112?page=com.atlassian.jira.plu... ] Andrew Rubinger commented on SHRINKRES-112: ------------------------------------------- Upstream: https://github.com/shrinkwrap/resolver/commit/eee2a42556709dd5c228b7fa8b7... > MavenImporter ignores AcceptScopesStrategy for dependency inclusion > ------------------------------------------------------------------- > > Key: SHRINKRES-112 > URL: https://issues.jboss.org/browse/SHRINKRES-112 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Blocker > Fix For: 2.0.0-beta-4 > > > AcceptScopesStrategy is not correctly propagated: > {code} > @Deployment(testable = false) > public static WebArchive createDeployment() > { > return ShrinkWrap.create(MavenImporter.class) > .loadPomFromFile("pom.xml") > .importBuildOutput(new AcceptScopesStrategy(ScopeType.COMPILE, ScopeType.RUNTIME)) > .as(WebArchive.class); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-133) RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-133?page=com.atlassian.jira.plu... ] Andrew Rubinger resolved SHRINKRES-133. --------------------------------------- Resolution: Done Resolved alongside SHRINKRES-112 > RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way > --------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-133 > URL: https://issues.jboss.org/browse/SHRINKRES-133 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.0.0-beta-3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.0.0-beta-4 > > > It is unclear what should happen if you use RejectDependencies Filter/Strategy. > Currently, it does: > 1/ Reject in preResolution -> that means dependency is removed including all possible transtives > 2/ Reject in resolution -> removed during resolution, not including transitives > We need to cover both use cases especially with SHRINKRES-112 changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-112) MavenImporter ignores AcceptScopesStrategy for dependency inclusion

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-112?page=com.atlassian.jira.plu... ] Andrew Rubinger resolved SHRINKRES-112. --------------------------------------- Assignee: Karel Piwko Resolution: Done > MavenImporter ignores AcceptScopesStrategy for dependency inclusion > ------------------------------------------------------------------- > > Key: SHRINKRES-112 > URL: https://issues.jboss.org/browse/SHRINKRES-112 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Priority: Blocker > Fix For: 2.0.0-beta-4 > > > AcceptScopesStrategy is not correctly propagated: > {code} > @Deployment(testable = false) > public static WebArchive createDeployment() > { > return ShrinkWrap.create(MavenImporter.class) > .loadPomFromFile("pom.xml") > .importBuildOutput(new AcceptScopesStrategy(ScopeType.COMPILE, ScopeType.RUNTIME)) > .as(WebArchive.class); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-133) RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-133?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-133: ---------------------------------- Component/s: impl-maven > RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way > --------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-133 > URL: https://issues.jboss.org/browse/SHRINKRES-133 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.0.0-beta-3 > Reporter: Karel Piwko > Assignee: Karel Piwko > > It is unclear what should happen if you use RejectDependencies Filter/Strategy. > Currently, it does: > 1/ Reject in preResolution -> that means dependency is removed including all possible transtives > 2/ Reject in resolution -> removed during resolution, not including transitives > We need to cover both use cases especially with SHRINKRES-112 changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-133) RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-133?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-133: ---------------------------------- Fix Version/s: 2.0.0-beta-4 > RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way > --------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-133 > URL: https://issues.jboss.org/browse/SHRINKRES-133 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.0.0-beta-3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: 2.0.0-beta-4 > > > It is unclear what should happen if you use RejectDependencies Filter/Strategy. > Currently, it does: > 1/ Reject in preResolution -> that means dependency is removed including all possible transtives > 2/ Reject in resolution -> removed during resolution, not including transitives > We need to cover both use cases especially with SHRINKRES-112 changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-133) RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-133?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-133: ---------------------------------- Affects Version/s: 2.0.0-beta-3 > RejectDependenciesFilter and strategy should be able to work in both recursive and nonrecursive way > --------------------------------------------------------------------------------------------------- > > Key: SHRINKRES-133 > URL: https://issues.jboss.org/browse/SHRINKRES-133 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Affects Versions: 2.0.0-beta-3 > Reporter: Karel Piwko > Assignee: Karel Piwko > > It is unclear what should happen if you use RejectDependencies Filter/Strategy. > Currently, it does: > 1/ Reject in preResolution -> that means dependency is removed including all possible transtives > 2/ Reject in resolution -> removed during resolution, not including transitives > We need to cover both use cases especially with SHRINKRES-112 changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 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 2013