[
https://jira.codehaus.org/browse/MANTRUN-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MANTRUN-161.
----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> antrun does not resolve build.xml from classpath
> ------------------------------------------------
>
> Key: MANTRUN-161
> URL: https://jira.codehaus.org/browse/MANTRUN-161
> Project: Maven Antrun Plugin
> Issue Type: Bug
> Affects Versions: 1.6
> Environment: maven-3.0.3
> Reporter: Frank Jakop
>
> I am referencing an ant-file in the configuration of antrun-plugin.
> {noformat}
> <configuration>
> <target>
> <ant antfile="subscripts/build.xml">
> <target name="mytarget"/>
> </ant>
> </target>
> </configuration>
> {noformat}
> The file "subscripts/build.xml" is included in the "src/main/resources"
> folder of a dependency of the antrun-plugin.
> {noformat}
> <dependency>
> <groupId>my.ant</groupId>
> <artifactId>subscripts</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> </dependency>
> {noformat}
> Layout of "my.ant.subscripts" is
> {noformat}
> src
> \main
> \resources
> \subscripts
> \build.xml
> {noformat}
> which is correctly packaged.
> Given the basedir name "basedir", the antrun tells me on execution that the
> file "basedir/subscripts/build.xml" is not found.
> My use-case includes about 30 projects, which execute the same ant target in
> their build lifecycle. I could solve the problem by putting a copy of
> "subscripts/build.xml" in every project's directory, but that is a very bad
> way.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
