Ok, osgi has a separate Bundle-Version header for the bundle version information which
would be needed. The java spec/implementation manifest headers would default to the maven
version format still. Looking at the:
there is no way to transform the version other than specifying a new set of header values.
It really comes down to needing a version policy so that there is only one pom.version
specification that gets mapped to all of the version uses.
View the original post :
Reply to the post :