[ https://issues.jboss.org/browse/JBIDE-16719?page=com.atlassian.jira.plugi... ] Karel Piwko commented on JBIDE-16719: ------------------------------------- bq. Shrinkwrap resolver could search for relative paths in the current working directory and, in case the requested path isn't found, in the directory mentioned in the shrinkwrap.project.home system property. Arquillian Eclipse would set the shrinkwrap.project.home property to the project's home before executing a deployment method. Well, I want to make sure that it works from both CI and IDE. If introducing a new property can fix that, I'll do that. However, it would be better if that works without any property. Why is Arquillan Eclipse actually having problem with currentDirectory != projectDirectory? For test execution it works fine from Eclipse (e.g. in test execution, currentDirectory==projectDirectory). bq. However, what we could do is to use Maven.configureResolverViaPlugin(). This way Eclipse/JBDS will need just to setup a few system properties (pom.xml file, settings.xml file, active profiles etc) and user does not have to handle with it anymore. That won't solve the issue if a user uses the loadPomFromFile method. BTW, the maven.execution.pom-file property isn't mentioned in the documentation. Right, that's something which is set by plugin, so user does not have to fiddle with how it it actually set. If IDE (m2e) has support for the plugin, it would just work. -- 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