On 10/17/2014 03:52 AM, Gary Gregory wrote:
> On Thu, Oct 16, 2014 at 9:15 PM, sebb wrote:
>
>> On 15 October 2014 14:19, wrote:
>>> Author: ggregory
>>> Date: Wed Oct 15 13:19:50 2014
>>> New Revision: 1632011
>>>
>>> URL: http://svn.apache.org/r1632011
>>> Log:
>>> Update Oracle Mail from 1.4
On Thu, Oct 16, 2014 at 9:15 PM, sebb wrote:
> On 15 October 2014 14:19, wrote:
> > Author: ggregory
> > Date: Wed Oct 15 13:19:50 2014
> > New Revision: 1632011
> >
> > URL: http://svn.apache.org/r1632011
> > Log:
> > Update Oracle Mail from 1.4.7 to 1.5.2.
> >
> > Modified:
> > commons/pr
On 15 October 2014 14:19, wrote:
> Author: ggregory
> Date: Wed Oct 15 13:19:50 2014
> New Revision: 1632011
>
> URL: http://svn.apache.org/r1632011
> Log:
> Update Oracle Mail from 1.4.7 to 1.5.2.
>
> Modified:
> commons/proper/email/trunk/pom.xml
>
> Modified: commons/proper/email/trunk/pom
GitHub user jamessawle opened a pull request:
https://github.com/apache/commons-lang/pull/33
LANG-1050 Generic nullToEmpty method
A generic nullToEmpty method has been created. The idea was to use this as
a base for all of the wrapper class methods; however this would break the
con
Github user jamessawle closed the pull request at:
https://github.com/apache/commons-lang/pull/31
---
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 featur
GitHub user jamessawle opened a pull request:
https://github.com/apache/commons-lang/pull/32
Lang-536
Added new isSorted methods to the ArrayUtils class, along with generic
implementations.
Some of the primitive methods have needed reverse-engineered Java 7
'compare' meth
GitHub user jamessawle opened a pull request:
https://github.com/apache/commons-lang/pull/31
LANG-1050 Added new generic emptyToNull array method
Based upon the comments in
[JIRA](https://issues.apache.org/jira/browse/LANG-1050), I have implemented a
new generic defensive programmi
That should have been svn ignored. Arg. I'll have to fix when I get home.
Gary
Original message From: sebb
Date:10/16/2014 15:57 (GMT-05:00) To:
dev@commons.apache.org Cc: comm...@commons.apache.org
Subject: Re: svn commit: r1631874 - in /commons/proper/jcs/trunk:
commons
On 14 October 2014 21:42, wrote:
> Author: ggregory
> Date: Tue Oct 14 20:42:57 2014
> New Revision: 1631874
>
> URL: http://svn.apache.org/r1631874
> Log:
> Add maven-eclipse.xml and other Maven/Eclipse files to svn:ignore.
>
> Added:
> commons/proper/jcs/trunk/commons-jcs-core/.externalTool
To be honest, I really don't like this commit. My personal sense for
aesthetics put aside, you modified almost the whole code base. Patches
assigned to Jira tickets will probably no longer apply cleanly.
Oliver
Am 15.10.2014 um 22:15 schrieb ggreg...@apache.org:
> Author: ggregory
> Date: Wed Oct
OK. I submitted the pull request yesterday. I'm going to now remove the
diff from JIRA.
https://github.com/apache/commons-math/pull/2
On Tue, Oct 14, 2014 at 9:36 AM, luc wrote:
> Le 2014-10-14 15:16, Hank Grabowski a écrit :
>
>> Should I try an experiment with that with those interpolator
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38442&projectId=65
Build statistics:
State: Failed
Previous State: Ok
Started at: Thu 16 Oct 2014 17:09:07 +
Finished at: Thu 16 Oct 2014 17:10:33 +
Total time: 1m 26s
Build Trigger: Forced
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38438&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 16 Oct 2014 16:57:40 +
Finished at: Thu 16 Oct 2014 16:58:39 +
Total time: 58s
Build Trigger: Forced
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38437&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 16 Oct 2014 16:39:11 +
Finished at: Thu 16 Oct 2014 16:40:11 +
Total time: 59s
Build Trigger: Forced
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38436&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 16 Oct 2014 16:32:13 +
Finished at: Thu 16 Oct 2014 16:32:59 +
Total time: 46s
Build Trigger: Forced
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38435&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 16 Oct 2014 16:21:27 +
Finished at: Thu 16 Oct 2014 16:22:53 +
Total time: 1m 25s
Build Trigger: Force
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38434&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 16 Oct 2014 16:13:15 +
Finished at: Thu 16 Oct 2014 16:14:52 +
Total time: 1m 36s
Build Trigger: Force
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38431&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 16 Oct 2014 15:49:01 +
Finished at: Thu 16 Oct 2014 15:50:38 +
Total time: 1m 37s
Build Trigger: Force
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38430&projectId=65
Build statistics:
State: Failed
Previous State: Ok
Started at: Thu 16 Oct 2014 15:42:01 +
Finished at: Thu 16 Oct 2014 15:43:30 +
Total time: 1m 29s
Build Trigger: Forced
Once again, thank you Sebb for stepping in and explaining jar hell. It's
hellish just explaining it ;-)
Gary
On Thu, Oct 16, 2014 at 9:48 AM, sebb wrote:
> On 16 October 2014 14:30, Romain Manni-Bucau
> wrote:
> > 2014-10-16 14:40 GMT+02:00 sebb :
> >> On 16 October 2014 13:02, Romain Manni-Bu
On 16 October 2014 14:30, Romain Manni-Bucau wrote:
> 2014-10-16 14:40 GMT+02:00 sebb :
>> On 16 October 2014 13:02, Romain Manni-Bucau wrote:
>>> 2014-10-16 13:48 GMT+02:00 sebb :
On 16 October 2014 09:35, Thomas Vandahl wrote:
> On 16.10.14 02:06, sebb wrote:
>> On 16 October 2014
2014-10-16 14:40 GMT+02:00 sebb :
> On 16 October 2014 13:02, Romain Manni-Bucau wrote:
>> 2014-10-16 13:48 GMT+02:00 sebb :
>>> On 16 October 2014 09:35, Thomas Vandahl wrote:
On 16.10.14 02:06, sebb wrote:
> On 16 October 2014 00:47, Olivier Lamy wrote:
>> Perso I don' get the poi
On 16.10.14 12:17, Romain Manni-Bucau wrote:
> seems I can't do anything on jira,
I have added you as committer to the project.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands,
On 16.10.14 12:17, Romain Manni-Bucau wrote:
> seems I can't do anything on jira,
>
> here few action to do:
> 1) resolved as won't fix JCS-132 (we have to use java 7 for this tck module)
> 2) move JCS-130, JCS-119, JCS-116, JCS-16 to alpha2
Done.
Bye, Thomas.
-
On 16 October 2014 13:02, Romain Manni-Bucau wrote:
> 2014-10-16 13:48 GMT+02:00 sebb :
>> On 16 October 2014 09:35, Thomas Vandahl wrote:
>>> On 16.10.14 02:06, sebb wrote:
On 16 October 2014 00:47, Olivier Lamy wrote:
> Perso I don' get the point to use this version number at the end
2014-10-16 13:48 GMT+02:00 sebb :
> On 16 October 2014 09:35, Thomas Vandahl wrote:
>> On 16.10.14 02:06, sebb wrote:
>>> On 16 October 2014 00:47, Olivier Lamy wrote:
Perso I don' get the point to use this version number at the end of
the artifactId
>>>
>>> The idea is that if the pack
On 16 October 2014 09:35, Thomas Vandahl wrote:
> On 16.10.14 02:06, sebb wrote:
>> On 16 October 2014 00:47, Olivier Lamy wrote:
>>> Perso I don' get the point to use this version number at the end of
>>> the artifactId
>>
>> The idea is that if the package name has to be changed again, i.e. to
seems I can't do anything on jira,
here few action to do:
1) resolved as won't fix JCS-132 (we have to use java 7 for this tck module)
2) move JCS-130, JCS-119, JCS-116, JCS-16 to alpha2
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com
On 16.10.14 11:19, Romain Manni-Bucau wrote:
> If everybody is ok with a 2.0-alpha-1 can someone create this version
> on jira please?
Done.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For addition
Le 16/10/2014 11:19, Romain Manni-Bucau a écrit :
> If everybody is ok with a 2.0-alpha-1 can someone create this version
> on jira please?
Or rename the version 2.0 to 2.0-alpha-1, this avoids reaffecting the bugs.
It looks like JCS isn't configured like the other Commons components in
JIRA, I c
If everybody is ok with a 2.0-alpha-1 can someone create this version
on jira please?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-10-16 10:37 GMT+02:00 Thomas Vandahl :
> On 16.10.14 08:35, Romain Manni-Bucau wrot
On 16.10.14 08:35, Romain Manni-Bucau wrote:
> ok so it means we are ready to release?
As far As I'm concerned: Go ahead.
Please check JIRAs and docs.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
F
On 16.10.14 00:02, Emmanuel Bourg wrote:
> Le 15/10/2014 23:54, Gary Gregory a écrit :
>> Hm, no, the last item to agree on is the artifact Id. So... Some folks like
>> me like commons-jcs2 and other(s?) commons-jcs.
>
> My preference goes to commons-jcs without the version appended. That's
> no
On 16.10.14 02:06, sebb wrote:
> On 16 October 2014 00:47, Olivier Lamy wrote:
>> Perso I don' get the point to use this version number at the end of
>> the artifactId
>
> The idea is that if the package name has to be changed again, i.e. to
> org.apache.commons.jcs2, then the artifactId would be
I think jcs is nice since it keeps this history the project has.
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-10-16 8:49 GMT+02:00 Emmanuel Bourg :
> Do we want to keep the JCS name or switch to a more generic name
35 matches
Mail list logo