>If I need a specific version (usual to workaround a known issue) then >I specify it in the the pom. Otherwise I want the latest. This is the current problem, where builds are done with undetermined versions. (ie the version for dev a might not match dev b)
>For snapshot builds if I will use specified, then latest. >For a released build, I want the pom to be transformed and fully >locked down so that the build is reproducible. And I don't want to do >that manually. I would expect that my snapshot builds to be exactly the same as the eventual release build for that version. The last thing I need is release to decide for me which versions to use. I do want to do it manually, because I want to try out each new plugin before I bless it and allow it into the build process for the rest of the team. I've had too many occurrences where a plugin change breaks my build (I'm ok with that, it's necessary for forward progress). By manually vetting a plugin, it gives me a chance to make any adjustments needed. It's no different than how we upgrade Maven itself: I have used enforcer to lock my build to 2.0.5 until I can get all the depMgt straightened out and then I will move everyone forward. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
