Note that the bundle is now created without a version, as verified by test-bundle-war-final-name. Internally within the bundle zip, the resulting war file will still have a version.
Note that if you're using the deploy goal with the bundle deploy API, the resulting bundle directory will still have the version number in, as it's derived from the version in the manifest within the bundle file, not the bundle file name.
This is still useful for scenarios where you're deploying the resulting bundle file yourself though
OK - @ind1go showed me that final name is a pre-existing maven feature which we're just overriding in this case, so the behaviour is remaining equivalent!
Fixes #224
Note that the bundle is now created without a version, as verified by
test-bundle-war-final-name
. Internally within the bundle zip, the resulting war file will still have a version.Note that if you're using the
deploy
goal with the bundle deploy API, the resulting bundle directory will still have the version number in, as it's derived from the version in the manifest within the bundle file, not the bundle file name.This is still useful for scenarios where you're deploying the resulting bundle file yourself though