Maven: If sentense in pom.xml in the property tag

up vote0down votefavorite

I'd like to set a property if an environment variable is set. I googled a lot on it and all I found is something similar to the code below, but I keep getting the error: *[FATAL] Non-parseable POM Y:\Maven\parent-pom\pom.xml: TEXT must be immediately followed by END_TAG and not START_TAG (position: START_TAG s een ...roperties"\r\n classpathref="maven.plugin.classpath" />... @29:55) @ line 29, column 55* That's the code I'm trying, its inside a pom.xml and I ran the command - mvn --errors deploy Of course, I'll be happy to get any other solution, if you have other suggestion on how to set a property in pom.xml depending on an environment variable content. Thanks, Eli .....

resource="net/sf/antcontrib/antcontrib.properties" classpathref="maven.plugin.classpath" /> arg1="${env.WAS60_HOME}" arg2=""\> ${env.WAS60_HOME} ${was60.home}/java/bin/javac arg1="${env.WAS85_HOME}" arg2=""\> ${env.WAS85_HOME} ${was85.home}/java/bin/javac was.base.v60 .... ${was60.home}/java/jre/lib/xml.jar ..... was.base.v85 .... ${was85.home}/java/jre/lib/xml.jar .....

xml maven if-statement pom.xml sentence

share|improve this question

edited Aug 5 at 7:48

asked Aug 5 at 7:21 Elyahu 84

3 Answers

activeoldestvotes

up vote1down vote

usage of tasks inside properties tag is wired , use maven-antrun plugin instead. you can set maven properties with http://maven.apache.org/plugins/maven-antrun-plugin/ maven-antrun-plugin

1.3 ftp package run resource="net/sf/antcontrib/antcontrib.properties" classpathref="maven.plugin.classpath" /> arg1="${ftp}" arg2="true" /> message="The value of property ftp is true" /> message="The value of property ftp is not true" /> true ant-contrib ant-contrib 20020829

share|improve this answer

edited Aug 5 at 10:00

answered Aug 5 at 7:49 mebada 389621

Can you please give me an example ? I couldn't find it in the link you sent –  Elyahu Aug 5 at 8:44

up vote1down vote

A much better approach would be to use profile activations. was.base.v60

env.WAS60_HOME .... ${env.WAS60_HOME}/java/jre/lib/xml.jar ..... was.base.v85 env.WAS85_HOME .... ${env.WAS85_HOME}/java/jre/lib/xml.jar .....

Update:

My preferred way to use profiles is to have a default set of properties in my POM and then override these on demand using profiles in my settings file.

This approach is easy to do explicitly by using the "-s" and "-P" commandline parameters:

mvn -s $PROJECT_SETTINGS -P myProfile ....

This approach is easy to maintain in Jenkins using Config File Provider plugin which enables a GUI for editing the various settings files I use for each project.

Update 2:

Here's an example of how I setup my builds. The POM contains a section with the default property values. And I setup one or more pfiles to over-ride these values:

  
     hello

world .. .. build_in_spanish hola mundo .. build_in_irish dia dhuit an domhain ..

So in this example the build defaults to English. To run the build with the settings in Spanish

mvn -P build_in_spanish ...

Note:

• Profiles can be in the POM or in a separated settings file. The latter approach gives the most flexibility.
• Profiles can be explicitly enabled (using the "-P" command line option or by attempting to discover the environment it sits within. This is a design choice)

share|improve this answer

edited Aug 6 at 13:54

answered Aug 5 at 8:18 Mark O'Connor 24.2k22146