maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <>
Subject [jira] Closed: (MANTRUN-104) Documentation for referring to artifacts classpaths is wrong
Date Wed, 01 Jul 2009 22:21:05 GMT


Paul Gier closed MANTRUN-104.

    Resolution: Duplicate

This was fixed in MANTRUN-110

> Documentation for referring to artifacts classpaths is wrong
> ------------------------------------------------------------
>                 Key: MANTRUN-104
>                 URL:
>             Project: Maven 2.x Antrun Plugin
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Andreas Kohn
>            Assignee: Paul Gier
>             Fix For: 1.4
> The documentation on
claims that referring to the path of an artifact can be accomplished with 
> {code}
> <property name="mvn.dependency.jar" refid=""/>
> {code}
> This is using the wrong separators, ':' does not work. Instead, one needs to use '.',
like this:
> {code}
> <property name="mvn.dependency.jar" refid=""/>
> {code}
> Also while there: it would be nice to have the documentation be clear about the fact
that the classifier part is only set if a classifier is defined on the artifact. For an artifact
without classifier, the property would be called
> And of course, 'jar' should be replaced by 'type' to match the other parts.
> This information now has to be found by trying the documented way, seeing it fail, and
then scanning through the debug output which eventually says:
> {quote}
> [INFO] [antrun:run {execution: build}]
> [DEBUG] Storing: maven.dependency.rhino.js.jar.path=/home/andreask/.m2/repository/rhino/js/1.7R1/js-1.7R1.jar
> {quote}

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message