Your resolution looks like you misunderstood one thing about Maven version ranges: This is not about what YOU do, it is about what USERS do. Maven version ranges is a tool inherent to Maven, and used by Maven users, with OR WITHOUT you like this nor not. What you currently do is: You simply make it impossible for users to use this feature. Please also note that nobody wants to void the JBoss versioning scheme. This issue is not about the scheme. It is about the SYNTAX. See, Maven simply has a different SYNTAX. All I ask you to do is to use Maven as it is intended. Not to change your SCHEME. You can keep the scheme. But please get rid of the SYNTAX ERRORS you are doing. When your schema says, you want to have "5.0.0.Alpha1", the SOLE CORRECT USE of Maven is to have "5.0.0-Alpha1" in the POM. This is not change to your scheme. It is simply the correction of the WRONG POM you are providing. That's all. And please do not feel offended. I invested time to exlain that you made a mistake, nobody pays me for that. So wouldn't it be polite to accept how Maven works instead of asking fancy stuff like Maven and OSGi? Maven has its own packaging. You cannot change this. If you support Maven (and I appreciate that) you just have to follow Maven rules. BTW, I do not see any problem with this, as a Maven artifact and an OSGi artifact simply do not have much in common and can be supported in parallel if you want that.