June 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKWRAP-458) addAsWebInfResource doesn't work with Arquillian 1.0.4.Final

by Ron Šmeral (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-458?page=com.atlassian.jira.pl... ] Ron Šmeral updated SHRINKWRAP-458: ---------------------------------- Attachment: shrinkwrap458-reproducer.zip Reproducer attached. > addAsWebInfResource doesn't work with Arquillian 1.0.4.Final > ------------------------------------------------------------ > > Key: SHRINKWRAP-458 > URL: https://issues.jboss.org/browse/SHRINKWRAP-458 > Project: ShrinkWrap > Issue Type: Bug > Components: impl-base > Affects Versions: 1.1.2 > Environment: Arquillian 1.0.4.Final > Reporter: Ron Šmeral > Attachments: shrinkwrap458-reproducer.zip > > > When using {{addAsWebInfResource}} with ShrinkWrap 1.1.2 and Arquillian 1.0.4.Final, the added WEB-INF resources are 0 bytes in size. > With Arquillian 1.0.3.Final this works OK. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-458) addAsWebInfResource doesn't work with Arquillian 1.0.4.Final

by Ron Šmeral (JIRA)

Ron Šmeral created SHRINKWRAP-458: ------------------------------------- Summary: addAsWebInfResource doesn't work with Arquillian 1.0.4.Final Key: SHRINKWRAP-458 URL: https://issues.jboss.org/browse/SHRINKWRAP-458 Project: ShrinkWrap Issue Type: Bug Components: impl-base Affects Versions: 1.1.2 Environment: Arquillian 1.0.4.Final Reporter: Ron Šmeral When using {{addAsWebInfResource}} with ShrinkWrap 1.1.2 and Arquillian 1.0.4.Final, the added WEB-INF resources are 0 bytes in size. With Arquillian 1.0.3.Final this works OK. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-132) MavenImport should have different name

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-132?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-132: ------------------------------------------ Do we want to perform name changes which already concerns 'stable' versions? > MavenImport should have different name > -------------------------------------- > > Key: SHRINKRES-132 > URL: https://issues.jboss.org/browse/SHRINKRES-132 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0 > Reporter: Karel Piwko > Assignee: Andrew Rubinger > Priority: Minor > > MavenImporter is now able to build the project from pom.xml. This means that MavenImporter name is no longer valid, as it does not promote the fact that project will be build from scratch. > It might be MavenBuilder instead. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-132) MavenImport should have different name

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-132?page=com.atlassian.jira.plu... ] Michal Matloka updated SHRINKRES-132: ------------------------------------- Affects Version/s: 2.0.0 > MavenImport should have different name > -------------------------------------- > > Key: SHRINKRES-132 > URL: https://issues.jboss.org/browse/SHRINKRES-132 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0 > Reporter: Karel Piwko > Assignee: Andrew Rubinger > Priority: Minor > > MavenImporter is now able to build the project from pom.xml. This means that MavenImporter name is no longer valid, as it does not promote the fact that project will be build from scratch. > It might be MavenBuilder instead. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] Michal Matloka edited comment on SHRINKRES-140 at 6/25/13 5:06 PM: ------------------------------------------------------------------- Last eclipse aether version was released in february. I have tried then to perform migration https://github.com/mmatloka/resolver/tree/ECLIPSE_AETHER_NOT_WORKING . However as far as I remember the problem was in maven-aether-provider which still uses the sonatype aether. It seems that maven-aether-provider 3.1.0-alpha-1 was relead on 01-Jun-2013 and uses already the eclipse one. Migration concerns import changes, but also they have performed some minor api refactors. was (Author: mmatloka): Last eclipse aether version was released in february. I have tried then to perform migration https://github.com/mmatloka/resolver/tree/ECLIPSE_AETHER_NOT_WORKING . However as far as I remember the problem was in maven-aether-provider. It seems that maven-aether-provider 3.1.0-alpha-1 was relead on 01-Jun-2013 and uses already the eclipse one aether. > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Andrew Rubinger > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-140: ------------------------------------------ Last eclipse aether version was released in february. I have tried then to perform migration https://github.com/mmatloka/resolver/tree/ECLIPSE_AETHER_NOT_WORKING . However as far as I remember the problem was in maven-aether-provider. It seems that maven-aether-provider 3.1.0-alpha-1 was relead on 01-Jun-2013 and uses already the eclipse one aether. > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Andrew Rubinger > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-142) Add User Guide to README.asciidoc

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-142?page=com.atlassian.jira.plu... ] Andrew Rubinger resolved SHRINKRES-142. --------------------------------------- Fix Version/s: 2.0.1 Resolution: Done > Add User Guide to README.asciidoc > --------------------------------- > > Key: SHRINKRES-142 > URL: https://issues.jboss.org/browse/SHRINKRES-142 > Project: ShrinkWrap Resolvers > Issue Type: Task > Reporter: Andrew Rubinger > Assignee: Andrew Rubinger > Fix For: 2.0.1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-142) Add User Guide to README.asciidoc

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKRES-142: ----------------------------------------- Summary: Add User Guide to README.asciidoc Key: SHRINKRES-142 URL: https://issues.jboss.org/browse/SHRINKRES-142 Project: ShrinkWrap Resolvers Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-141) MavenImporter fails when there is no resources directory

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-141?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-141. --------------------------------- > MavenImporter fails when there is no resources directory > -------------------------------------------------------- > > Key: SHRINKRES-141 > URL: https://issues.jboss.org/browse/SHRINKRES-141 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Affects Versions: 2.0.0-beta-3, 2.0.0-beta-5 > Reporter: Michal Matloka > Assignee: Karel Piwko > Fix For: 2.0.0-cr-1 > > > When using the following code: > {code} > ShrinkWrap.create(MavenImporter.class).loadPomFromFile("pom.xml").importBuildOutput() > .as(WebArchive.class); > {code} > and there is no src/main/resources directory, the exception is thrown > {noformat} > java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive com.sth.myIT.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.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.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > 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.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > 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) > ... 56 more > Caused by: java.lang.NullPointerException > at org.jboss.shrinkwrap.resolver.impl.maven.pom.ParsedPomFileImpl$FileUtils.listFiles(ParsedPomFileImpl.java:170) > at org.jboss.shrinkwrap.resolver.impl.maven.pom.ParsedPomFileImpl.getProjectResources(ParsedPomFileImpl.java:83) > at org.jboss.shrinkwrap.resolver.impl.maven.archive.packaging.WarPackagingProcessor.importBuildOutput(WarPackagingProcessor.java:95) > at org.jboss.shrinkwrap.resolver.impl.maven.archive.packaging.WarPackagingProcessor.importBuildOutput(WarPackagingProcessor.java:49) > at org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.PomEquippedMavenImporterImpl.importBuildOutput(PomEquippedMavenImporterImpl.java:49) > at org.jboss.shrinkwrap.resolver.impl.maven.archive.importer.PomEquippedMavenImporterImpl.importBuildOutput(PomEquippedMavenImporterImpl.java:44) > at com.sth.test.ArquillianWarUtils.importBuildOutput(ArquillianWarUtils.java:28) > at com.sth.myIT.createDeployment(myIT.java:33) > ... 61 more > {noformat} > stack from 2.0.0-beta3, but the same situation happens on beta5. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-433) Race condition deadlock in TarGz Exporter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-433?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on SHRINKWRAP-433: ---------------------------------------------------- thradec(a)redhat.com changed the Status of [bug 875031|https://bugzilla.redhat.com/show_bug.cgi?id=875031] from ON_QA to VERIFIED > Race condition deadlock in TarGz Exporter > ----------------------------------------- > > Key: SHRINKWRAP-433 > URL: https://issues.jboss.org/browse/SHRINKWRAP-433 > Project: ShrinkWrap > Issue Type: Bug > Components: impl-base > Affects Versions: 1.0.1 > Environment: RHEL6 32bit + Oracle JDK 6, Oracle JDK 7, OpenJDK 7 > Windows 2008 32 bit + Oracle JDK 7 > Solaris 10 32 bit + Oracle JDK 6, Oracle JDK 7 > Reporter: Karel Piwko > Assignee: Michal Matloka > Fix For: 1.1.1 > > > There is a deadlock which is triggered on various platforms concerning handling of TarGz archives. Concerned environments are listed in the environment field. > Following error is logged by Jenkins > {code} > 11:48:05 Running org.jboss.shrinkwrap.impl.base.exporter.TarGzExporterTestCase > 16:45:04 Build timed out (after 300 minutes). Marking the build as aborted. > {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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues June 2013