[ https://jira.codehaus.org/browse/MNG-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299880#comment-299880 ]
Darshak Thakore edited comment on MNG-4998 at 5/28/12 11:03 AM: ---------------------------------------------------------------- I recently ended up on this issue thru the thread mentioned in the description while i was searching for the solution to the same problem. I was mavenizing one of our mixed project (c, c++ and java) and was using the properties-maven-plugin along with the cbuilds plugins to mavenize my gnu autotools project. As part of that, i had defined various defaults in the pom file for autoconf and make but i needed a mechanism for the user to override those defaults and the most logical and concise way i could find was by using the properties-maven-plugin to read various parameters from a properties file. However when i run the project under maven3, i'm suffering this static vs dynamic interpolation. I thought i'll comment here with my use case to push for either maven2 like behavior or Luke's suggestion above. I think without either of those, we seem to be crippling the usability of maven 3. was (Author: darshakthakore): I recently ended up on this issue thru [this thread|http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html] while i was searching for the solution to the same problem. I was mavenizing one of our mixed project (c, c++ and java) and was using the properties-maven-plugin along with the cbuilds plugins to mavenize my gnu autotools project. As part of that, i had defined various defaults in the pom file for autoconf and make but i needed a mechanism for the user to override those defaults and the most logical and concise way i could find was by using the properties-maven-plugin to read various parameters from a properties file. However when i run the project under maven3, i'm suffering this static vs dynamic interpolation. I thought i'll comment here with my use case to push for either maven2 like behavior or Luke's suggestion above. I think without either of those, we seem to be crippling the usability of maven 3. > Variables interpolation: dynamic in Maven 2, static in Maven 3 > -------------------------------------------------------------- > > Key: MNG-4998 > URL: https://jira.codehaus.org/browse/MNG-4998 > Project: Maven 2 & 3 > Issue Type: Bug > Components: POM > Affects Versions: 3.0.2 > Reporter: Evgeny Goldin > > Please, see > http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html. > It demonstrates two examples where expression with ${variables} are > interpolated differently in Maven 2 and Maven 3: Maven 2 allows to update > <properties> and effect expressions interpolated later, Maven 3 also allows > to update <properties> but all expressions are interpolated with their old > values. > I believe Maven 2 dynamic behavior is much more preferable than Maven 3 > Ant-like "stickiness" to what's defined in <properties>. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira