On Wed, Dec 31, 2008 at 9:40 AM, Wayne Fay <wayne...@gmail.com> wrote: >> - change <version> from "1.4" to "snapshot" >> - every build I make, will be stored in the Archiva SNAPSHOTS repository >> - the snapshot is stored with a date suffix, to see differences >> between the builds > > The choice of 1.4.1 vs 1.5 vs 2.0 depends on how much your codebase is > expected to change. A simple bugfix will generally just trigger a > 1.4.1 while a bigger change will bump to 1.5 and a very large change > will trigger 2.0.
It's important to note that whether you bump major, minor, or micro, this is a point of policy that you would set for your own codebase and then educate your users about expectations based on version number. Maven doesn't really specify a convention for it that I know of. Probably the closest to a convention is that the defaults for the release plugin will increment the final number of your version. For example, if you release 1.4, it will suggest you renumber to 1.5. If you release 1.4.0, it will suggest you renumber to 1.4.1. Archiva or Nexus should handle mapping your deployment of 1.4.1-SNAPSHOT to 1.4.1-timestamp-buildnumber at deployment time, as well as symlinking 1.4.1-SNAPSHOT to the newest. - John --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
