Yes, although take a look at the 'Better Builds with Maven' book (available from Mergere).
It has a section on exactly this situation, where the version is controlled not from the settings.xml, but from the parent POM of your multi-module build, and propogated through all your dependencies. Providing all your directory, module and artifact names match exactly (including case-sensitivity - working on Windows I ran into problems with this initially!), and Maven will just work happily, including the release plugin correctly maintaining versioning dependencies in POM relationships and snapshot dependency issues. G -----Original Message----- From: hamdard [mailto:[EMAIL PROTECTED] Sent: 17 August 2006 11:12 To: users@maven.apache.org Subject: [M2] How to softcode 'version' in dependency declaration Hi Is it possible to softcode the version in the dependency declaration? For example, the pom could be like this: <dependency> <groupId>com.mycompany.ixaf</groupId> <artifactId>gw-plugin</artifactId> <version>${myversion}</version> </dependency> And the myversion parameter is controllable from the settings.xml file. The motivation is that if we have a multi-module build in maven with all the different modules using the same 'one' version, we could control/update the version of the entire project from one place (settings.xml), instead of updating it in several places. Thanks -- View this message in context: http://www.nabble.com/-M2--How-to-softcode-%27version%27-in-dependency-declaration-tf2120609.html#a5848660 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- 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]
