Re: [All] Jenkins: where are the projects?

I do remember Infra team warned in end of July '17 to remove Commons from top-level to A-D or C tab else they were about to remove it on 1st August '17 ... And they did it . But no worries we already had it in A-D tab. https://builds.apache.org/view/A-D/view/Commons/ Regards, Amey On Thu, Aug 1

Re: [VOTE] Release Apache Commons JCS 2.2 based on RC1

This VOTE is 7 days old. Has it been tallied? Did I miss it? Gary On Wed, Aug 2, 2017 at 6:32 AM, Thomas Vandahl wrote: > I would like to release the [jcs] component to resolve some overdue bugs > > Apache Commons JCS 2.2 RC1 is available for review at: > https://dist.apache.org/repos/dist/de

Re: [All] Jenkins: where are the projects?

I thought we already had a new view, I guess not :-( Gary On Wed, Aug 9, 2017 at 5:17 PM, Gilles wrote: > Hi. > > The top view does not show "Commons" anymore. > [I do recall some notice about a change on Jenkins. > But, no, I don't know whether every developer had to > do something and, if so,

[All] Jenkins: where are the projects?

Hi. The top view does not show "Commons" anymore. [I do recall some notice about a change on Jenkins. But, no, I don't know whether every developer had to do something and, if so, what and how...] Thanks, Gilles - To unsubscri

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Wed, Aug 9, 2017 at 4:52 PM, Gilles wrote: > On Thu, 10 Aug 2017 01:31:04 +0200, Gilles wrote: > >> On Wed, 9 Aug 2017 16:10:58 -0700, Gary Gregory wrote: >> >>> On Wed, Aug 9, 2017 at 3:52 PM, Gilles >>> wrote: >>> >>> On Wed, 9 Aug 2017 15:23:23 -0700, Gary Gregory wrote: I would

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Thu, 10 Aug 2017 01:48:48 +0200, Gilles wrote: On Thu, 10 Aug 2017 00:30:59 +0100, sebb wrote: On 10 August 2017 at 00:08, Gilles wrote: On Wed, 9 Aug 2017 23:48:30 +0100, sebb wrote: On 9 August 2017 at 23:19, Gilles wrote: On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote: On 9 Augus

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Thu, 10 Aug 2017 01:31:04 +0200, Gilles wrote: On Wed, 9 Aug 2017 16:10:58 -0700, Gary Gregory wrote: On Wed, Aug 9, 2017 at 3:52 PM, Gilles wrote: On Wed, 9 Aug 2017 15:23:23 -0700, Gary Gregory wrote: I would start by updating the Maven plugins and any third party deps. For example:

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Thu, 10 Aug 2017 00:30:59 +0100, sebb wrote: On 10 August 2017 at 00:08, Gilles wrote: On Wed, 9 Aug 2017 23:48:30 +0100, sebb wrote: On 9 August 2017 at 23:19, Gilles wrote: On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote: On 9 August 2017 at 13:51, Gilles wrote: Hi. Build with

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Wed, 9 Aug 2017 16:10:58 -0700, Gary Gregory wrote: On Wed, Aug 9, 2017 at 3:52 PM, Gilles wrote: On Wed, 9 Aug 2017 15:23:23 -0700, Gary Gregory wrote: I would start by updating the Maven plugins and any third party deps. For example: [INFO] --- maven-jgit-buildnumber-plugin:1.2.10:e

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On 10 August 2017 at 00:08, Gilles wrote: > On Wed, 9 Aug 2017 23:48:30 +0100, sebb wrote: >> >> On 9 August 2017 at 23:19, Gilles wrote: >>> >>> On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote: On 9 August 2017 at 13:51, Gilles wrote: > > > Hi. > > Build with Ja

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Wed, Aug 9, 2017 at 3:52 PM, Gilles wrote: > On Wed, 9 Aug 2017 15:23:23 -0700, Gary Gregory wrote: > >> I would start by updating the Maven plugins and any third party deps. >> >> For example: >> >> [INFO] --- maven-jgit-buildnumber-plugin:1.2.10:extract-buildnumber >> (default) @ commons-mat

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Wed, 9 Aug 2017 23:48:30 +0100, sebb wrote: On 9 August 2017 at 23:19, Gilles wrote: On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote: On 9 August 2017 at 13:51, Gilles wrote: Hi. Build with Java 8 runs fine: https://travis-ci.org/apache/commons-math/jobs/262647212 But with Java 7:

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Wed, 9 Aug 2017 15:23:23 -0700, Gary Gregory wrote: I would start by updating the Maven plugins and any third party deps. For example: [INFO] --- maven-jgit-buildnumber-plugin:1.2.10:extract-buildnumber (default) @ commons-math4 --- [ERROR] org.eclipse.jgit.errors.RevWalkException: Walk fa

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On 9 August 2017 at 23:19, Gilles wrote: > On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote: >> >> On 9 August 2017 at 13:51, Gilles wrote: >>> >>> Hi. >>> >>> Build with Java 8 runs fine: >>> https://travis-ci.org/apache/commons-math/jobs/262647212 >>> >>> But with Java 7: >>> https://travis-ci

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

I would start by updating the Maven plugins and any third party deps. For example: [INFO] --- maven-jgit-buildnumber-plugin:1.2.10:extract-buildnumber (default) @ commons-math4 --- [ERROR] org.eclipse.jgit.errors.RevWalkException: Walk failure. Why not try updating maven-jgit-buildnumber-plugi

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote: On 9 August 2017 at 13:51, Gilles wrote: Hi. Build with Java 8 runs fine: https://travis-ci.org/apache/commons-math/jobs/262647212 But with Java 7: https://travis-ci.org/apache/commons-math/jobs/262647211 Is anyone willing to debug this fail

[GitHub] commons-imaging pull request #30: add-tests

Github user TheRealHaui commented on a diff in the pull request: https://github.com/apache/commons-imaging/pull/30#discussion_r132311416 --- Diff: pom.xml --- @@ -209,6 +209,12 @@ 2.5 test + --- End diff -- Understand your point.

[GitHub] commons-imaging pull request #30: add-tests

Github user kinow commented on a diff in the pull request: https://github.com/apache/commons-imaging/pull/30#discussion_r132310660 --- Diff: pom.xml --- @@ -209,6 +209,12 @@ 2.5 test + --- End diff -- Indeed, and I may even use it

[GitHub] commons-imaging issue #30: add-tests

Github user TheRealHaui commented on the issue: https://github.com/apache/commons-imaging/pull/30 Changes incorporated. Build working. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] commons-imaging pull request #30: add-tests

Github user TheRealHaui commented on a diff in the pull request: https://github.com/apache/commons-imaging/pull/30#discussion_r132308184 --- Diff: pom.xml --- @@ -209,6 +209,12 @@ 2.5 test + --- End diff -- Well, Equalsverifier ch

[GitHub] commons-imaging pull request #30: add-tests

Github user TheRealHaui commented on a diff in the pull request: https://github.com/apache/commons-imaging/pull/30#discussion_r132307800 --- Diff: src/test/java/org/apache/commons/imaging/formats/tiff/taginfos/TagInfoByteOrShortTest.java --- @@ -0,0 +1,55 @@ +/* + * Licens

[GitHub] commons-imaging pull request #30: add-tests

Github user TheRealHaui commented on a diff in the pull request: https://github.com/apache/commons-imaging/pull/30#discussion_r132306981 --- Diff: src/test/java/org/apache/commons/imaging/formats/pnm/PgmFileInfoTest.java --- @@ -0,0 +1,49 @@ +/* + * Licensed to the Apache S

[GitHub] commons-imaging pull request #30: add-tests

Github user TheRealHaui commented on a diff in the pull request: https://github.com/apache/commons-imaging/pull/30#discussion_r132306138 --- Diff: src/test/java/org/apache/commons/imaging/formats/pnm/PgmFileInfoTest.java --- @@ -0,0 +1,49 @@ +/* + * Licensed to the Apache S

Re: Ready for JDK 9 ?

On Wed, Aug 9, 2017 at 1:00 PM, Ralph Goers wrote: > I have my doubts about the module system but I am not sure why you would > think multi-release jars will cause problems. > IIRC, multi-release jars causes problem in the Android tool chain. I imagine there are going to be a lot of catching up

Re: Ready for JDK 9 ?

I have my doubts about the module system but I am not sure why you would think multi-release jars will cause problems. Ralph > On Aug 9, 2017, at 8:28 AM, Gary Gregory wrote: > > On Wed, Aug 9, 2017 at 1:09 AM, Jörg Schaible < > joerg.schai...@bpm-inspire.com

Re: Ready for JDK 9 ?

Hi Jorg, Yes, I think rather just checking latest released source we should check the HEAD of components to ensure we will not break next planned release with java 9, at least we can fix if there is some issue from java9 RC it self, that will ensure future stability. Looking at commons-text late

Re: Ready for JDK 9 ?

On Wed, Aug 9, 2017 at 1:09 AM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > Hi Simon, > > Simon Spero wrote: > > > Compress HEAD is tested against the equivalent of RC. The main issues > were > > with tests; some types of mocking (especially of concrete classes) don't > > work. This m

Re: [Math][ALL] Travis failing (with JDK7 but not JDK8)

On 9 August 2017 at 13:51, Gilles wrote: > Hi. > > Build with Java 8 runs fine: > https://travis-ci.org/apache/commons-math/jobs/262647212 > > But with Java 7: > https://travis-ci.org/apache/commons-math/jobs/262647211 > > Is anyone willing to debug this failure? 1) Bug in maven-jgit-buildnum

[Math][ALL] Travis failing (with JDK7 but not JDK8)

Hi. Build with Java 8 runs fine: https://travis-ci.org/apache/commons-math/jobs/262647212 But with Java 7: https://travis-ci.org/apache/commons-math/jobs/262647211 Is anyone willing to debug this failure? Or is this a hint for making Java 8 the minimum supported version for the next releas

Re: [ALL] Automated requirements (e.g. CheckStyle)?

On 9 August 2017 at 03:57, Gilles wrote: > On Tue, 8 Aug 2017 18:49:44 -0700, Chas Honton wrote: >> >> Since most of us work in an IDE, the "wasted" time of checkstyle for >> every build is negligible. IDEs vary in how easy it is to set up the checks to agree with the project settings. And IDEs v

Re: Ready for JDK 9 ?

Hi Simon, Simon Spero wrote: > Compress HEAD is tested against the equivalent of RC. The main issues were > with tests; some types of mocking (especially of concrete classes) don't > work. This might have been fixed by now. > I believe that the latest jacoco is 9 compatible. > > [The biggest pro

Re: Ready for JDK 9 ?

Hi Amey, Amey Jadiye wrote: > Hmm, isn't that easy with just Travis ? We just have to add java9 > option(not sure it have RC) and trigger build it will automatically check > build and tests. IIRC for few components we are having java9 Travis env > already set. That would only ensure that the hea