<style>
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and (-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
</style>
<div id="email-body">
<table id="email-wrap" align="center" border="0" cellpadding="0" cellspacing="0" style="background-color:#f0f0f0;color:#000000;width:100%;">
<tr valign="top">
<td id="email-page" style="padding:16px !important;">
<table align="center" border="0" cellpadding="0" cellspacing="0" style="background-color:#ffffff;border:1px solid #bbbbbb;color:#000000;width:100%;">
<tr valign="top">
<td bgcolor="#3e4c4e" style="background-color:#3e4c4e;color:#ffffff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;"><img src="https://www.jboss.org/dms/hibernate/images/jira/jiraheader_hibernate.png" alt="" style="vertical-align:top;" /></td>
</tr><tr valign="top">
<td id="email-banner" style="padding:32px 32px 0 32px;">
<table align="left" border="0" cellpadding="0" cellspacing="0" width="100%" style="width:100%;">
<tr valign="top">
<td style="color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;">
<img id="email-avatar" src="https://hibernate.onjira.com/secure/useravatar?avatarId=10162" alt="" height="48" width="48" border="0" align="left" style="padding:0;margin: 0 16px 16px 0;" />
<div id="email-action" style="padding: 0 0 8px 0;font-size:12px;line-height:18px;">
<a class="user-hover" rel="mkarg" id="email_mkarg" href="https://hibernate.onjira.com/secure/ViewProfile.jspa?name=mkarg" style="color:#6c797f;">Markus Karg</a>
commented on <img src="https://hibernate.onjira.com/images/icons/bug.gif" height="16" width="16" border="0" align="absmiddle" alt="Bug"> <a style='color:#6c797f;text-decoration:none;' href='https://hibernate.onjira.com/browse/HV-610'>HV-610</a>
</div>
<div id="email-summary" style="font-size:16px;line-height:20px;padding:2px 0 16px 0;">
<a style='color:#6c797f;text-decoration:none;' href='https://hibernate.onjira.com/browse/HV-610'><strong>Wrong use of maven version schema</strong></a>
</div>
</td>
</tr>
</table>
</td>
</tr>
<tr valign="top">
<td id="email-fields" style="padding:0 32px 32px 32px;">
<table border="0" cellpadding="0" cellspacing="0" style="padding:0;text-align:left;width:100%;" width="100%">
<tr valign="top">
<td id="email-gutter" style="width:64px;white-space:nowrap;"></td>
<td>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr valign="top">
<td colspan="2" style="color:#000000;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;padding:0 0 16px 0;width:100%;">
<div class="comment-block" style="background-color:#edf5ff;border:1px solid #dddddd;color:#000000;padding:12px;"><p>Thank you for explaining your position. In fact, it proofs the misunderstanding and gives room to explain and possibly find a solution. Also, thank you for finally starting to discuss the actual problem.</p>
<ul>
<li>The UPPERCASE was used solely as "speak out loud and clear", just as in a full room where you want to get people look at you. It was not intended offending or aggressive, hence the smiley at the end of that sentence. It was your personal interpretation that this is aggressive. It was simply meant imperative and clear.</li>
</ul>
<p> Nothing else. I was actually perplexed by the tone that came back in the first comments, so I answered in the same tone, which possibly was not the best idea.</p>
<ul>
<li>No, I did actually NOT know that you do NOT use Maven! If you had said loud and clear, I would have known. But you didn't. I assumed you ARE using Maven, since I found several "wrong" (regarding the rules of the Maven Central Repository) artefacts in the Maven Central Repository, which all started this trouble (and I wondered why that happened, as Maven can translate Maven-Version-Syntax into OSGi-Version-Syntax actually). Reading the link you sent me about the JBoss versioning scheme (which refers to Maven) underpinned this assumption. So I thought you know about what happened and what I am talking about being the problem and being the solution.</li>
</ul>
<ul>
<li>Now knowing that it is not your team that pushed "wrong" artefacts meta information into Maven Central Repository (as you do not use Maven I assume you also do not write into Maven's repo), I will agree to close this case and ask Sonatype (= host of Maven Centreal Repository) to not further accept "wrong" JBoss artefacts from anyone but the JBoss team itself. This should prevent trouble like this in future. In fact, I wonder how the artefacts made their way into the repo, as Sonatype usually does NOT accept foreign or unauthorized uploads. Strange.</li>
</ul>
<ul>
<li>The misunderstanding about the scheme change is that the literal "SCHEME" is interpreted in different ways. In my interpretation, a SCHEME is like a database scheme, something that is just describing parts, and which can be expressed in different SYNTAX, just like ER diagrams have different syntax than SQL-DDL has, but both describe the SAME scheme. So for me (and the team around me, but apparently not you and your team) "VERSION SCHEME" means the sole fact that a version consists of four parts with clearly defined use (major, minor, micro / build, qualifier). So, as you correctly say, BOTH, Maven AND OSGi have the same parts. Hence, they share the same scheme (in my interpretation of the word), but this scheme can be written in different SYNTAX! The sole problem is (and here you are right, too) the SYNTAX of the Maven POM (= project description) file. While OSGi SYNTAX (not SCHEME) mandates that all parts are separated by dots, the Maven SYNTAX (not SCHEME) mandates a dash at the last position (for good reason: every version with a dash is meant to be "earlier" than a version without a dash!).</li>
</ul>
<ul>
<li>I do not see a difference between an OSGi standard and Maven's: Both are open alliances where anybody can contribute. But this has nothing to do with this problem and a possible solution, but simply with "political" view. I do not intend to participate to a political discussion, but simply want to get things (here: the Maven Central Repository) working.</li>
</ul>
<ul>
<li>You will be surprised, but I do NOT agree: Yes, Maven is the problem, as it has a differen SYNTAX. Agreed. Really. But this does not solve the problem. Still I am solely talking about the versions found in the Maven Central Repository, not about anything else, and inside that repository, Maven rules apply (makes sense, doesn't it?). Dispite what you assume, no confusion will arise, as all Maven users will understand that what OSGi expresses as "1.2.3.Final" in Maven simply is written as "1.2.3-Final". In fact, confusion arises from "1.2.3-Final" inside of a POM, as this is totally untypical Maven use.</li>
</ul>
<ul>
<li>The short term solution is not to petition to the Maven team (in fact, a good idea; my dream would be to have some marker in the POM that tells maven the pattern of the version SYNTAX, so one could write OSGi version SYNTAX into the POM) since such appeal would take months or years. The solution is to provide the OSGi Version in a different SYNTAX when uploading artefacts to the Maven Central Repository. That's what I wanted to explain. Keeps OSGi, but don't breaks Maven. Just as simple as that.</li>
</ul>
<ul>
<li>The real long term solution is that OSGi, Maven and Oracle finally come up with one and only one modules solution. But it is way out of my power to influence either of them.</li>
</ul>
<ul>
<li>I actually have read the links two times that you sent me. Don't know why you assume I don't like to read it, as I actually mentioned content of these documents in my postings already.</li>
</ul>
<p>So, as obviously the "wrong" artefacts meta information was not provided by JBoss, I will close with this explanation. In the hope that you understood what I meant and that it was never my intention to be agressive or offending against you or your team. I just wanted to propose a rather cheap and simple solution that would allow Maven users to easily use JBoss products without breaking Maven features. Not more. I didn't want to evangelize anybody. I didn't bash anybody for anything. You just understood it that way.</p>
<p>Regards<br/>
Markus</p></div>
<div style="color:#505050;padding:4px 0 0 0;"> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td><!-- End #email-page -->
</tr>
<tr valign="top">
<td style="color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:10px;line-height:14px;padding: 0 16px 16px 16px;text-align:center;">
This message is automatically generated by JIRA.<br />
If you think it was sent incorrectly, please contact your <a style='color:#6c797f;' href='https://hibernate.onjira.com/secure/ContactAdministrators!default.jspa'>JIRA administrators</a>.<br />
For more information on JIRA, see: <a style='color:#6c797f;' href='http://www.atlassian.com/software/jira'>http://www.atlassian.com/software/jira</a>
</td>
</tr>
</table><!-- End #email-wrap -->
</div><!-- End #email-body -->