-
- Downloads
Merge branch 'release-version' into 'master'
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 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 cc: @paul.erickson @apatwary See merge request !2
No related branches found
No related tags found
Showing
- README.md 6 additions, 1 deletionREADME.md
- artifact-version.groovy 17 additions, 0 deletionsartifact-version.groovy
- build.gradle 9 additions, 2 deletionsbuild.gradle
- git-publisher-config.png 0 additions, 0 deletionsgit-publisher-config.png
- src/main/groovy/edu/wisc/doit/gradle/ContinuousPublishPlugin.groovy 24 additions, 0 deletions...roovy/edu/wisc/doit/gradle/ContinuousPublishPlugin.groovy
- src/test/groovy/edu/wisc/doit/gradle/ContinuousPublishPluginTest.groovy 9 additions, 0 deletions...y/edu/wisc/doit/gradle/ContinuousPublishPluginTest.groovy
artifact-version.groovy
0 → 100644
git-publisher-config.png
0 → 100644
86.2 KiB