[
https://issues.apache.org/jira/browse/MANTRUN-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MANTRUN-171.
----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> maven.compile.classpath should not contain target/classes when packaging=POM
> ----------------------------------------------------------------------------
>
> Key: MANTRUN-171
> URL: https://issues.apache.org/jira/browse/MANTRUN-171
> Project: Maven Antrun Plugin
> Issue Type: Improvement
> Affects Versions: 1.7
> Environment: Maven 3.0.3
> Reporter: Frank Schwarz
>
> {code}
> <plugin>
> <artifactId>maven-antrun-plugin</artifactId>
> <version>1.7</version>
> <executions>
> <execution>
> <configuration>
> <target>
> <property name="path" refid="maven.compile.classpath" />
> <echo message="${path}" />
> </target>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> This will print out (besides others) "target/classes", although the
> packaging-type of the enclosing pom.xml is "POM".
> IMHO there cannot be any compiled classes in this case, so please leave it
> out.
> (My actual use-case: I would like to process all declared dependencies in the
> antrun-section, so "target/classes" makes me trouble.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
