On Fri, Apr 2, 2010 at 6:39 PM, Scott Susslin <[email protected]> wrote: > We're working in Agile, and QA needs to know what version number their > working against. Since they're QAing about every day, I'd like to have them > know exactly which version they're hitting without forcing the developers to > change the version number manually every day. We'd only be using this number > below the major.minor in our version, and only for SNAPSHOTs, so I don't see > the harm in using it for that. A release build will be an agreed-up, solid > number.
Is there some reason it has to be in the version number? (And if it does, snapshots are *already* timestamped, with a build number...) You're already using the buildnumber plugin, so you can bake that number into the product elsewhere, such as an 'about' page, or in the jar file manifests, or... Personally I like to bake the svn revision number into the product, so I know *exactly* what code I'm working with. (And as you've already discovered, no, using a property in the version number won't work.) Best advise with Maven is to use what it gives you, and not try to bend it to your will. It tends to bite. ;) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
