Hmm...
Idealy i wanted to use ${pom.artifactId} from project.xml as filter
argument:
<ant:filter filtersfile="[a property file]" />
Only supports property-files -> Problem
Or is there a way to create a property-file from the project.xml
(jelly-script)
Thx
rolf
-----Urspr�ngliche Nachricht-----
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 11. Juli 2004 02:49
An: Maven Users List
Betreff: Re: Using ${pom.*} variables while filtering
for now, you need to set the ant filters manually.
On Fri, 9 Jul 2004 12:02:09 +0200, mr.x <[EMAIL PROTECTED]> wrote:
> Hi
>
> Im want to filter some files while creating my app (Manifest, some
> *.properties) and i would like to use some pom variables in my
> filtered output.
>
> <resource>
> <directory>${basedir}/src/resources</directory>
> <includes>
> <include>*.properties</include>
> <include>**/*.whatever</include>
> </includes>
> <filtering>true</filtering>
> </resource>
> Seems to work only if some ant-like filter files are loaded before
> filtering.
>
> Is there a way to access pom variables for filtering ? Other ideas?
>
> Thanks for help
>
> Rolf
>
> ---------------------------------------------------------------------
> 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]
