July 2013 - shrinkwrap-issues - Jboss List Archives

[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 reassigned SHRINKRES-140: ---------------------------------------- Assignee: Michal Matloka (was: Andrew Rubinger) > 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: Michal Matloka > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-144) Upgrade to Maven 3.1.0

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-144?page=com.atlassian.jira.plu... ] Andrew Rubinger commented on SHRINKRES-144: ------------------------------------------- Upgrade what exactly? :) Aether libraries used in SWR? Or you want to add an enforcer rule to build this w/ Maven 3.1.0 ? > Upgrade to Maven 3.1.0 > ---------------------- > > Key: SHRINKRES-144 > URL: https://issues.jboss.org/browse/SHRINKRES-144 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Reporter: Michal Matloka > Assignee: Michal Matloka > > Maven 3.1.0 was recently released. -- 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-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: ------------------------------------------ Maven 3.1.0 migrated to Eclipse Aether. Although no final versions seems to be released in central, we should consider migration. > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-144) Upgrade to Maven 3.1.0

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-144?page=com.atlassian.jira.plu... ] Michal Matloka updated SHRINKRES-144: ------------------------------------- Affects Version/s: 2.0.0 > Upgrade to Maven 3.1.0 > ---------------------- > > Key: SHRINKRES-144 > URL: https://issues.jboss.org/browse/SHRINKRES-144 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Affects Versions: 2.0.0 > Reporter: Michal Matloka > Assignee: Michal Matloka > > Maven 3.1.0 was recently released. -- 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-144) Upgrade to Maven 3.1.0

by Michal Matloka (JIRA)

Michal Matloka created SHRINKRES-144: ---------------------------------------- Summary: Upgrade to Maven 3.1.0 Key: SHRINKRES-144 URL: https://issues.jboss.org/browse/SHRINKRES-144 Project: ShrinkWrap Resolvers Issue Type: Component Upgrade Reporter: Michal Matloka Assignee: Michal Matloka Maven 3.1.0 was recently released. -- 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-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: ---------------------------------------------------- Marek Schmidt <maschmid(a)redhat.com> changed the Status of [bug 875031|https://bugzilla.redhat.com/show_bug.cgi?id=875031] from VERIFIED to CLOSED > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-444) Deploy fail on ZipException("error in opening zip file") when ShrinkWrap.createFromZipFile is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-444?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on SHRINKWRAP-444: ---------------------------------------------------- Marek Schmidt <maschmid(a)redhat.com> changed the Status of [bug 918442|https://bugzilla.redhat.com/show_bug.cgi?id=918442] from VERIFIED to CLOSED > Deploy fail on ZipException("error in opening zip file") when ShrinkWrap.createFromZipFile is used > -------------------------------------------------------------------------------------------------- > > Key: SHRINKWRAP-444 > URL: https://issues.jboss.org/browse/SHRINKWRAP-444 > Project: ShrinkWrap > Issue Type: Bug > Affects Versions: 1.1.1 > Reporter: Tomas Hradec > Assignee: Andrew Rubinger > Priority: Critical > Fix For: 1.1.2 > > > How to reproduce: > This bug appeared when deploying war archive into EAP 6.0.1. The archive was created by `ShrinkWrap.createFromZipFile(WebArchive.class, new File("path to war"))`. And it has to contain embedded library, which size is greater than few kilobytes, on tiny sizes it didn't appear. > My test archive has following structure and size 670kB. > {code} > test.war: > /WEB-INF/ > /WEB-INF/lib/ > /WEB-INF/lib/hsqldb-1.8.0.10.jar > /WEB-INF/web.xml > /WEB-INF/classes/ > /WEB-INF/classes/org/ > /WEB-INF/classes/org/jboss/ > /WEB-INF/classes/org/jboss/wfk/ > /WEB-INF/classes/org/jboss/wfk/test/ > /WEB-INF/classes/org/jboss/wfk/test/arquillian/ > /WEB-INF/classes/org/jboss/wfk/test/arquillian/HelloWorldServlet.class > {code} > Stack trace: > {code} > org.jboss.arquillian.container.spi.client.container.DeploymentException: Could not deploy to container: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"stub9.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"stub9.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"stub9.war\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: \"/content/stub9.war/WEB-INF/lib/hsqldb-1.8.0.10.jar\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: \"/content/stub9.war/WEB-INF/lib/hsqldb-1.8.0.10.jar\" > Caused by: java.util.zip.ZipException: error in opening zip file"}} > at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:74) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:148) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > 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.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > 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.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > 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.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.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: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.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:300) > 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.Exception: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"stub9.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"stub9.war\".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment \"stub9.war\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: \"/content/stub9.war/WEB-INF/lib/hsqldb-1.8.0.10.jar\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018037: Failed to process WEB-INF/lib: \"/content/stub9.war/WEB-INF/lib/hsqldb-1.8.0.10.jar\" > Caused by: java.util.zip.ZipException: error in opening zip file"}} > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.arquillian.container.ArchiveDeployer.executeDeploymentPlan(ArchiveDeployer.java:91) > at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:58) > ... 88 more > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-459) Misleading exception message when creating an Archive from a Zip file

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-459?page=com.atlassian.jira.pl... ] Michal Matloka resolved SHRINKWRAP-459. --------------------------------------- Resolution: Duplicate Issue SHRINKWRAP-456 > Misleading exception message when creating an Archive from a Zip file > --------------------------------------------------------------------- > > Key: SHRINKWRAP-459 > URL: https://issues.jboss.org/browse/SHRINKWRAP-459 > Project: ShrinkWrap > Issue Type: Bug > Affects Versions: 1.1.2 > Reporter: René Link > Assignee: Michal Matloka > > When I try to create an Archive from a zip file using > ShrinkWrap.createFromZipFile(WebArchive.class, new File("not-existent-file.zip")); > I get: > IllegalArgumentException: File for import exist: not-existent-file.zip > I took a look at the source code and found that the > org.jboss.shrinkwrap.api.ArchiveFactory.createFromZipFile(Class<T>, File) > contains the statement > if (!(archiveFile.exists())) { > throw new IllegalArgumentException("File for import exist: " > + archiveFile.getAbsolutePath()); > } > I guess the exception message should be: File for import does not exist: -- 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] (SHRINKDESC-145) Provide a ManifestBuilder

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-145?page=com.atlassian.jira.pl... ] Andrew Rubinger moved SHRINKWRAP-460 to SHRINKDESC-145: ------------------------------------------------------- Project: ShrinkWrap Descriptors (was: ShrinkWrap) Key: SHRINKDESC-145 (was: SHRINKWRAP-460) > Provide a ManifestBuilder > ------------------------- > > Key: SHRINKDESC-145 > URL: https://issues.jboss.org/browse/SHRINKDESC-145 > Project: ShrinkWrap Descriptors > Issue Type: Task > Reporter: Thomas Diesler > > WildFly has a dependency on [jbosgi-metadata|https://github.com/tdiesler/jbosgi-metadata] because of frequent usage of it's [ManifestBuilder|https://github.com/tdiesler/jbosgi-metadata/blob/master/s...] > Please also consider moving the [OSGiManifestBuilder|https://github.com/tdiesler/jbosgi-metadata/blob/mast...] to shrinkwrap. -- 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-450) Build not working due to lack of JAVA7_HOME environment variable

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-450?page=com.atlassian.jira.pl... ] Andrew Rubinger closed SHRINKWRAP-450. -------------------------------------- > Build not working due to lack of JAVA7_HOME environment variable > ---------------------------------------------------------------- > > Key: SHRINKWRAP-450 > URL: https://issues.jboss.org/browse/SHRINKWRAP-450 > Project: ShrinkWrap > Issue Type: Bug > Reporter: Chris Lowe > Assignee: Michal Matloka > Fix For: 1.1.3 > > > Shrinkwrap nio2-api fails to compile, resulting in the following error: > [INFO] ------------------------------------------------------------------------ > [INFO] Building ShrinkWrap NIO.2 API 1.1.3-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ shrinkwrap-api-nio2 --- > [INFO] Deleting C:\source\external\shrinkwrap\api-nio2\target > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ shrinkwrap-api-nio2 --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ shrinkwrap-api-nio2 --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-environment) @ shrinkwrap-api-nio2 --- > [INFO] > [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ shrinkwrap-api-nio2 --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory C:\source\external\shrinkwrap\api-nio2\src\main\resources > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ shrinkwrap-api-nio2 --- > [INFO] Compiling 4 source files to C:\source\external\shrinkwrap\api-nio2\target\classes > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] Failure executing javac, but could not parse the error: > The system cannot find the path specified. > After some digging into this, it turned out this error was down to a missing environment variable JAVA7_HOME. This is not obvious from the error message. > Currently in the shrinkwrap parent pom.xml there is a check for the JAVA5_HOME. Could an additional check be added at the same point for JAVA7_HOME? -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues July 2013