Versioning for a maven project with small, very frequent releases
I'm converting an ant project to a maven one. This project differs from the ones I've usually converted since it has very frequent releases, typically 8-10 times per day.

By release I mean that the resulting jar is packaged and included in the production enviroment. This project is a _leaf_ one, so it publishes no API, it only consumes it. It is also at most a _runtime_ dependency for two other projects.

I'd like to have a versioning scheme where:

- it's easy to deploy without forcing the developers to think about what version number to assign to the project, since the number is meaningless;
- It's easy to include the latest version of this project as a dependency without constantly bumping up dependency versions;

Most likely the dependency version would not be a `-SNAPSHOT`, since that would conflict with the `maven-release-plugin` we're using for other projects, but I'm open to suggestions.
Versioning for a maven project with small, very frequent releases
===

I'm converting an ant project to a maven one. This project differs from the ones I've usually converted since it has very frequent releases, typically 8-10 times per day.

By release I mean that the resulting jar is packaged and included in the production enviroment. This project is a _leaf_ one, so it publishes no API, it only consumes it. It is also at most a _runtime_ dependency for two other projects.

I'd like to have a versioning scheme where:

- it's easy to deploy without forcing the developers to think about what version number to assign to the project, since the number is meaningless;
- It's easy to include the latest version of this project as a dependency without constantly bumping up dependency versions;

Most likely the dependency version would not be a `-SNAPSHOT`, since that would conflict with the `maven-release-plugin` we're using for other projects, but I'm open to suggestions.