PLEASE STOP THIS MISUSE OF THE VERSION ATTRIBUTE AND START USING VERSION NUMBERS IN THE WAY MAVEN WAS INTENDED TO WORK
Sure sounds pretty aggressive. Especially love the all caps. Also, surely you are aware that we in fact do not use Maven to build Hibernate. Hard to "misuse" something you are not using.
And, yes, you are in fact asking/telling us to change the version scheme.
You are using "5.0.0.Alpha1" instead of "5.0.0-Alpha-1".
How is changing the version from "5.0.0.Alpha1" to "5.0.0-Alpha-1" not changing the version scheme? In fact it is exactly what you are asking us to do. And as for "changing it just in Maven", sorry but thats a stupid idea. Can't possibly see any confusion growing out of that (rolls eyes).
The trick to make this work is simple: The version of an artifact must be X.Y.Z-F
And this is exactly the problem. According to OSGi (you know, a standard as opposed to some random Apache group) that should be X.Y.Z.F. F, just like with Maven, if specified is what is called (by Maven as well) a "qualifier" (alpha, beta, etc). The problem as I see it is Maven. You can disagree. You can sit here and continue to argue in your not-arguing way. Or, you know what might actually be useful? Maybe you could petition the Maven team to stop half-ass supporting OSGi versioning.
And I am really done now. You obviously don't want to read the links we sent nor understand why JBoss and we decided on this scheme. You'd rather just bash Hibernate and/or JBoss for a Maven problem.
Sure sounds pretty aggressive. Especially love the all caps. Also, surely you are aware that we in fact do not use Maven to build Hibernate. Hard to "misuse" something you are not using.
And, yes, you are in fact asking/telling us to change the version scheme.
How is changing the version from "5.0.0.Alpha1" to "5.0.0-Alpha-1" not changing the version scheme? In fact it is exactly what you are asking us to do. And as for "changing it just in Maven", sorry but thats a stupid idea. Can't possibly see any confusion growing out of that (rolls eyes).
And this is exactly the problem. According to OSGi (you know, a standard as opposed to some random Apache group) that should be X.Y.Z.F. F, just like with Maven, if specified is what is called (by Maven as well) a "qualifier" (alpha, beta, etc). The problem as I see it is Maven. You can disagree. You can sit here and continue to argue in your not-arguing way. Or, you know what might actually be useful? Maybe you could petition the Maven team to stop half-ass supporting OSGi versioning.
And I am really done now. You obviously don't want to read the links we sent nor understand why JBoss and we decided on this scheme. You'd rather just bash Hibernate and/or JBoss for a Maven problem.