continuous-publish-plugin merge requestshttps://git.doit.wisc.edu/adi-ia/continuous-publish-plugin/-/merge_requests2016-09-06T14:01:58-05:00https://git.doit.wisc.edu/adi-ia/continuous-publish-plugin/-/merge_requests/4fix: handle maven release plugin generated tags2016-09-06T14:01:58-05:00Nicholas Blairnicholas.blair@wisc.edufix: handle maven release plugin generated tagsLook like 'my-awesome-project-0.1.0'; need to use a Pattern to slice out the semver triplet.
This pull request fixes a bug found while converting a project that previously used the maven-release-plugin; the tags generated by that plug...Look like 'my-awesome-project-0.1.0'; need to use a Pattern to slice out the semver triplet.
This pull request fixes a bug found while converting a project that previously used the maven-release-plugin; the tags generated by that plugin start with the project name, and can't be parsed by the Java SemVer library as is.
See https://git.doit.wisc.edu/adi-ia/bucky-backup-app/merge_requests/5
cc @paul.erickson Craig KnuthCraig Knuthhttps://git.doit.wisc.edu/adi-ia/continuous-publish-plugin/-/merge_requests/3fix: artifact-version needs to use Manifest#getMainAttributes2016-08-31T13:14:37-05:00Nicholas Blairnicholas.blair@wisc.edufix: artifact-version needs to use Manifest#getMainAttributesgetAttributes returns nullgetAttributes returns nullhttps://git.doit.wisc.edu/adi-ia/continuous-publish-plugin/-/merge_requests/2feat: always populate MANIFEST with project.name and .version2016-08-31T13:31:11-05:00Nicholas Blairnicholas.blair@wisc.edufeat: always populate MANIFEST with project.name and .versionThis 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` ...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
Craig KnuthCraig Knuthhttps://git.doit.wisc.edu/adi-ia/continuous-publish-plugin/-/merge_requests/1docs: correct documentation for buildscript block, add local confirmProjectVe...2016-08-30T15:54:45-05:00Nicholas Blairnicholas.blair@wisc.edudocs: correct documentation for buildscript block, add local confirmProjectVersionIncrementedTaskSmall fix to correct the example provided in the README.
Also includes a way to invoke the confirmProjectVersionIncrementedTask, sharing the logic with the task in the release.Small fix to correct the example provided in the README.
Also includes a way to invoke the confirmProjectVersionIncrementedTask, sharing the logic with the task in the release.Craig KnuthCraig Knuthhttps://git.doit.wisc.edu/adi-ia/continuous-publish-plugin/-/merge_requests/5Add placeholder for project version in README2017-07-26T15:25:25-05:00Benjamin SousaAdd placeholder for project version in READMEAdd placeholder for project version in README, so that copy/paste doesn't leave an old version of the dependency in the parent project's build.Add placeholder for project version in README, so that copy/paste doesn't leave an old version of the dependency in the parent project's build.Matt TrefilekMatt Trefilek