Re: [email] Jenkins not building

On Wed, 28 Feb 2018 18:26:33 -0500, Otto Fowler wrote: Does this mean anything "Jenkins needs Java 7 for Maven jobs] Using -Pjava-1.6 JAVA_1_6_HOME is defined by the job, so may be incorrect for some hosts Solution TBA” If this is the cause, copy the relevant parts from the "commons-rng" conf

Re: [email] Jenkins not building

Does this mean anything "Jenkins needs Java 7 for Maven jobs] Using -Pjava-1.6 JAVA_1_6_HOME is defined by the job, so may be incorrect for some hosts Solution TBA” On February 28, 2018 at 18:03:08, Gary Gregory (garydgreg...@gmail.com) wrote: Can't figure out why: https://builds.apache.org/job/

[email] Jenkins not building

Can't figure out why: https://builds.apache.org/job/commons-email/ Thoughts from other Jenkins users? Gary

Re: [DISCUSS] new component for timing?

Le 28 févr. 2018 19:27, "Matt Sicker" a écrit : This sounds almost like a sort of Commons Metrics type project. See < http://metrics.dropwizard.io/4.0.0/> for an example. There's a sandbox project called Commons Monitoring which may be similar. Sirona started from commons-monitoring ;) On 28

RE: [COMPRESS] TIFF file identified as TAR

As always, thank you, Stefan! We might add a kluge at the Tika level to check for TIFF first...unless you'd like that kluge in your code? 😉 The reporter recommended one option: a conditional that checked the tarHeader variable to see if it started with one of the TIFF magic numbers (II/MM 49 49

[VOTE][LAZY] Release Commons Release Plugin 1.1 based on RC2

Hello all, This is a [LAZY][VOTE] for releasing Apache Commons Release Plugin 1.1 (from RC2). Tag name: commons-release-plugin-1.1-RC2 (signature can be checked from git using 'git tag -v') Tag URL: https://git-wip-us.apache.org/repos/asf?p=commons-release-plugin.git;a=tag;h=a0daa9c5a26

Re: [LANG] travis build failures

For a flaky test like this, perhaps running it N times and asserting that it passes ~N-1 iterations? On 28 February 2018 at 12:00, Otto Fowler wrote: > As long as it is the pr that fails, or that someone with rights to > re-trigger apache travis > notices and restarts the build. > > > On Februar

Re: [DISCUSS] new component for timing?

This sounds almost like a sort of Commons Metrics type project. See < http://metrics.dropwizard.io/4.0.0/> for an example. There's a sandbox project called Commons Monitoring which may be similar. On 28 February 2018 at 10:56, Gilles wrote: > On Wed, 28 Feb 2018 17:24:29 +0100, Romain Manni-Buca

Re: [LANG] travis build failures

As long as it is the pr that fails, or that someone with rights to re-trigger apache travis notices and restarts the build. On February 28, 2018 at 12:39:03, Gilles (gil...@harfang.homelinux.org) wrote: Hi. On Wed, 28 Feb 2018 08:49:42 +0200, Allon Mureinik wrote: > An alternative approach coul

Re: [LANG] travis build failures

Hi. On Wed, 28 Feb 2018 08:49:42 +0200, Allon Mureinik wrote: An alternative approach could be to remove the randomness from the test by using a predefined random seed and test the overloaded variants that accept a second java.util.Random argument. This will superficially reduce the test's cov

Re: [DISCUSS] new component for timing?

On Wed, 28 Feb 2018 17:24:29 +0100, Romain Manni-Bucau wrote: 2018-02-28 17:11 GMT+01:00 Gilles : On Wed, 28 Feb 2018 16:59:08 +0100, Romain Manni-Bucau wrote: Hi guys, On that topic we can keep in mind we retired not a lot time ago Apache Sirona which was a perf framework industrializing a

Re: [DISCUSS] new component for timing?

On Wed, 28 Feb 2018 08:56:07 -0700, Gary Gregory wrote: On Wed, Feb 28, 2018 at 6:35 AM, Gilles wrote: Hello. On Wed, 28 Feb 2018 04:56:36 -0800, Otto Fowler wrote: Hi, In the course of working through my pull request for adding new LANG functionality on top of the StopWatch class, the i

Re: [DISCUSS] new component for timing?

2018-02-28 17:11 GMT+01:00 Gilles : > On Wed, 28 Feb 2018 16:59:08 +0100, Romain Manni-Bucau wrote: > >> Hi guys, >> >> On that topic we can keep in mind we retired not a lot time ago Apache >> Sirona which was a perf framework industrializing a stopwatch to summarize >> it. >> We can make it live

Re: [DISCUSS] new component for timing?

On Wed, 28 Feb 2018 16:59:08 +0100, Romain Manni-Bucau wrote: Hi guys, On that topic we can keep in mind we retired not a lot time ago Apache Sirona which was a perf framework industrializing a stopwatch to summarize it. We can make it live again and would probably be a better fir than commo

Re: [DISCUSS] new component for timing?

Hi guys, On that topic we can keep in mind we retired not a lot time ago Apache Sirona which was a perf framework industrializing a stopwatch to summarize it. We can make it live again and would probably be a better fir than commons cause you quickly need more than just some time measurement when

Re: [DISCUSS] new component for timing?

On Wed, Feb 28, 2018 at 6:35 AM, Gilles wrote: > Hello. > > On Wed, 28 Feb 2018 04:56:36 -0800, Otto Fowler wrote: > >> Hi, >> >> In the course of working through my pull request for adding new LANG >> functionality on top of the StopWatch class, the issue has been raise as >> to >> if this funct

Re: Nexus: Staging Repository Dropped

More work to do here, as the .md5 files and .sha1 files on the dists respectively contain the same values. -Rob > On Feb 28, 2018, at 8:48 AM, Nexus Repository Manager > wrote: > > Message from: https://repository.apache.org > > Description: > > Bug found in

Re: [DISCUSS] new component for timing?

Hello. On Wed, 28 Feb 2018 04:56:36 -0800, Otto Fowler wrote: Hi, In the course of working through my pull request for adding new LANG functionality on top of the StopWatch class, the issue has been raise as to if this functionality is ‘common’ or should be placed in a more specialized common

[Testing][Lang] Scope of new component?

Hi. A timing utility was proposed by Otto Fowler for inclusion into [Lang]: https://issues.apache.org/jira/browse/LANG-1373 Gary questioned whether it was appropriate to include it in [Lang], and suggested the creation of a new "Commons Perf" component. I argued that the feature could be inclu

[DISCUSS] new component for timing?

Hi, In the course of working through my pull request for adding new LANG functionality on top of the StopWatch class, the issue has been raise as to if this functionality is ‘common’ or should be placed in a more specialized commons- component. We would like to take the discussion to the list