Sad to read that you completely misunderstood that this is not a "OSGi vs. Maven" topic and all feel offended and agressive about my postings (which solely are done to help to solve the issue). Nobody said you have to give up OSGi version numbers for the sake of Maven, this is a complete wrong assumption of your team. But as your team obviously has absolutely no interest in supporting Maven besides (cluttering Maven Central with simply wrong syntax and pre-release snapshots), it makes no sense to further try to explain your fault and how to solve it easily WITHOUT touching OSGi (the solution would be to keep the version NAME aka FILE NAME in the OSGi style, but to provide the version NUMBER inside of the POM in the Maven style – but you certainly know this and just do not want to allow people to use Maven).
Sad to read that you completely misunderstood that this is not a "OSGi vs. Maven" topic and all feel offended and agressive about my postings (which solely are done to help to solve the issue). Nobody said you have to give up OSGi version numbers for the sake of Maven, this is a complete wrong assumption of your team. But as your team obviously has absolutely no interest in supporting Maven besides (cluttering Maven Central with simply wrong syntax and pre-release snapshots), it makes no sense to further try to explain your fault and how to solve it easily WITHOUT touching OSGi (the solution would be to keep the version NAME aka FILE NAME in the OSGi style, but to provide the version NUMBER inside of the POM in the Maven style – but you certainly know this and just do not want to allow people to use Maven).