${user.home} works in the following way for antrun 1.0, but not sure if it
is ok for 2.0. As I know antrun 2.0 does not create a correct classpath
(maven.dependency.classpath).

        <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-antrun-plugin</artifactId>
                <version>1.0</version>
                <executions>
                        <execution>
                                <id>createDB</id>
                                <phase>test</phase>
                                <configuration>
                                        <tasks>
                                                <property 
file="${user.home}/.m2/build.properties" />
                                                <ant dir="." inheritrefs="true" 
inheritAll="true" antfile="build.xml"
target="antTarget" />
                                        </tasks>
                                </configuration>
                                <goals>
                                        <goal>run</goal>
                                </goals>
                        </execution>
                </executions>
        </plugin>

Regards,

Bill



-----Original Message-----
From: Prasad Kashyap [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 21, 2006 10:18 AM
To: Maven Users List
Subject: Re: [m2] antrun cant find user.home


Don't know if that is a bug but I've used ${settings.localRespository}
to get to the m2 repository.

Cheers
Prasad

On 2/21/06, Roland Kofler <[EMAIL PROTECTED]> wrote:
> when executing an antrun script
> <property name="maven.repo.local" value="${user.home}/.m2/repository" />
>
> the ${user.home} variable isn't translated and outputs
>  C:\Dokumente und
>
Einstellungen\roland.kofler\systemone\core\${user.home}\.m2\repository\at\sy
stemone\core\...
>
> is this an antrun-plugin bug?
>
> thanks,
> roland
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to