Problem in resolving artifact version

Mar 13, 2010 at 3:59 AM
Edited Mar 13, 2010 at 4:00 AM

In Maven, we can avoid specifying the literal version number for a dependency, and instead use a variable such as ${project.version} that is resolved at runtime to the version string.

<project>

...

<version>1.0.0.0</version>
<packaging>library</packaging>

<dependency>
        <groupId>group</groupId>
        <artifactId>artifact</artifactId>
        <type>library</type>
        <version>${project.version}</version>
</dependency>

...

</project>

Unfortunately, this fails with NPanday 1.1 during mvn install as follows:

INFO: NPANDAY-180-018: Retrieving artifact: Artifact ID  = example
java.io.IOException: NPANDAY-180-020: Problem in resolving artifact: Assembly Artifact Id = artifact, Type = library, Local Path Check = /home/jfallows/.m2/uac/gac_msil/artifact/${project.version}__group/artifact.dll, Message = Unable to download the artifact from any repository

Is this a known issue with NPanday?

Kind Regards.

Coordinator
Mar 14, 2010 at 11:43 PM

http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=9603

There are a class of issues related to the fact that the original NMaven code re-implemented some Maven functionality using an RDF repository and a clone of the local repository to avoid assembly naming issues. We're planning to strip this back to use Maven libraries more directly to avoid these types of problems in the future. You'll also find you can't use dependencyManagement unfortunately.