Ian, This looks like a usecase for release:prepare, this will create a new SCM tag and manage your version numbers in the pom.xml files. thanks, -Guillaume
________________________________ From: Ian Rowlands [mailto:[EMAIL PROTECTED] Sent: Tue 24/06/2008 7:34 PM To: [email protected] Subject: Incrementing a pom version in a multi-module project (without doing by hand) Just wondering what the best way to change the version of POMs in a multi-module Maven 2 project from one number to another? I know you can use the release:branch plugin to do it if you require a branch, but sometimes I don't want to branch - I just want to increase the version! I need to be able to choose the version as well. Which plugin can do this, and how do I use it? Thanks, Ian Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected (administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. ____________________________________________________________________________________________________ This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply email so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.
