Oliver, for me the site builds just fine (Maven 3.5.0, OpenJDK 1.8.0_151,
Debian amd64). Iĺl try to reproduce the issue when I could get my hands on
a Windows.
In the meantime, I'd like to ask the Commons PMC to vote on this RC. So far
we have only non-binding votes :-/
On Sat, Dec 9, 2017 at 12:
cancelling then (and updating the subject)
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-12-12 17:13 GMT+01:00 Thomas Vandahl :
> On 12.12.17 09:14, Romain Manni-Bucau wrote:
>> This is the part I really don't understand since it will never work.
>
> Yes, I know. An
+1 (non-binding) for release
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T15:39:06-04:00)
Java version: 1.8.0_65, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
Nice he
On 12.12.17 09:14, Romain Manni-Bucau wrote:
> This is the part I really don't understand since it will never work.
Yes, I know. And I agree. But it's the process in commons as of now.
Let's get this out of the door and save the discussion for later.
Please?
Bye, Thomas
+1 Release this package (non-binding)
Builds on OS X with Java 8
$ mvn -version
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T03:58:13-04:00)
Maven home: /usr/local/Cellar/maven/3.5.2/libexec
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /Library/Jav
I don’t understand the use case. It feels like a contrivance without that clear
understanding. That said, given sufficient documentation it could go in either
based upon who you think would be using it most.
-Rob
> On Dec 11, 2017, at 5:28 PM, Gary Gregory wrote:
>
> Too weird for lang or te
The vote passes with the following votes (in order of appearance):
Gary Gregory: +1
Bruno Kinoshita: +1
Amey Jadiye (non-binding): +1
Rob Tompkins: +1
I will proceed with publishing the release candidate. Many thanks to all of
those that helped in preparing and validating this release.
Cheers,
Here’s my +1
> On Dec 8, 2017, at 11:16 PM, Rob Tompkins wrote:
>
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.2 (from RC1).
>
> Tag name:
> commons-text-1.2-RC1 (signature can be checked from git using 'git tag -v')
>
> Tag URL:
>
> https://git-wip-us.apache.org
This is the part I really don't understand since it will never work.
Either we respect the tag and therefore need yet another release to
have a final which makes the RC pointless or we do not respect the tag
which is worse IMHO. From my point of view it is way less hurting to
not do the RC than doi
On 11.12.17 22:43, Romain Manni-Bucau wrote:
> I can drop the rc2, no problem but can you confirm rc3 will be this exact
> vote with revisions as only change?
yes, and the RC-tag is probably required.
Bye, Thomas.
-
To unsubscri
10 matches
Mail list logo
