Ticket #1725 (closed task: fixed)
Opened 2013-03-22T11:37:07-05:00
Last modified 2014-05-01T15:09:57-05:00
Use maven-release-plugin for ImageJ releases
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | major | Milestone: | imagej-2.0.0 |
| Component: | Build System | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1718 |
Description
It would be ideal to use the maven-release-plugin for our ImageJ releases, so that they are done according to best practice rather than using our custom tag-release.sh script etc. (At the very least, our script could use mvn release:prepare and mvn release:perform as part of its operation.)
This would also play well with our planned move of ImageJ and friends to Central (#1670).
See this article for a guide.
Change History
comment:1 Changed 2013-03-22T11:37:15-05:00 by curtis
- Summary changed from Test maven-release-plugin for ImageJ releases to Use maven-release-plugin for ImageJ releases
comment:2 Changed 2014-05-01T15:09:57-05:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
We do now use the maven-release-plugin via the release-version.sh script. We also have Jenkins jobs. In general, we are on track for release management, though the process still needs some refinement.