In preparation of releasing Jaybird 2.2, I am investigating releasing it
to Maven. Now I am having trouble deciding on a naming / versioning
scheme, so I'd like your input on this one.

The question is posted on stackoverflow:
http://stackoverflow.com/questions/9555722/deploying-maven-artifacts-for-different-jvm-versions

Full text:
For the release of Jaybird (Firebird JDBC driver) we also want to
release to the Maven repository. I am now considering how to
name/version the artifacts, as there is a different version for each
supported Java version (for the upcoming Jaybird 2.2 it would be a
version for Java 5/JDBC 3, Java 6/JDBC 4.0 and Java 7/JDBC 4.1).

I have found three different ways of naming JVM specific versions:

1. JVM version in the artifact (eg
<artifactId>jaybird-jdk15</<artifactId>)
2. JVM version in the version (eg <version>2.2.0-jdk15</version>)
3. Using the classifier (eg <classifier>jdk15</classifier>)

As the builds have different sourcecode one could consider the JVM
variants to be actually different artifacts (option 1). I have seen that
PostgreSQL JDBC uses option 2. Option 3 has (AFAIK) the downside that
you can't include version specific sources and javadoc.

I would like to know if I have missed a totally different option or
maven-feature for JVM specific artifacts, or if there is a preferred
method for versioning these types of artifacts.

NOTE: The Jaybird build process itself does not use Maven

PS I expect to release a beta version of Jaybird 2.2 this month
--
Mark Rotteveel