On Sat, 13 Jan 2018 08:48:19 -0500, Rob Tompkins wrote:
Given that right now we don’t have sufficient votes to release the
plugin, do folks want me to cancel this vote in leu of the lazy vote
process cleaning up the nits that folks have found? I’m curious since
folks don’t seem to have the appetite for this process.
?
I don't think that anyone disagreed about "lazy" voting.
So, you can do as you please.
[IIUC, Gary is waiting for a release of the your new release
plugin in order to attempt the release of a component.]
I surely am interested in the *idea* which I have about
what you have been doing. [I did not read a single line of
the plugin code! But I hope that it will solve the problem
which I have exposed (about creating the distribution files
for a modular project).]
Regards,
Gilles
On Jan 11, 2018, at 10:51 PM, Gary Gregory <garydgreg...@gmail.com>
wrote:
Tangent: It just occurred to me that this could have helped in the
process
of developing this plugin:
https://github.com/ok2c/httpcomponents-release-tools/wiki
Gary
On Thu, Jan 11, 2018 at 6:54 PM, Rob Tompkins <chtom...@gmail.com>
wrote:
I had that quickly set up by adding
<dryRun>${dryRun}</dryRun>
to the plugin configuration, but I admit that’s a bit of a hack. I
was
just trying to be speedy in the first version of the plugin for
folks’
benefit.
On Jan 11, 2018, at 7:25 PM, sebb <seb...@gmail.com> wrote:
On 11 January 2018 at 14:42, Rob Tompkins <chtom...@gmail.com>
wrote:
If you do try to run it locally make sure you add
<dryRun>true</dryRun>
It would be useful to be able to define this on the command-line.
To the configuration section of the plugin.
On Jan 11, 2018, at 3:58 AM, Jörg Schaible <
joerg.schai...@bpm-inspire.com> wrote:
Am Wed, 10 Jan 2018 20:35:52 -0700 schrieb Gary Gregory:
I wonder if:
- This should be a LAZY VOTE since this is not an official
component
but
rather a tool
+1
- We should release it as 1.0 anyway (unless obvious bugs
are found) to avoid the chicken and egg problem: To really test
this,
I
want to create an RC for Commons Collection (for example). But
that
means using a commons-release-plugin 1.0 version in my POM -
which we
cannot release as a repeatable build since 1.0 is not out yet.
And
cutting an RC with a 1.0-SNAPSHOT is not acceptable (not
repeatable.)
we might release 1.0-RC1 (or 0.1) as Sergio suggested.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
