feat: always populate MANIFEST with project.name and .version
This pull request directs the plugin to configure the jar
task (if present, provided by the java
plugin) and/or the war
task (if present, provided by the war
plugin) to set the Implementation-Version
and Implementation-Title
attributes in the MANIFEST.MF file included in the result.
The end result is that issue #1 (closed) can be satisfied by pulling out Implementation-Version
from the MANIFEST. By using MANIFEST, we use a file in Java specifications and we don't have to pollute the build of downstream projects with our own custom properties file.
Manifest reference:
https://docs.oracle.com/javase/tutorial/deployment/jar/packageman.html
Merge request reports
Activity
Build finished. Tests PASSED. Build results available at: https://ia-builds.doit.wisc.edu:8443/job/continuous-publish-plugin-master-pull-requests/3/
Added 1 commit:
- 965b82ff - test: confirm we can still add the plugin to projects w/o java/war
Build finished. Tests PASSED. Build results available at: https://ia-builds.doit.wisc.edu:8443/job/continuous-publish-plugin-master-pull-requests/4/
Added 1 commit:
- 718f28a5 - feat: add artifact-version.groovy expected by Jenkins build
Build finished. Tests PASSED. Build results available at: https://ia-builds.doit.wisc.edu:8443/job/continuous-publish-plugin-master-pull-requests/5/
Added 1 commit:
- 161c85a3 - docs: describe how to get Jenkins to tag releases
Build finished. Tests PASSED. Build results available at: https://ia-builds.doit.wisc.edu:8443/job/continuous-publish-plugin-master-pull-requests/6/
mentioned in commit 300638dc