OH what a wonderful surprise, that makes me feel touched :)
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Tue, Feb 18, 2014 at 6:51 PM, Benedikt Ritter brit...@apache.org wrote:
Hi all,
I've just published our website. The new skin is now online. [1]
It may be my fault, that this is online now, since I've republished the
website yesterday. I'll have a look and see what I can clean up.
2014-02-26 21:04 GMT+01:00 Edmond Kemokai ekemo...@gmail.com:
ok.
On Wed, Feb 26, 2014 at 3:00 PM, Mark Thomas ma...@apache.org wrote:
On 26/02/2014
Hello Ate,
without knowing SCXML or the specs here are my thought about your proposals
(just from a apache commons point of view ;-):
2014-02-27 0:48 GMT+01:00 Ate Douma a...@douma.nu:
Hi SCXML and other community members/developers,
After working on the new Commons SCXML 2.0 code base for
On 27-02-14 11:30, Benedikt Ritter wrote:
Hello Ate,
without knowing SCXML or the specs here are my thought about your proposals
(just from a apache commons point of view ;-):
2014-02-27 0:48 GMT+01:00 Ate Douma a...@douma.nu:
Hi SCXML and other community members/developers,
After working
Hi,
I've worked on the website today. It uses the new design now. I've fixed
some broken links also. If you find anything that's not working, just drop
me a message.
Benedikt
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
Hello Stefan,
the project reports look good to me. Some package have low test coverage
but I think you've already said that it's pretty hard to write tests for
this areas of the code. PMD shows four violations. The first three look
like they can be fixed easily.
Benedikt
2014-02-27 8:03
I've changed the date for 1.6 in the changes report to TBA.
2014-02-27 11:23 GMT+01:00 Benedikt Ritter brit...@apache.org:
It may be my fault, that this is online now, since I've republished the
website yesterday. I'll have a look and see what I can clean up.
2014-02-26 21:04 GMT+01:00
Well... any idea about this?
2014-02-26 10:45 GMT+01:00 Apache Continuum d...@continuum.apache.org:
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28250projectId=74
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 26 Feb
On 27-02-14 13:36, Benedikt Ritter wrote:
Hi,
I've worked on the website today. It uses the new design now. I've fixed
some broken links also. If you find anything that's not working, just drop
me a message.
Wow, many thanks!
It looks great and 'refreshed' :)
After only a quick check I see
2014-02-27 13:52 GMT+01:00 Ate Douma a...@douma.nu:
On 27-02-14 13:36, Benedikt Ritter wrote:
Hi,
I've worked on the website today. It uses the new design now. I've fixed
some broken links also. If you find anything that's not working, just drop
me a message.
Wow, many thanks!
It looks
2014-02-27 13:57 GMT+01:00 Benedikt Ritter brit...@apache.org:
2014-02-27 13:52 GMT+01:00 Ate Douma a...@douma.nu:
On 27-02-14 13:36, Benedikt Ritter wrote:
Hi,
I've worked on the website today. It uses the new design now. I've fixed
some broken links also. If you find anything that's
Hi Benedikt,
you have to create and put the file download_scxml.cgi into
src/site/resources
Take a look at some other components about the content.
Thomas
On Thu, Feb 27, 2014 at 2:05 PM, Benedikt Ritter brit...@apache.org wrote:
2014-02-27 13:57 GMT+01:00 Benedikt Ritter
On 2014-02-27, Benedikt Ritter wrote:
the project reports look good to me. Some package have low test coverage
but I think you've already said that it's pretty hard to write tests for
this areas of the code. PMD shows four violations. The first three look
like they can be fixed easily.
Not
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28275projectId=73
Build statistics:
State: Failed
Previous State: Error
Started at: Thu 27 Feb 2014 13:20:11 +
Finished at: Thu 27 Feb 2014 13:20:14 +
Total time: 2s
Build Trigger: Schedule
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28276projectId=74
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 27 Feb 2014 13:20:18 +
Finished at: Thu 27 Feb 2014 13:20:38 +
Total time: 20s
Build Trigger: Schedule
I think [imaging] had similar problem days ago [1]
Maybe looking at the commits sent to [imaging] could be of some help. Just my
0.02 cents :)
HTH
Bruno
[1] http://markmail.org/thread/lxdlwp35vdlwousi
- Original Message -
From: Benedikt Ritter brit...@apache.org
To: Commons
On Feb 27, 2014 4:35 AM, Ate Douma a...@douma.nu wrote:
On 27-02-14 11:30, Benedikt Ritter wrote:
Hello Ate,
without knowing SCXML or the specs here are my thought about your
proposals
(just from a apache commons point of view ;-):
2014-02-27 0:48 GMT+01:00 Ate Douma a...@douma.nu:
Hi
It looks like this should be a smooth release :)
Gary
On Thu, Feb 27, 2014 at 2:03 AM, Stefan Bodewig bode...@apache.org wrote:
Hi all,
this is a heads-up that I intend to cut a RC for Compress 1.8 soon. We
have accumulated a few bugfixes and at least COMPRESS-264 is pretty
serious.
Hi,
Trying to run the tests for [imaging] on the current development
version, I keep getting a failing Junit test.
Failed tests:
MicrosoftTagTest.testRewrite:77-checkFields:85 expected:[title] but
was:[WE à l'étang de Blodelsheim]
Is this failure expected? I am running the tests suite on
Should be working now :-)
2014-02-27 14:22 GMT+01:00 Bruno P. Kinoshita brunodepau...@yahoo.com.br:
I think [imaging] had similar problem days ago [1]
Maybe looking at the commits sent to [imaging] could be of some help. Just
my 0.02 cents :)
HTH
Bruno
[1]
All the tests run for me from Eclipse on Windows 7 with Java 7 64 bit.
Gary
On Thu, Feb 27, 2014 at 9:25 AM, luc l...@spaceroots.org wrote:
Hi,
Trying to run the tests for [imaging] on the current development version,
I keep getting a failing Junit test.
Failed tests:
On 27-02-14 15:53, Benedikt Ritter wrote:
Should be working now :-)
Yes it does. Thanks!
2014-02-27 14:22 GMT+01:00 Bruno P. Kinoshita brunodepau...@yahoo.com.br:
I think [imaging] had similar problem days ago [1]
Maybe looking at the commits sent to [imaging] could be of some help.
it works at least in my environment which is:
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home:
On 2014-02-27, luc wrote:
Is this failure expected? I am running the tests suite on a Linux
computer, maybe MicrosoftTagTest is windows-specific?
all tests pass for me:
$ uname -a
Linux brick 3.5.0-46-generic #70-Ubuntu SMP Wed Jan 8 18:40:46 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
$ java
Hi,
I'm preparing lang 3.3 RC 1. While looking through the reports I've
noticed, that we have a Clirr error in 3.3 compared to 3.2.1 [1]. This was
introduced in r1557882 [2]. The change is a result of LANG-950 [3]
The question for me is: can we handle this change without breaking BC?
Benedikt
On Wed, 26 Feb 2014 21:18:01 -0500, Bruce A Johnson wrote:
On Feb 26, 2014, at 6:23 PM, Bruce A Johnson johns...@umbc.edu
wrote:
The NonLinearConjugateGradientOptimizer does a line search for a
zero in the gradient (see comment from source below), rather than a
search for a minimum of the
Le 2014-02-27 16:22, Stefan Bodewig a écrit :
On 2014-02-27, luc wrote:
Is this failure expected? I am running the tests suite on a Linux
computer, maybe MicrosoftTagTest is windows-specific?
all tests pass for me:
$ uname -a
Linux brick 3.5.0-46-generic #70-Ubuntu SMP Wed Jan 8 18:40:46
Could this be code page related?
Gary
On Thu, Feb 27, 2014 at 11:10 AM, luc l...@spaceroots.org wrote:
Le 2014-02-27 16:22, Stefan Bodewig a écrit :
On 2014-02-27, luc wrote:
Is this failure expected? I am running the tests suite on a Linux
computer, maybe MicrosoftTagTest is
The raw image has the XP TITLE field in IFD0, but the test writes it
into the EXIF IFD and then reads it from any IFD, so it could find it
the wrong one. The search order must be different, but I don't
understand why.
In any case, the whole TIFF package is full of nonsense and in need of
a
It has been a while since it was first suggested but we have reached the
point where DBCP 2.0 is ready for release.
The significant changes are:
- switched to Pool 2 for better performance
- added JMX support
We have also fixed quite a few bugs
DBCP 2.0 RC1 is available for review here:
Can we add back a ctor?
Gary
On Thu, Feb 27, 2014 at 10:37 AM, Benedikt Ritter brit...@apache.orgwrote:
Hi,
I'm preparing lang 3.3 RC 1. While looking through the reports I've
noticed, that we have a Clirr error in 3.3 compared to 3.2.1 [1]. This was
introduced in r1557882 [2]. The change
ISTR someone saying it seemed like it would be safe to make this break in
BC because there were likely to be no existing FastDateParser subclasses.
However, the compatibility was preserved in FastDateFormat by passing
through a null *to* FastDateParser, so doing the same on FastDateParser
itself
While it exists in 1.x, the package org.apache.commons.dbcp.cpdsadapter
would be could have a better, simpler name like
org.apache.commons.dbcp2.cpds and some package level docs just to say what
CPDS even is for our first time users.
Aside from that, builds OK from zip src (hash and sig OK) with
33 matches
Mail list logo
