[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-223) ClasspathWorkspaceReader does not resolve version variables

Thorsten Meinl (JIRA) issues at jboss.org
Tue Jun 30 05:27:02 EDT 2015


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

Thorsten Meinl updated SHRINKRES-223:
-------------------------------------
    Attachment: resolver-bug.zip


Here are three project to reproduce the problem. Try to run projectB/Test and it will fail because it cannot resolve com.knime:projectA. The version of com.knime:projectA is a veriable defined in com.knime:config (${com.knime.a.version}). The dependency in com.knime:projectB uses this version variable and it is resolved correctly to 5.2.0-SNAPSHOT. However, the resolution does not resolve in in com.knime:projectA. If you set the version there to the constant "5.2.0-SNAPSHOT" then it works as expected.

> ClasspathWorkspaceReader does not resolve version variables
> -----------------------------------------------------------
>
>                 Key: SHRINKRES-223
>                 URL: https://issues.jboss.org/browse/SHRINKRES-223
>             Project: ShrinkWrap Resolvers
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 2.2.0-beta-2
>            Reporter: Thorsten Meinl
>         Attachments: resolver-bug.zip
>
>
> The ClasspathWorkspaceReader does not resolve variables in artifact versions. We have an artifact whose version is a variable that is defined in its parent pom. "ClasspathWorkspaceReader.createFoundArtifact" reads the variable as-is and does not resolve it to the real version. However, when resolving the dependencies for the "root" artifacts (the one whose pom has been loaded by the resolver via "loadPomFromFile") version variables *are* resolved and therefore there will always be a mismatch.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the shrinkwrap-issues mailing list