You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Adam Krieg <ak...@pragmatrading.com> on 2010/07/15 00:06:16 UTC
antrun plugin resolving properties referencing properties
I'm trying to access the project.build.directory property which is defined in my pom as
<build>
<directory>${project.basedir}/target</directory>
....
In ant I have this setup:
<artifact:pom id="project-pom" file="pom.xml" />
<property name="outputdir" value="${project-pom.build.directory}"/>
However when I run my ant build, outputdir is being set to the literal value "${project.basedir}/target" rather than antrun expanding the variable ${project.basedir}. Has anyone else run into this issue?
________________________________
Disclaimer: http://pragmatrading.com/disclaimer.html
Re: antrun plugin resolving properties referencing properties
Posted by Hervé BOUTEMY <he...@free.fr>.
it seems this is a known bug in maven-ant-tasks 2.1.0:
http://jira.codehaus.org/browse/MANTTASKS-179
please confirm that you don't have the problem when using maven-ant-tasks
2.0.9
Regards,
Hervé
Le jeudi 15 juillet 2010, Adam Krieg a écrit :
> I'm trying to access the project.build.directory property which is defined
> in my pom as
>
> <build>
> <directory>${project.basedir}/target</directory>
> ....
>
> In ant I have this setup:
> <artifact:pom id="project-pom" file="pom.xml" />
> <property name="outputdir" value="${project-pom.build.directory}"/>
>
> However when I run my ant build, outputdir is being set to the literal
> value "${project.basedir}/target" rather than antrun expanding the
> variable ${project.basedir}. Has anyone else run into this issue?
>
>
>
> ________________________________
> Disclaimer: http://pragmatrading.com/disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven ant tasks resolving properties referencing properties
Posted by Adam Krieg <ak...@pragmatrading.com>.
Well the thing is, I am using the default. I deduced the value from looking at the pom-4.0.0.xml that comes with maven.
-----Original Message-----
From: Shan Syed [mailto:shan.ss@gmail.com]
Sent: Wednesday, July 14, 2010 6:45 PM
To: Maven Users List
Subject: Re: Maven ant tasks resolving properties referencing properties
that's weird - I think your syntax is correct
there's an example here:
http://hohonuuli.blogspot.com/2007/03/boostrapping-mavens-antlib-maven.html
what happens if you remove the directory value from your pom and allow
it to use the default?
On Wed, Jul 14, 2010 at 6:27 PM, Adam Krieg <ak...@pragmatrading.com> wrote:
> Forgive me, I meant Maven ant tasks. I'm trying to reference information defined in the pom from my build.xml.
>
> -----Original Message-----
> From: Shan Syed [mailto:shan.ss@gmail.com]
> Sent: Wednesday, July 14, 2010 6:23 PM
> To: Maven Users List
> Subject: Re: antrun plugin resolving properties referencing properties
>
> just to clarify, are you using the antrun plugin for maven or the
> maven tasks for ant?
>
>
> On Wed, Jul 14, 2010 at 6:06 PM, Adam Krieg <ak...@pragmatrading.com> wrote:
>> I'm trying to access the project.build.directory property which is defined in my pom as
>>
>> <build>
>> <directory>${project.basedir}/target</directory>
>> ....
>>
>> In ant I have this setup:
>> <artifact:pom id="project-pom" file="pom.xml" />
>> <property name="outputdir" value="${project-pom.build.directory}"/>
>>
>> However when I run my ant build, outputdir is being set to the literal value "${project.basedir}/target" rather than antrun expanding the variable ${project.basedir}. Has anyone else run into this issue?
>>
>>
>>
>> ________________________________
>> Disclaimer: http://pragmatrading.com/disclaimer.html
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> Disclaimer: http://pragmatrading.com/disclaimer.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Disclaimer: http://pragmatrading.com/disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven ant tasks resolving properties referencing properties
Posted by Shan Syed <sh...@gmail.com>.
that's weird - I think your syntax is correct
there's an example here:
http://hohonuuli.blogspot.com/2007/03/boostrapping-mavens-antlib-maven.html
what happens if you remove the directory value from your pom and allow
it to use the default?
On Wed, Jul 14, 2010 at 6:27 PM, Adam Krieg <ak...@pragmatrading.com> wrote:
> Forgive me, I meant Maven ant tasks. I'm trying to reference information defined in the pom from my build.xml.
>
> -----Original Message-----
> From: Shan Syed [mailto:shan.ss@gmail.com]
> Sent: Wednesday, July 14, 2010 6:23 PM
> To: Maven Users List
> Subject: Re: antrun plugin resolving properties referencing properties
>
> just to clarify, are you using the antrun plugin for maven or the
> maven tasks for ant?
>
>
> On Wed, Jul 14, 2010 at 6:06 PM, Adam Krieg <ak...@pragmatrading.com> wrote:
>> I'm trying to access the project.build.directory property which is defined in my pom as
>>
>> <build>
>> <directory>${project.basedir}/target</directory>
>> ....
>>
>> In ant I have this setup:
>> <artifact:pom id="project-pom" file="pom.xml" />
>> <property name="outputdir" value="${project-pom.build.directory}"/>
>>
>> However when I run my ant build, outputdir is being set to the literal value "${project.basedir}/target" rather than antrun expanding the variable ${project.basedir}. Has anyone else run into this issue?
>>
>>
>>
>> ________________________________
>> Disclaimer: http://pragmatrading.com/disclaimer.html
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> Disclaimer: http://pragmatrading.com/disclaimer.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven ant tasks resolving properties referencing properties
Posted by Adam Krieg <ak...@pragmatrading.com>.
Forgive me, I meant Maven ant tasks. I'm trying to reference information defined in the pom from my build.xml.
-----Original Message-----
From: Shan Syed [mailto:shan.ss@gmail.com]
Sent: Wednesday, July 14, 2010 6:23 PM
To: Maven Users List
Subject: Re: antrun plugin resolving properties referencing properties
just to clarify, are you using the antrun plugin for maven or the
maven tasks for ant?
On Wed, Jul 14, 2010 at 6:06 PM, Adam Krieg <ak...@pragmatrading.com> wrote:
> I'm trying to access the project.build.directory property which is defined in my pom as
>
> <build>
> <directory>${project.basedir}/target</directory>
> ....
>
> In ant I have this setup:
> <artifact:pom id="project-pom" file="pom.xml" />
> <property name="outputdir" value="${project-pom.build.directory}"/>
>
> However when I run my ant build, outputdir is being set to the literal value "${project.basedir}/target" rather than antrun expanding the variable ${project.basedir}. Has anyone else run into this issue?
>
>
>
> ________________________________
> Disclaimer: http://pragmatrading.com/disclaimer.html
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Disclaimer: http://pragmatrading.com/disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: antrun plugin resolving properties referencing properties
Posted by Shan Syed <sh...@gmail.com>.
just to clarify, are you using the antrun plugin for maven or the
maven tasks for ant?
On Wed, Jul 14, 2010 at 6:06 PM, Adam Krieg <ak...@pragmatrading.com> wrote:
> I'm trying to access the project.build.directory property which is defined in my pom as
>
> <build>
> <directory>${project.basedir}/target</directory>
> ....
>
> In ant I have this setup:
> <artifact:pom id="project-pom" file="pom.xml" />
> <property name="outputdir" value="${project-pom.build.directory}"/>
>
> However when I run my ant build, outputdir is being set to the literal value "${project.basedir}/target" rather than antrun expanding the variable ${project.basedir}. Has anyone else run into this issue?
>
>
>
> ________________________________
> Disclaimer: http://pragmatrading.com/disclaimer.html
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org