2015-02-17 7:04 GMT+01:00 Benedikt Ritter :
>
>
> 2015-02-17 0:13 GMT+01:00 Peter Ansell :
>
>> Hi Bernard,
>>
>> The Commons RDF project is not planning on including any non-trivial
>> implementations, to avoid bias towards any of the participating
>> platforms. Stian has written a trivial implem
2015-02-19 5:11 GMT+01:00 Gary Gregory :
> On Wed, Feb 18, 2015 at 7:04 PM, Ben McCann wrote:
>
> > Would it be possible to release 6.0 now and release Mark's patches as 6.1
> > or 7.0? I'm concerned it may be quite a long time before his patches are
> > committed since they are not actively bein
On Wed, Feb 18, 2015 at 7:04 PM, Ben McCann wrote:
> Would it be possible to release 6.0 now and release Mark's patches as 6.1
> or 7.0? I'm concerned it may be quite a long time before his patches are
> committed since they are not actively being reviewed and there is no
> activity on them for t
Would it be possible to release 6.0 now and release Mark's patches as 6.1
or 7.0? I'm concerned it may be quite a long time before his patches are
committed since they are not actively being reviewed and there is no
activity on them for the past couple weeks.
There is little downside to frequent r
Github user artnaseef closed the pull request at:
https://github.com/apache/commons-lang/pull/45
---
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 feature
enabled and wishes so, or if the feature
GitHub user artnaseef opened a pull request:
https://github.com/apache/commons-lang/pull/45
Replace the busy wait from AtomicSafeInitializer with an alternate method
that eliminates wasted CPU cycles
This patch eliminates the busy-wait in AtomicSafeInitializer that consumes
signifi
On 2/18/15 7:43 AM, Thomas Neidhart wrote:
> Sorry it was my mistake, I did not test the change with Java 8.
>
> The pom.xml is now fixed, I used the same override for jacoco as was used
> for commons-math 3.4
Thanks!
Phil
>
> Thomas
>
> On Wed, Feb 18, 2015 at 3:24 PM, Thomas Neidhart
> wrote:
Sorry it was my mistake, I did not test the change with Java 8.
The pom.xml is now fixed, I used the same override for jacoco as was used
for commons-math 3.4
Thomas
On Wed, Feb 18, 2015 at 3:24 PM, Thomas Neidhart
wrote:
> I enabled jacoco a while a go, but if you would prefer cobertura we ca
I enabled jacoco a while a go, but if you would prefer cobertura we can
easily change to it.
Thomas
On Wed, Feb 18, 2015 at 2:54 PM, Phil Steitz wrote:
> On 2/18/15 6:52 AM, Emmanuel Bourg wrote:
> > Le 18/02/2015 14:48, Phil Steitz a écrit :
> >
> >> That is not good. What JDK and OS?
> > Tha
Le 18/02/2015 14:47, Phil Steitz a écrit :
> Good point. If you or others feel strongly that this is too ugly, I
> can change and re-roll.
>
> Any other opinions on this?
>
> Thanks for the review!
On the same line I wonder if the isFastFailValidation() method would be
better named isFailFastV
Due to problems with JDK 8 build...
On 2/16/15 9:04 PM, Phil Steitz wrote:
> Quite a few bugs have been fixed since DBCP 2.0.1 and a few new
> features have been added. It is time for a 2.1 release.
>
> The release is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/dbc
On 2/18/15 6:52 AM, Emmanuel Bourg wrote:
> Le 18/02/2015 14:48, Phil Steitz a écrit :
>
>> That is not good. What JDK and OS?
> That was with OpenJDK 8u40b22 on Debian Jessie.
Thanks. I was just able to replicate. I need to get rid of the
jacoco nonsense somehow. Will fix and reroll.
Phil
>
Le 18/02/2015 14:48, Phil Steitz a écrit :
> That is not good. What JDK and OS?
That was with OpenJDK 8u40b22 on Debian Jessie.
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional comman
On 2/18/15 5:05 AM, Emmanuel Bourg wrote:
> Le 17/02/2015 16:50, Phil Steitz a écrit :
>
>> That is just the site build, which is not essential to the release,
>> IMO, so again not a blocker.
> Not only the site build, I got the same error with a simple 'mvn test'.
That is not good. What JDK and
On 2/18/15 6:30 AM, Emmanuel Bourg wrote:
>> [X] +1 Release these artifacts
> Tested with OpenJDK 7 on Debian.
>
> The name of the isLogExpiredConnections() method in BasicDataSource and
> BasicDataSourceMXBean looks a bit inconsistent with the other methods
> returning a boolean. I would have pick
On 2/18/15 3:08 AM, Thomas Neidhart wrote:
> hmm, I do not know what I have seen yesterday, but the references to dbcp
> 2.x and pool 2.3 are already correct.
Thanks. That was driving me crazy. Could be some funny svn mirror
lag or something if you were hitting them from the web page instead
of l
> [X] +1 Release these artifacts
Tested with OpenJDK 7 on Debian.
The name of the isLogExpiredConnections() method in BasicDataSource and
BasicDataSourceMXBean looks a bit inconsistent with the other methods
returning a boolean. I would have picked getLogExpiredConnections
(similar to the getRemo
2015-02-18 13:22 GMT+01:00 Stian Soiland-Reyes :
> Also, as changing Java package names is a drastic step, you would
> think three times before introducing breaking changes at all. (or if
> you do - do so with a big bang and "fix everything" :) ).
>
> So I think this specialization looks all sensi
Also, as changing Java package names is a drastic step, you would
think three times before introducing breaking changes at all. (or if
you do - do so with a big bang and "fix everything" :) ).
So I think this specialization looks all sensible, specially for
Apache Commons which are utility librari
Le 17/02/2015 16:50, Phil Steitz a écrit :
> That is just the site build, which is not essential to the release,
> IMO, so again not a blocker.
Not only the site build, I got the same error with a simple 'mvn test'.
Emmanuel Bourg
---
hmm, I do not know what I have seen yesterday, but the references to dbcp
2.x and pool 2.3 are already correct.
I have updated the other 2 examples to use an h2 database as already
outlined in the PoolingDataSourceExample.
Thomas
On Wed, Feb 18, 2015 at 1:13 AM, Phil Steitz wrote:
> On 2/17/15
21 matches
Mail list logo
