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

[Matous Jobanek (JIRA)]

     [ https://issues.jboss.org/browse/SHRINKRES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed SHRINKRES-240.
------------------------------------
    Fix Version/s: 2.2.2
       Resolution: Duplicate Issue


I'm closing this issue as it should be already fixed. 
Feel free to reopen it if you still observe unexpected behaviour. 

> Configuring from settings.xml fails if there is a Travis ${env.VAR} in <password>
> ---------------------------------------------------------------------------------
>
>                 Key: SHRINKRES-240
>                 URL: https://issues.jboss.org/browse/SHRINKRES-240
>             Project: ShrinkWrap Resolvers
>          Issue Type: Bug
>            Reporter: Peter Palaga
>            Assignee: Matous Jobanek
>             Fix For: 2.2.2
>
>
> [~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/8664a3ebb8920349396949e6cc4f5991b2469524/hawkular-nest/hawkular-nest-itest/pom.xml#L181
> The commit in the following PR deactivates the workaround and shows the issue
>  https://github.com/hawkular/hawkular-commons/pull/48 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)