I am preparing, at least mentally, to do to [1] to the maven-bundle-plugin -- to make it require Maven 3.x.
So, you might think that I need to change the major version number. This, of course, would have the effect of de-syncing the versions from bnd versions. Maybe this doesn't bother anyone. On the other hand, there's this issue: in theory, names of the form maven-X-bundle are supposed to be reserved for the actual Apache Maven Project. I can't really imagine my Maven PMC fellow-members deciding to hassle another Apache project, but it _could_ be that a better name would be the felix-bundle-plugin. 'maven' in the artifact-id of a maven plugin hardly carries a ton of information. And we could set the version back to 1.0.0. Personally, I'd be happy to just bump the version to 4.0.0 and give up on mirroring bnd version numbers, but I felt compelled for some reason to offer the community the other idea. [1] https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
