you can use setup maven exec task on sedThis will globally replace all fu with 
bar in input.file and output result to output.filee.g.           
<groupId>org.codehaus.mojo</groupId>                  
<artifactId>exec-maven-plugin</artifactId>                  
<version>1.1</version>                  <executions>                      
<execution>                          <id>exec-one</id>                          
<phase>verify</phase>                          <configuration>                  
            <executable>sed</executable>                              
<arguments>                                  <argument>s/fu/bar/g</argument> 
                                 <argument>input.file</argument> 
                                 <argument>> output.file</argument>             
                 </arguments>                          </configuration>         
                 <goals>                              <goal>exec</goal>         
                 </goals>                      </execution> 
HTHMartin Gainty ______________________________________________ Disclaimer and 
confidentiality note Everything in this e-mail and any attachments relates to 
the official business of Sender. This transmission is of a confidential nature 
and Sender does not endorse distribution to any party other than intended 
recipient. Sender does not necessarily endorse content contained within this 
transmission. > Date: Sat, 5 Jul 2008 16:21:28 +0200> From: [EMAIL PROTECTED]> 
To: [email protected]> Subject: Re: Filtering of a SINGLE property> > 
Noone?> > Please, there must be someone able to answer this?!> > > Thanks,> > 
Peter> > 2008/7/3 Peter Horlock <[EMAIL PROTECTED]>:> > > Hi,> >> > I want to 
let Maven / the Resource plugin (> > 
http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html>
 > )> >> > parse my source code to replace {project.version} with the current 
version> > of the project as defined in the pom.> > This works great, but - in 
JSTL, as well as in OpenLazlo, ${variableName}> > is also a variable of the 
language itself -> > therefore, this leads to collisions - for example, one of 
our developers> > used a variable named ${parent} which then was filtered by 
Maven and booom> > the code was broken. Yada yada YAda!> >> > => Is there a way 
of telling Maven to JUST filter certain properties? I> > know I could tell it 
to just filter certain files,> > but> > a) a developer could then STILL use 
${parent} as a variable in this very> > file> > b) whenever I wanted a new file 
to be filtered, I would have to add this> > file to the filter section...> >> > 
Thanks a lot folks,> >> > Peter> >
_________________________________________________________________
The i’m Talkaton. Can 30-days of conversation change the world?
http://www.imtalkathon.com/?source=EML_WLH_Talkathon_ChangeWorld

Reply via email to