Re: [CSV] Inconsistent record separator behavior

Am Do., 23. Aug. 2018 um 20:17 Uhr schrieb sebb : > On 23 August 2018 at 17:31, Benedikt Ritter wrote: > > Hi, > > > > Am Do., 23. Aug. 2018 um 12:11 Uhr schrieb sebb : > > > >> On 23 August 2018 at 07:10, Benedikt Ritter wrote: > >> > Hey sebb, > >> > > >> > Am Do., 23. Aug. 2018 um 01:23 Uhr s

Re: [COLLECTIONS] Master branch build failing

Am Do., 23. Aug. 2018 um 20:12 Uhr schrieb sebb : > Huh? > > Looks like the failure is due to Clirr is reporting some breaks; not > sure how that can depend on the Java version. > Maybe related to Java 8 default methods? I'm just guessing here... Need to dig into this on the weekend. Benedikt

JDK 11: First Release Candidate available

Hi Benedikt, *JDK 11 build 28 is our first JDK 11 Release Candidate [1] * * JDK 11 Early Access  build 28 is available at : - jdk.java.net/11/ *FOSS fixes in recent builds.* * Eclipse Jetty - JDK-8207177 (b27) * Apache Tomcat   -JDK-8208

Re: New release distribution checksum policy

Hi Benedikt, On 23.08.18 18:25, Benedikt Ritter wrote: > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl : > >> Shall we use this for commons-parent? >> > > Sounds reasonable to me. If I'm not mistaken, the requirement for SHA-512 checksums only exists for the source distribution, not

Re: New release distribution checksum policy

Hi Thomas, Am Fr., 24. Aug. 2018 um 13:13 Uhr schrieb Thomas Vandahl : > Hi Benedikt, > > On 23.08.18 18:25, Benedikt Ritter wrote: > > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl >: > > > >> Shall we use this for commons-parent? > >> > > > > Sounds reasonable to me. > > If I'm not

Re: New release distribution checksum policy

On Fri, 24 Aug 2018 15:13:22 +0200, Benedikt Ritter wrote: Hi Thomas, Am Fr., 24. Aug. 2018 um 13:13 Uhr schrieb Thomas Vandahl : Hi Benedikt, On 23.08.18 18:25, Benedikt Ritter wrote: > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl >: > >> Shall we use this for commons-parent

Re: [COLLECTIONS] Master branch build failing

Hi, Am Fr., 24. Aug. 2018 um 09:06 Uhr schrieb Benedikt Ritter < brit...@apache.org>: > > > Am Do., 23. Aug. 2018 um 20:12 Uhr schrieb sebb : > >> Huh? >> >> Looks like the failure is due to Clirr is reporting some breaks; not >> sure how that can depend on the Java version. >> > > Maybe related

Re: New release distribution checksum policy

On 24 August 2018 at 14:13, Benedikt Ritter wrote: > Hi Thomas, > > Am Fr., 24. Aug. 2018 um 13:13 Uhr schrieb Thomas Vandahl : > >> Hi Benedikt, >> >> On 23.08.18 18:25, Benedikt Ritter wrote: >> > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl > >: >> > >> >> Shall we use this for com

Re: [COLLECTIONS] Master branch build failing

On Fri, Aug 24, 2018 at 7:41 AM Benedikt Ritter wrote: > Hi, > > Am Fr., 24. Aug. 2018 um 09:06 Uhr schrieb Benedikt Ritter < > brit...@apache.org>: > > > > > > > Am Do., 23. Aug. 2018 um 20:12 Uhr schrieb sebb : > > > >> Huh? > >> > >> Looks like the failure is due to Clirr is reporting some bre

Re: [COLLECTIONS] Master branch build failing

On Fri, 24 Aug 2018 15:41:36 +0200, Benedikt Ritter wrote: Hi, Am Fr., 24. Aug. 2018 um 09:06 Uhr schrieb Benedikt Ritter < brit...@apache.org>: Am Do., 23. Aug. 2018 um 20:12 Uhr schrieb sebb : Huh? Looks like the failure is due to Clirr is reporting some breaks; not sure how that can

Re: [COLLECTIONS] Master branch build failing

On 24 August 2018 at 14:46, Gary Gregory wrote: > On Fri, Aug 24, 2018 at 7:41 AM Benedikt Ritter wrote: > >> Hi, >> >> Am Fr., 24. Aug. 2018 um 09:06 Uhr schrieb Benedikt Ritter < >> brit...@apache.org>: >> >> > >> > >> > Am Do., 23. Aug. 2018 um 20:12 Uhr schrieb sebb : >> > >> >> Huh? >> >> >>

Re: [COLLECTIONS] Master branch build failing

On 24 August 2018 at 14:53, sebb wrote: > On 24 August 2018 at 14:46, Gary Gregory wrote: >> On Fri, Aug 24, 2018 at 7:41 AM Benedikt Ritter wrote: >> >>> Hi, >>> >>> Am Fr., 24. Aug. 2018 um 09:06 Uhr schrieb Benedikt Ritter < >>> brit...@apache.org>: >>> >>> > >>> > >>> > Am Do., 23. Aug. 2018

Re: [COLLECTIONS] Master branch build failing

On 24/08/18 14:46, Gary Gregory wrote: > On Fri, Aug 24, 2018 at 7:41 AM Benedikt Ritter wrote: > >> Hi, >> >> Am Fr., 24. Aug. 2018 um 09:06 Uhr schrieb Benedikt Ritter < >> brit...@apache.org>: >> >>> >>> >>> Am Do., 23. Aug. 2018 um 20:12 Uhr schrieb sebb : >>> Huh? Looks like

Re: [RNG] Build failure on "master"

Also: build fails (while running "Jacoco") with Java 10. On Fri, 17 Aug 2018 17:15:19 -0400, Rob Tompkins wrote: On Aug 15, 2018, at 6:41 PM, Gilles wrote: Hi. Build on "master" fails after the batch of commits post-release. See console output excerpt below. This is indeed weird. I’ve see

[GitHub] commons-validator pull request #14: VALIDATOR-446 ISSN extraction from EAN-1...

Github user alcole closed the pull request at: https://github.com/apache/commons-validator/pull/14 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.or

Re: New release distribution checksum policy

On 24.08.18 15:42, sebb wrote: > If it really is the case that the Apache Parent POM only creates the > checksums for artifacts with a specific name, then IMO it is badly > broken and needs a bug report. Feel free. Lines 425 to 454. > Note that it says: > "For every artifact distributed to the pu

Re: New release distribution checksum policy

On Fri, 24 Aug 2018 19:51:04 +0200, Thomas Vandahl wrote: On 24.08.18 15:42, sebb wrote: If it really is the case that the Apache Parent POM only creates the checksums for artifacts with a specific name, then IMO it is badly broken and needs a bug report. Feel free. Lines 425 to 454. Note th

Re: New release distribution checksum policy

On 24 August 2018 at 18:51, Thomas Vandahl wrote: > On 24.08.18 15:42, sebb wrote: >> If it really is the case that the Apache Parent POM only creates the >> checksums for artifacts with a specific name, then IMO it is badly >> broken and needs a bug report. > > Feel free. Lines 425 to 454. > >> N

Re: New release distribution checksum policy

On 24 August 2018 at 19:42, sebb wrote: > On 24 August 2018 at 18:51, Thomas Vandahl wrote: >> On 24.08.18 15:42, sebb wrote: >>> If it really is the case that the Apache Parent POM only creates the >>> checksums for artifacts with a specific name, then IMO it is badly >>> broken and needs a bug

[ALL] SHA256/512 hashes

As noted in another thread, I don't think the recent change to the Apache parent pom is of any use to Commons. However it does provide an example of how to use the checksum plugin. This has been used to create a sample profile that could be added to CP. See COMMONSSITE-121 Or for local testing

Re: [ALL] SHA256/512 hashes

Our release plugin already creates SHA256 and SHA512 files and saves those to Apache's dev/dist for an RC as part of creating an RC, pushing it to Nexus and dist/dev. Is what you are referring to for a different purpose? Gary On Fri, Aug 24, 2018 at 6:03 PM sebb wrote: > As noted in another th

[release-plugin] Taking up 1.4 now.

Just didn’t want to duplicate effort if someone else was planning to work on it. -Rob - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

[LAZY][VOTE] Release Apache Commons Release Plugin 1.4 based on RC1

We have fixed quite a few bugs and added some significant enhancements since Apache Commons Release Plugin 1.3 was released, so I would like to release Apache Commons Release Plugin 1.4. Apache Commons Release Plugin 1.4 RC1 is available for review here: https://dist.apache.org/repos/dist/d