Seems like a big misunderstanding. It was neither my intention to be offending or to make you understand any fancy assumption like thinking I would be a Maven Expert or your would be wits. In fact, I am far from being a Maven Expert, but I am a professional user and see that your team's use of the version POM field is a problem, and I wanted to provide a solution (which JBoss just doesn't want to get). This is your interpretation that I do not share. My tone was the sole reaction upon the comments in this tracker, in the same tone as I understood those. Please read my original posting and you will not find anything agressive or offending (if you do, please quote, and I will explain how it was meant).

Again, your last sentence tells me that JBoss still has not understood that I do not want to change the version schema, but solely SYNTAX of the POM. All your documents, projects, sites, whatever, will stay with the OSGi SYNTAX, but solely Maven Central and Maven POMs will change. This is a valid interpretation of the JBoss document you referred to, as that document does not enforce that at all places and in any way the SYNTAX has to be enforced, but it solely talks about a SCHEMA which is KEPT even if the SYNTAX in the POM is modified.