commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COMMONSSITE-112) [release-plugin] should create a VOTE.txt file
Date Mon, 14 May 2018 23:02:00 GMT

     [ https://issues.apache.org/jira/browse/COMMONSSITE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Gregory updated COMMONSSITE-112:
-------------------------------------
    Description: 
It would be great if the plugin would create a VOTE.txt file based on the template [http://commons.apache.org/releases/prepare.html]

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 -Duser.name=${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.

  was:
It would be great if the plugin would create a VOTE.txt file based on the template [http://commons.apache.org/releases/prepare.html]

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.

Normally, releasing an RC is done with our new Commons Release plugin:
{noformat}
mvn -Duser.name=${my_apache_id} -Prelease [-Ptest-deploy] clean package site deploy
{noformat}

I'd like a VOTE.txt file to be left behind, perhaps in the root folder of the project or in
the {{target}} folder.

I'm not sure if something attached to the {{deploy}} goal should do that or if we should have
an additional goal.


> [release-plugin] should create a VOTE.txt file 
> -----------------------------------------------
>
>                 Key: COMMONSSITE-112
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-112
>             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 [http://commons.apache.org/releases/prepare.html]
> 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 -Duser.name=${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
(v7.6.3#76005)

Mime
View raw message