Hello,

Can anyone tell me how to make sure that the property values changed
by the antrun plugin stick around for use by Maven?

I have defined the following properties in Maven:

    <properties>
        <!-- valid values: developer or production -->
        <BUILD_TYPE>developer</BUILD_TYPE>
        <DEVELOPER_BUILD>false</DEVELOPER_BUILD>
        <PRODUCTION_BUILD>false</PRODUCTION_BUILD>
    </properties>

And I'm trying to operate on them and change their default values via
the maven-antrun-plugin:
   <condition property="DEVELOPER_BUILD" value="true" else="false">
       <equals arg1="${BUILD_TYPE}" arg2="developer"/>
   </condition>
   <condition property="PRODUCTION_BUILD" value="true" else="false">
       <equals arg1="${BUILD_TYPE}" arg2="production"/>
   </condition>

When I echo the property values before and after the conditions in the
antrun plugin, I can see the maven values coming in and the
appropriate conditions changing those values from false to true.

But when I try to use the property values (that should have been
altered by the antrun plugin) in Maven again, they are not available.
Only the original values from Maven are available!
   <definesDeclaration>
       <property>
           <name>BUILD_TYPE::developer</name>
           <value>${DEVELOPER_BUILD}</value>
       </property>
       <property>
           <name>BUILD_TYPE::production</name>
           <value>${PRODUCTION_BUILD}</value>
       </property>
   </definesDeclaration>

Can anyone tell me how to make sure that the property values changed
by the antrun plugin stick around for use by Maven?

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to