[ https://issues.jboss.org/browse/SHRINKRES-42?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-42: ------------------------------------------ What's the use case? Why try to resolve a known File path via the ShrinkWrap Maven Resolver? Why not simply import it as a new ShrinkWrap archive from the file? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKRES-42?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-42: ------------------------------------------ Ah I see, you're importing a full POM, not attempting to manually specify a dependency element programatically. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKRES-42?page=com.atlassian.jira.plug... ] Andrew Rubinger commented on SHRINKRES-42: ------------------------------------------ Test cases appreciated; if you can submit a pull request for the case mentioned it can accelerate our ability to fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKRES-42?page=com.atlassian.jira.plug... ] Andrew Rubinger updated SHRINKRES-42: ------------------------------------- Summary: Import of POM Metadata does not account for System Properties (was: MavenDependencyResolver is unable to resolve absolute paths) Description: When using MavenDependencyResolver and dependencies with system scope, i.e. {noformat} <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> {noformat} I get an exception saying that shrinkwrap requires absolute path. at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:154) at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:126) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.loadMetadataFromPom(MavenBuilderImpl.java:153) at org.jboss.qa.brms.container.tools.ContainerTestWrapper.getDroolsDependencies(ContainerTestWrapper.java:73) at org.jboss.qa.brms.container.tools.ContainerTestWrapper.createTestsEar(ContainerTestWrapper.java:35) at org.jboss.qa.brms.container.tools.ManualContainerTestWrapper.deployManual(ManualContainerTestWrapper.java:27) ... 79 more Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.jboss.qa:brms:5.3.0.BRMS-ER6 [ERROR] 'dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${java.home}/../lib/tools.jar @ {code} was: When using MavenDependencyResolver and dependencies with system scope, i.e. {noformat} <dependency> <groupId>com.sun</groupId> <artifactId>tools</artifactId> <version>1.6</version> <scope>system</scope> <systemPath>${java.home}/../lib/tools.jar</systemPath> </dependency> {noformat} I get an exception saying that shrinkwrap requires absolute path. True issue is that system properties aren't resolved; changed the issue to reflect this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira