[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-500) Configuring from settings.xml fails if there is a Travis ${env.VAR} in <password>

Configuring from settings.xml fails if there is a Travis ${env.VAR} in <password> --------------------------------------------------------------------------------- Key: SHRINKWRAP-500 URL: https://issues.jboss.org/browse/SHRINKWRAP-500 Project: ShrinkWrap Issue Type: Bug Reporter: Peter Palaga [~aslak] and [~mjobanek] this is the issue I told you about in Peagas about two weeks ago We have a code like this in {{createDeployment() }}: {code} File[] libs = Maven.configureResolver().fromFile(shrinkwrapMavenSettings).loadPomFromFile("pom.xml") .resolve("org.hawkular.commons:hawkular-rest-status", "com.squareup.okhttp:okhttp") .withTransitivity().asFile(); {code} If {{shrinkwrapMavenSettings}} points to a settings.xml file that contains something like the following {code} <servers> <server> <id>jboss-snapshots-repository</id> <username>${env.NEXUS_DEPLOY_USERNAME}</username> <password>${env.NEXUS_DEPLOY_PASSWORD}</password> </server> </servers> {code} then the above snippet fails with {code} java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.hawkular.commons.rest.status.itest.StatusEndpointITest.createDeployment() at org.hawkular.commons.rest.status.itest.StatusEndpointITest.createDeployment(StatusEndpointITest.java:52){code} I admit the Exception of the message is not very helpful, but that's what I get from Maven. We have a workaround in place https://github.com/hawkular/hawkular-commons/blob/8664a3ebb8920349396949e... The commit in the following PR deactivates the workaround and shows the issue https://github.com/hawkular/hawkular-commons/pull/48