commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <>
Subject [jira] [Commented] (COMMONSSITE-112) [release-plugin] should create a VOTE.txt file
Date Wed, 16 May 2018 16:41:00 GMT


Gary Gregory commented on COMMONSSITE-112:

It would be great to stash the SHA1's someplace indeed. I only picked Ant because the build
plugin uses Ant and it seems to do the job easily. I'd say try Ant and it is becomes too messy,
then move it to Java...

> [release-plugin] should create a VOTE.txt file 
> -----------------------------------------------
>                 Key: COMMONSSITE-112
>                 URL:
>             Project: Commons All
>          Issue Type: New Feature
>          Components: Commons Release Plugin
>            Reporter: Gary Gregory
>            Priority: Major
> It would be great if the plugin would create a VOTE.txt file based on the template []
> First, we should resolve whether or not we want the site to be copied as a zip file or
as an uncompressed folder on dev.
> The steps would be, first create the release candidate. Normally, releasing an RC is
done with our new Commons Release plugin:
> {noformat}
> mvn${my_apache_id} -Prelease [-Ptest-deploy] clean package site deploy
> {noformat}
> Then create the release notes, right now, with what I have, you can test like this
> {noformat}
> mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:vote-txt
> {noformat}
> Using a goal prefix should work after the release:
> {noformat}
> mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT commons-release:vote-txt
> {noformat}
> This creates a VOTE.txt file in the root folder of the project.
> I am currently testing this with Commons Collections.

This message was sent by Atlassian JIRA

View raw message