Hi, I understand that in a code review context all the diff caused by the updated <version> parameters can be quite problematic, and I don't know how you could fix it via Maven.
The thing I don't understand though is that if someone is going to review code he is probably not going to compare released code against released code. I would find it more logical to compare released code against modified code under submission (so that the one reviewing the code could actually stop the submission and require whatever changes judged necessary). If so couldn't the review prosess happen just before the release plugin is used (when there is no diff for the <version> tags)? Tell me if I'm unclear I could really be missing something here :) Med vennlig hilsen, --- Florent Legendre -----Opprinnelig melding----- Fra: Graham Leggett [mailto:[EMAIL PROTECTED] Sendt: 11. desember 2007 17:16 Til: Maven Users List Emne: Re: Defining version in single location? Adrian Jackson wrote: > Which brings us back to square one: that doesn't work with our > workflow, as it would result in hundreds of changes to pom.xml files > for every piece of work. Which the release plugin does for you. What procedure do you use to release code, is is standardised or has it been custom built? Regards, Graham -- Statnett SF, Tel. head office +47 22527000, Enterprise No. NO 962 986 633 VAT, www.statnett.no, [EMAIL PROTECTED] _________________________________________________________________ This e-mail and any attached files are confidential and may be legally privileged. If you have received this transmission in error please notify the sender by reply e-mail immediately and then delete the e-mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. If verification is required please request a hard copy version. This e-mail message has been virus checked by the virus programs used by Statnett SF. _________________________________________________________________ Save a tree - don't print this e-mail unless necessary! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
