This would work great. I will try latest snapshot to confirm.
As for STS - is there a way for STS to pick up a version from some external source vs. template.mf explicit value? Otherwise manifest generated by STS will differ from one generated by the build be that ant or maven.
Originally Posted by Ben Hale
It sounds good for me too. I'll try it.
I just upgraded our parent-pom from bundlor 1.0.0.M6 to 1.0.0.RELEASE using the following config.
We're using a pom-first approach where properties are defined in the pom.xml and reused in template.mf. This template.mf is then used by maven to generate a MANIFEST.MF which shall be used inside STS (for deployment into dm server) and be put into the jar (for which we now use the maven-jar-plugin)
<!-- generate the manifest automatically during packaging -->
if a BSN or BV is specified in the Maven configuration it overrides anything specified in the template.
I agree with the above statement. Good point!!
Different people have different points of view. That’s why we have different opinions.
You may use Bing or Google to have a try.
To see more, check here: