Welcome Arnout!
On Mon, Dec 23, 2024, at 19:00, Gary Gregory wrote:
> Welcome aboard Arnout, our latest committer and PMC member!
>
> Gary
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e
On Mon, Dec 1, 2014, at 18:04, sebb wrote:
> On 1 December 2014 at 09:28, Christian Grobmeier
> wrote:
> > That aside, I would do the following:
> >
> > - jdk support for at least >7 (varargs need 5, but MessageFormat 7)
Just saw MessageFormat is even available in jdk
t? WRT Log4j 2: So there's another thing to compare WRT to
> > performance and String.format and our own {} support... any thoughts on
> > that?
> >
> > Gary
> >
> >
> > On Mon, Dec 1, 2014 at 4:28 AM, Christian Grobmeier
> > wrote:
> >
> &g
t
judgement for now
Christian
>
> Gary
>
>
> On Mon, Dec 1, 2014 at 4:28 AM, Christian Grobmeier
> wrote:
>
> > On Mon, Dec 1, 2014, at 00:50, sebb wrote:
> > > But it would be interesting to know why the Spring dev thought a new
> > > version wou
That aside, I would do the following:
- jdk support for at least >7 (varargs need 5, but MessageFormat 7)
- remove AvalonLogger and LogKitLogger
>
> > For anything more I would point to log4j 2.
> >
> > Gary
> >
> > Original message From
Hi folks,
I am perfectly aware that I was saying CL needs to be deprecated only
before month.
Tomcat uses CL and that was more or less the reason it would stay - so I
thought.
Recently I talked to a person actively involved in Spring. He explained,
Spring would use
CL and they are quite happy with
com/rmannibucau
>
>
> 2014-08-21 22:04 GMT+02:00 Gary Gregory :
>> On Thu, Aug 21, 2014 at 3:37 PM, Romain Manni-Bucau
>> wrote:
>>
>>> 2014-08-21 21:15 GMT+02:00 Christian Grobmeier :
>>> > On 20 Aug 2014, at 15:47, sebb wrote:
>>> >
Romain,
On Thu, Aug 21, 2014 at 9:37 PM, Romain Manni-Bucau
wrote:
> 2014-08-21 21:15 GMT+02:00 Christian Grobmeier :
> Not adding a dependency for one line answer.
>
> For longer one: take tomee example: we have [logging], slf4j cause of
> dependencies but as soon as we'l
On 20 Aug 2014, at 15:47, sebb wrote:
On 20 August 2014 14:37, Gary Gregory wrote:
On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote:
On 20 August 2014 14:04, Gary Gregory
wrote:
Moving discussion about logging from [JCS-122] to this dev ML.
Why not use Log4j 2, uses can redirect logging to ot
On 20 Aug 2014, at 19:35, Thomas Vandahl wrote:
On 20.08.14 15:37, Gary Gregory wrote:
On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote:
On 20 August 2014 14:04, Gary Gregory
wrote:
Moving discussion about logging from [JCS-122] to this dev ML.
Why not use Log4j 2, uses can redirect logging to
Hi folks,
i found this interesting:
http://www.takipiblog.com/2013/11/26/githubs-1-most-popular-java-projects-here-are-the-top-libraries-they-use/
Cheers
Christian
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
-
T
On 5 Dec 2013, at 13:44, Valentin Waeselynck wrote:
Should I keep answering to the whole ML about this, or only to you?
Keep the mailing list in loop. There might be others interested in this.
In addition ml do document history which is why we always use the ml.
Best regards,
Valentin
3 03:42 (GMT-05:00)
To: Commons Developers List
Subject: Re: [all] Removing websites of dormant components
Le 04/12/2013 09:35, Christian Grobmeier a écrit :
No objections or no interest?
A few more comments would have been helpful.
I am going to remove all dormant javadocs on friday or sat
, Christian Grobmeier wrote:
On 29 Nov 2013, at 19:21, sebb wrote:
I agree that the Javadoc pages could be removed.
Although it would not be difficult to fix the individual pages,
there's not much point in fixing Javadoc for dormant components.
However I'm not sure it makes sense to delete
On 29 Nov 2013, at 19:21, sebb wrote:
I agree that the Javadoc pages could be removed.
Although it would not be difficult to fix the individual pages,
there's not much point in fixing Javadoc for dormant components.
However I'm not sure it makes sense to delete the entire website
because of the
On 29 Nov 2013, at 14:44, Emmanuel Bourg wrote:
Le 29/11/2013 14:28, Christian Grobmeier a écrit :
We should respect the naming conventions of git as good as possible.
But git is a tool, not a development method, right? As such it doesn't
mandate any specific workflow, even if a r
On 29 Nov 2013, at 14:39, Torsten Curdt wrote:
This in fact means:
create a master branch which is stable.
create a develop branch which is not so stable.
create feature branches from develop where you work out your
changes.
We are just swapping the branch names here, in the end your mod
On 29 Nov 2013, at 14:09, Emmanuel Bourg wrote:
Le 29/11/2013 12:20, Christian Grobmeier a écrit :
This in fact means:
create a master branch which is stable.
create a develop branch which is not so stable.
create feature branches from develop where you work out your changes.
We are just
On 19.10. I wrote a mail in response to Henri Yandell.
http://markmail.org/message/c63kqyipuy6islib
I would like to follow up on the issues i mentioned there.
Our dormant components are unmaintained and our dormant websites are
broken.
Therefore I would like to remove the websites.
In example
On 26 Nov 2013, at 14:35, Gary Gregory wrote:
On Tue, Nov 26, 2013 at 3:52 AM, Emmanuel Bourg
wrote:
Le 26/11/2013 08:43, Benedikt Ritter a écrit :
I propose [1] as branching model. It looks very complicated at
first, but
I've found it very useful to always have a release ready version of
On 14 Nov 2013, at 10:01, Emmanuel Bourg wrote:
Le 10/11/2013 21:46, Christian Grobmeier a écrit :
From all the log4j talks I gave recently there were zero people using
commons-logging. For me it is dead.
For what it's worth, the install base of commons-logging in Debian is
ten time
On 10 Nov 2013, at 21:24, henrib wrote:
Would you share why ? I'm sure it would be beneficial to others
(including
the commons logging community).
Sorry I was short in my reply because I mentioned this a few times
already. Didn't find the mails, so here we go:
As you probably know, I have
On 10 Nov 2013, at 18:47, Lukasz Lenart wrote:
Ok, so let's leave logging layer for now and we should focus on
preparing the first release
+1, thanks Lukasz!
2013/11/9 Gary Gregory :
Neither does log4j 2 ;)
Original message
From: henrib
Date:11/09/2013 12:23 (GMT-05:0
I like it pretty much. Good job.
Anything which can go back into fluido and gives us the chnace to work
with the "original fluido"?
On 2 Nov 2013, at 18:47, Thomas Neidhart wrote:
Hi all,
I have further reworked the skin available at
https://github.com/netomi/commons-skin-fluido and the res
On 9 Nov 2013, at 19:54, Christian Grobmeier wrote:
On 7 Nov 2013, at 18:08, Lukasz Lenart wrote:
2013/11/7 Jason Pyeron :
-Original Message-
From: Benedikt Ritter
Sent: Thursday, November 07, 2013 11:00
Yes, as long as it's Log4j2 ;-)
Now I need a sed script to replace
On 7 Nov 2013, at 18:08, Lukasz Lenart wrote:
2013/11/7 Jason Pyeron :
-Original Message-
From: Benedikt Ritter
Sent: Thursday, November 07, 2013 11:00
Yes, as long as it's Log4j2 ;-)
Now I need a sed script to replace j.u.l. to it...
Is Log4j2 the one that is desired? I figured S
On 9 Nov 2013, at 18:23, henrib wrote:
IMHO, commons logging is the best choice for this kinds of lib; it
does not
force the choice of the implementation library.
No. Commons Logging is NOT the best choice. It's one of the worst.
Just my opinion, but I will object to that.
Henrib
--
View
al Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Wednesday, September 04, 2013 4:28
To: Commons Developers List
Subject: Re: [OGNL] Make use of logging?
2013/9/4 Lukasz Lenart
2013/9/3 Christian Grobmeier :
I found 11 uses of e.printStackTrace and think its pretty bad.
On 19 Oct 2013, at 17:22, Henri Yandell wrote:
On Sat, Oct 19, 2013 at 7:25 AM, Christian Grobmeier
wrote:
Being in the attic is NOT a permanent thing. Get active developers,
leave
the attic. If a project doesn't make any sense, stay in the attic.
We are having an attic but called it &qu
On 18 Oct 2013, at 9:24, Jörg Schaible wrote:
Hi Christian,
Christian Grobmeier wrote:
On 17 Oct 2013, at 18:12, Paul Benedict wrote:
I am glad to hear being "dormant" is not the same thing as being in
the
"attic"
Why?
Because "attic" means more or less t
one in the attic - except that the term "attic" is more
established (as in foundation wide)
as the term "dormant".
That said, I will not fight for removing the dormant-term. If you all
like it keep it.
On Thu, Oct 17, 2013 at 11:03 AM, Phil Steitz
wrote:
On 10/17/13
On 17 Oct 2013, at 18:03, Phil Steitz wrote:
> On 10/17/13 5:52 AM, Christian Grobmeier wrote:
>> On 17 Oct 2013, at 2:39, Henri Yandell wrote:
>>
>>> On Wed, Oct 16, 2013 at 4:59 PM, sebb wrote:
>>>
>>>> On 16 October 2013 12:25, Christian Grobmei
On 17 Oct 2013, at 2:39, Henri Yandell wrote:
On Wed, Oct 16, 2013 at 4:59 PM, sebb wrote:
On 16 October 2013 12:25, Christian Grobmeier
wrote:
If nobody is willing to put a component to "dormant" state, then the
label doesn't make any sense. I would vote to remove the do
On 16 Oct 2013, at 23:14, Mark Thomas wrote:
On 16/10/2013 21:34, Christian Grobmeier wrote:
Now what are you folks expecting? A full-fleshed out plan how to
move? I
think we should
first decide IF we move and that was was happening here.
What I was expecting was decisions to be made on the
On 16 Oct 2013, at 22:46, Phil Steitz wrote:
On 10/16/13 1:34 PM, Christian Grobmeier wrote:
On 14 Oct 2013, at 9:13, Mark Thomas wrote:
Further, if the consensus amongst the active developers on a
component
is that they wish to stick to svn, I see no why that component
should be
forced to
omain Manni-Bucau
Matt Benson
Benedikt Ritter
Bruno Kinoshita
Gary Gregory
Luc Maisonobe
Oliver Heger
Christian Grobmeier
Torsten Curdt
-1s
Mark Thomas
Thomas Vandahl
Damjan Jovanovic
Gilles Sadowski
Jorg Schaible
+0.5
Olivier Lamy
+0
Ralph Goers
-0
Emmanuel Bourg
The vote passes, so Apache Co
On 16 Oct 2013, at 16:28, Gary Gregory wrote:
On Wed, Oct 16, 2013 at 10:05 AM, Christian Grobmeier
wrote:
Maybe I have interpreted the Clirr report wrong. But besides the two
buffer fields it doesn't look so bad (just additions). I believe
these two
fields are acceptable although I under
Hi,
[X] +1 Release these artifacts
On 16 Oct 2013, at 15:20, Gary Gregory wrote:
Thank you Stefan for the new RC.
+1
Maybe I have interpreted the Clirr report wrong. But besides the two
buffer fields it doesn't look so bad (just additions). I believe these
two fields are acceptable althoug
If nobody is willing to put a component to "dormant" state, then the
label doesn't make any sense. I would vote to remove the dormant state
in general.
If we don't have any need of a specific component we can put it to
attic.apache.org too.
No need to duplicate things.
If we don't have a "dorm
On 14 Oct 2013, at 15:34, Emmanuel Bourg wrote:
> Thanks to the infra team we now have JIRA and svn commit notifications
> on the channel. Enjoy :)
boah thats cool! Thanks for organizing that! (assuming oyu did!)
> Emmanuel Bourg
>
>
> Le 10/10/2013 18:15, James Carman a écrit :
>> As a reminde
+1
let's move on step by step.
On 10 Oct 2013, at 16:50, James Carman wrote:
> All,
>
> We have had some great discussions about moving our SCM to Git. I
> think it's time to put it to a vote. So, here we go:
>
> +1 - yes, move to Git
> -1 - no, do not move to Git
>
> The vote will be left ope
Cheers
Christian
On Fri, Oct 11, 2013 at 6:01 AM, Christian Grobmeier
wrote:
+1
I consider this move to happen step by step and see only little risk
if we
start with a single component first.
As the half of the world works with git meanwhile I see less risk in
general too.
On 1
+1
I consider this move to happen step by step and see only little risk if
we start with a single component first.
As the half of the world works with git meanwhile I see less risk in
general too.
On 10 Oct 2013, at 16:41, James Carman wrote:
All,
We have had some great discussions about
On 10 Oct 2013, at 18:43, Jörg Schaible wrote:
> Hi James,
>
> James Carman wrote:
>
>> Sorry, didn't understand your question. The Apache Camel team uses
>> Git and they release maintenance versions all the time (I believe
>> about 3 or 4 at a time sometimes when a bug fix gets merged down).
>>
Here is some commit activity:
http://svnsearch.org/svnsearch/repos/ASF/search?view=plot&from=20130101&to=20131009&path=%2Fcommons%2Fproper&plotsort=%24plotsort
But we should to exclude "typo" fixes and such.
For example:
http://svnsearch.org/svnsearch/repos/ASF/search?view=resultlist&from=201301
On 8 Oct 2013, at 20:07, Benedikt Ritter wrote:
Hey Gary,
you are involved in other projects (like log4j2) how do they do it? Is
it easier to release log4j2 than it is to release for example [lang]?
Check this guide:
http://wiki.apache.org/logging/Log4j2ReleaseGuide
In fact we have an ASF m
On 8 Oct 2013, at 12:48, James Carman wrote:
I think the idea is to change the mindset. There seems to be an
almost
militant desire to maintain compatibility. Yes, we have the version
number
scheme, but some folks just never want to break compatibility it
seems.
This stalls innovation. I do
On 8 Oct 2013, at 11:42, Romain Manni-Bucau wrote:
just an habit. svn diff && attach diff to a jira is as easy/hard as
git
push + PR.
Tools like GitHub succeed because not everybody agrees with you.
svn/diff is stoneage to some. git/pr is the future for them. Maybe you
are right about the h
On 8 Oct 2013, at 6:53, Romain Manni-Bucau wrote:
Hi
Not sure svn is the issue. What makes quality and which rules are
mandatory
is more important IMO.
If you want to attract a new generation it is important. Would you
contribute to a CVS project?
I would if you need it urgently for work.
On 7 Oct 2013, at 13:58, Jochen Wiedmann wrote:
On Mon, Oct 7, 2013 at 1:42 PM, Christian Grobmeier
wrote:
What would be the difference to now?
The difference can be *huge*, emotionally. For example, I felt quite
at
home at the webservices project when working in JaxMe, XML-RPC, or
Axis
On 7 Oct 2013, at 12:58, Jean-Louis MONTEIRO wrote:
Hi Jochen,
Well summarized.
And I think you figured out what the real problem is.
We could work as in Incubator, isn't it?
Having one big umbrella and real subprojects.
What would be the difference to now?
I understand Commons as a project
James,
thank you.
I believe Commons is in a bad shape.
Look at Commons Collections. Before 4 years somebody
said Guava is more modern, he his answer seems to be widely accepted.
http://stackoverflow.com/a/167/690771
This guy said we have no generics. What did we do in the past 4 years?
http
On 6 Oct 2013, at 20:57, Phil Steitz wrote:
> On 10/6/13 11:45 AM, James Carman wrote:
>> Collections 4.x, nuff said
>
> Huh? Didn't we release a beta? We could say the same thing about
> math 4.0, pool/dbcp 2.0, etc. These things are in progress. They
> will get released. There is activity.
On 5 Oct 2013, at 14:29, James Carman wrote:
On Sat, Oct 5, 2013 at 7:03 AM, Benedikt Ritter
wrote:
I'm not sure I agree with all of your points. Yes, the sandbox is a
place to try new ideas out. Does this mean certain quality criterions
do not apply? I don't think so. This all has to be co
I found this in ognl pom:
org.apache.maven.plugins
maven-checkstyle-plugin
2.7
config/maven_checks.xml
config/maven-header.txt
I thought I would remember there is something going on with these
m
I found 11 uses of e.printStackTrace and think its pretty bad.
Including OgnlException overwrites printStackTrace and writes to
System.err for some reason.
In addition there are a lot of System.out's, but those are all commented
and seem to have served debugging purposes.
I believe small libs lik
Please note, there was code in ognl.ASTMap to support jdk1.3.
Considering maven aims at jdk 5, i removed this code.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.a
/mauriziocucchiara
> VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara
>
> Maurizio Cucchiara
>
>
> On 26 March 2013 09:53, Lukasz Lenart wrote:
>> 2013/3/26 Christian Grobmeier :
>>> +1, go for it.
>>> Now its time to see if our te
On Tue, Mar 26, 2013 at 9:53 AM, Lukasz Lenart wrote:
> 2013/3/26 Christian Grobmeier :
>> +1, go for it.
>> Now its time to see if our testcases are good.
>
> They are, I made a slight mistake and tests showed that :-)
>
>> I also think we should test it in conju
ing to remove two deprecated classes right now.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2013/3/8 Christian Grobmeier :
>>> On Wed, Mar 6, 2013 at 10:11 AM, sebb wrote:
>>>> On 6 March 2013 06
>> On Wed, Mar 20, 2013 at 8:53 PM, Benedikt Ritter
>> wrote:
>> >> +/**
>> >> + * Returns an iterator over the values of this record.
> Iterable.iterator() doc is:
>
> "Returns an iterator over a set of elements of type T."
>
> I thought it would be nice to tweak this a bit to match a CS
On Wed, Mar 20, 2013 at 8:53 PM, Benedikt Ritter wrote:
>> +/**
>> + * Returns an iterator over the values of this record.
>> + *
>> + * @return an iterator over the values of this record.
>> + */
>>
>
> I had no better idea how to comment this. Any suggestions how to make this
Should we move to the AdminGroups with this wiki too?
I think yes
On Wed, Mar 20, 2013 at 2:37 PM, Apache Wiki wrote:
> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Commons Wiki" for
> change notification.
>
> The "MarlaQuin" page has been changed by MarlaQuin:
> h
On Sat, Mar 9, 2013 at 10:00 AM, sebb wrote:
> On 9 March 2013 00:39, Ralph Goers wrote:
>> I'm not sure I understand what the big deal is. Sebb vetoed a commit and
>> identified exactly what needed to be changed for him to remove the veto. If
>> the requested change is made then all should b
On Wed, Mar 6, 2013 at 10:11 AM, sebb wrote:
> On 6 March 2013 06:49, Lukasz Lenart wrote:
>> Hi,
>>
>> I was checking out what should be solved before releasing a new
>> version and in my opinion most of PMD [1] errors can be omitted, maybe
>> "These nested if statements could be combined" shoul
On Wed, Mar 6, 2013 at 1:01 PM, Gary Gregory wrote:
> Strictly speaking, you do not need his permission AFAIK. IOW, don't bother
> sending ME an email to tell me you'll moving my @author to pom.xml ;)
Out of interest, are you sure there is no permission needed? I am
thinking on another project wh
+1... jdk1.3...
On Tue, Mar 5, 2013 at 4:34 PM, Simone Tripodi wrote:
> Just for the record: I don't intend to do a major rewrite ATM, just
> update and bugfix.
>
> best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripo
On Tue, Jan 15, 2013 at 7:47 PM, Dennis Lundberg wrote:
> On 2013-01-13 19:14, t...@apache.org wrote:
>> Author: tn
>> Date: Sun Jan 13 18:14:24 2013
>> New Revision: 1432688
>>
>> URL: http://svn.apache.org/viewvc?rev=1432688&view=rev
>> Log:
>> Upgrade test dependencies: log4j 1.2.17, avalong-fr
On Tue, Jan 15, 2013 at 7:43 PM, Thomas Neidhart
wrote:
>> I'm -1 on this change. I don't see any reason to do it. We don't need
>> features from a more recent Java version in commons-logging. As others
>> have said: most users of commons-logging are old and older apps.
>
> In general I am fine wi
On Sat, Jan 12, 2013 at 8:49 PM, Mark Thomas wrote:
> On 12/01/2013 19:29, Christian Grobmeier wrote:
>> On Sat, Jan 12, 2013 at 8:27 PM, Mark Thomas wrote:
>>> On 12/01/2013 17:36, Christian Grobmeier wrote:
>>>
>>>> Basically I am +1 on moving to
On Sat, Jan 12, 2013 at 8:27 PM, Mark Thomas wrote:
> On 12/01/2013 17:36, Christian Grobmeier wrote:
>
>> Basically I am +1 on moving to newer JDKs. But in this case I just see
>> use for old and older applications.
>> That said, I just checked and saw tomcat is sti
On Sat, Jan 12, 2013 at 6:26 PM, Thomas Neidhart
wrote:
> On 01/12/2013 05:37 PM, Christian Grobmeier wrote:
>> On Sat, Jan 12, 2013 at 3:03 PM, Thomas Neidhart
>> wrote:
>>> Hi,
>>>
>>> I would like to do a similar cleanup as for email also for lo
On Sat, Jan 12, 2013 at 3:03 PM, Thomas Neidhart
wrote:
> Hi,
>
> I would like to do a similar cleanup as for email also for logging and
> aim for a 1.2 release in the coming weeks. The things I have in mind:
>
> * update to Java 5
> * comply to default maven structure
> * update to Junit 4
>
> Do you know how to exclude some files/directories from the rat-plugin
> scan ? Right now it includes .idea folder in the scan which produces
> mass of errors :\
have not tried yet, but it supports an "exclude" option in the configuration:
http://creadur.apache.org/rat/apache-rat-plugin/rat-mojo.
On Tue, Jan 8, 2013 at 7:44 AM, Lukasz Lenart wrote:
> Another issue, I've noticed that the parent is defined as 28-SNAPSHOT,
> should it be simple 27 - the latest released version?
Not sure about the differences of these 2, but I think we cannot
release a stable version with a dependency to a -S
Hi folks,
before 2 or 3 months we have voted to let BeanShell come to Commons.
There is this page:
http://wiki.apache.org/incubator/BeanShellProposal
But there was never a vote on the incubator list. Nor did I see any
sign of life from the original authors. Actually it seems to me this
project i
d the new repo with the "old" content. But I
>>> don't get why that has to be the case; because if it is, we are in
>>> worse shape than Christian suggests - come Jan 1 we will be dark if
>>> we don't get everything moved to svn pub-sub.
>>&g
e in
>> worse shape than Christian suggests - come Jan 1 we will be dark if
>> we don't get everything moved to svn pub-sub.
>>
>> Sorry if above is naive. The intent is to avoid a huge amount of
>> fiddling in a short period of time when quite a few component si
h from
commons.apache.org to the new site
> Gary
>
> On Dec 10, 2012, at 7:13, Christian Grobmeier wrote:
>
>> On Mon, Dec 10, 2012 at 1:07 PM, Gary Gregory wrote:
>>> Bah, let's pick one component and start there and skip a test site.
>>
>> But then
On Mon, Dec 10, 2012 at 1:07 PM, Gary Gregory wrote:
> Bah, let's pick one component and start there and skip a test site.
But then there is only one component visible under the new commons.a.o?
> Gary
>
> On Dec 10, 2012, at 3:08, Christian Grobmeier wrote:
>
>> star
starting from 1. January. Just saw a final reminder from Infra.
Commons is surely a LOT of work.
I would like to suggest we act immediately.
In other terms: let us request a commons-test cms where we can try things
out and prepare the new sites.
As Ralph Goers has already mentioned, we have a s
On Thu, Nov 15, 2012 at 8:25 AM, Ralph Goers wrote:
>
> On Nov 14, 2012, at 2:03 PM, Ted Dunning wrote:
>
>> On Wed, Nov 14, 2012 at 1:53 PM, Olivier Lamy wrote:
>>
>>> 2012/11/14 Thomas Vandahl :
On 14.11.2012 08:40, Luc Maisonobe wrote:
>
> Please, could someone who knows what to d
Hi,
I am there too! (referring to ApacheCon EU)
Cheers
On Tue, Sep 18, 2012 at 9:29 PM, Thomas Neidhart
wrote:
> Hi,
>
> does anybody plan to go to ApacheCon 2012?
> Would be nice to meet each other there.
>
> Thomas
>
> -
> T
Hi,
and just to say it clearly: i am very much +1 to finally add this skin.
Cheers
Christian
On Fri, Aug 31, 2012 at 11:09 AM, Simone Tripodi
wrote:
> Hi again,
>
> Thanks to Christian Grobmeier, we also added the responsive bootstrap css.
>
> I re-uploaded the site, can you ple
On Thu, Aug 30, 2012 at 4:13 PM, Luc Maisonobe wrote:
> Le 30/08/2012 15:52, Simone Tripodi a écrit :
>> Hi all guys,
>>
>> new Apache Maven Fluido Skin is gonna be released soon, I started
>> experimenting locally how the _main_ commons site would look alike if
>> the new skin would be applied (w
On Wed, Aug 8, 2012 at 5:38 PM, Sébastien Brisard
wrote:
>>> Does that mean that porting it into Commons-Math is possible
>>> (license-wise?). I would think it does…
>>
>> That seems explicitly restrictive to me. e.g. If I don't claim to be in the
>> general scientific community, the software h
On Wed, Jun 27, 2012 at 1:50 AM, sebb wrote:
> On 26 June 2012 22:50, sebb wrote:
>> Some new SANSELAN JIRAs have just been raised, however the JIRA was
>> renamed to IMAGING.
>>
>> Looks like something is wrong with JIRA; I'll raise an Infra issue.
>
> https://issues.apache.org/jira/browse/INFRA
> However, as already mentioned on the respository mailing list, the
> .asc has been restored to the staging directory, so it should now be
> possible to release the full set of files.
I saw the mail from infra, but he mentioned the checksum is not
correct or something like that. Or am I wrong? we
On Tue, Jun 19, 2012 at 6:25 PM, sebb wrote:
> On 19 June 2012 16:30, Christian Grobmeier wrote:
>> On Tue, Jun 19, 2012 at 4:59 PM, sebb wrote:
>>> On 19 June 2012 13:05, Christian Grobmeier wrote:
>>>> On Tue, Jun 19, 2012 at 1:56 PM, Gary Gregory
>>>
On Tue, Jun 19, 2012 at 4:59 PM, sebb wrote:
> On 19 June 2012 13:05, Christian Grobmeier wrote:
>> On Tue, Jun 19, 2012 at 1:56 PM, Gary Gregory wrote:
>>> On Tue, Jun 19, 2012 at 7:42 AM, Jochen Wiedmann
>>> wrote:
>>>
>>>> On Tue, J
On Tue, Jun 19, 2012 at 1:56 PM, Gary Gregory wrote:
> On Tue, Jun 19, 2012 at 7:42 AM, Jochen Wiedmann
> wrote:
>
>> On Tue, Jun 19, 2012 at 1:35 PM, Gary Gregory
>> wrote:
>> > Commons-IO 2.4 has not made it to a Maven repo yet. I am working on it...
>>
>> Any problems, you could use help with?
On Mon, Jun 18, 2012 at 12:47 PM, Łukasz Lenart
wrote:
> Finally, the old issues from OpenSymphony were imported :-)
You are a true hero and i am impressed by your patience!
Thank you so much for following this issue for so long time. I would
have done a simple copy, but your solution is much be
On Sat, Jun 9, 2012 at 2:26 PM, Gary Gregory wrote:
> If sonar for snapshots on a.a.o replaces POM requested reports instead
> of complementing them, you loose the ability to analyze before
> committing, surely something we do not want.
you can use:
mvn sonar:sonar
before you commit, which should
On Sun, Jun 3, 2012 at 5:59 PM, Gary Gregory wrote:
> I would rather we eat our own dog food with log4j or commons logging.
As classscan is in sandbox... I think it would help the logging team
if we would try log4j 2.0 alpha. It is a great framework already and
logging-people could learn about pr
+1
On Tue, May 22, 2012 at 9:00 AM, Stefan Bodewig wrote:
> Hi all,
>
> I'd like to release Compress 1.4.1.
>
> Compress 1.4.1 RC1 is available for review here:
> http://people.apache.org/~bodewig/cc/
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/org
On Sun, May 20, 2012 at 12:43 AM, James Carman
wrote:
> Perhaps classscan? :)
makes perfect sense to me :-)
>
> On Sat, May 19, 2012 at 5:38 PM, Christian Grobmeier
> wrote:
>> On May 19, 2012 10:13 PM, "Gary Gregory" wrote:
>>>
>>> A one c
> > If we propose to switch one component first, I would be happy to
> > volunteer for switching [math]. What do other developers think about
> > Jochen idea ?
> >
> > Luc
> >
> >>
> >> Thanks,
> >>
> >> Jochen
> >>
> &g
Its still in development.
I have asked to switch to git with log4php before a few weeks and the
answer was it is possible, if one of us gets involved in the
git@apache project. I assume it is the the here. Its definitely not GA
at the moment.
On Wed, May 16, 2012 at 9:39 AM, Jochen Wiedmann
wrot
I read the thread and thought BeanShell would fit to Commons... I
think there are only a few committers.
OGNL is in the same vein too. I would oppose if the BS developers are
not willing to continue the project here. This is not very likely the
case here
Cheers,
Christian
On Mon, Apr 2, 2012 at 6
On Sun, Apr 1, 2012 at 7:01 AM, Stefan Bodewig wrote:
> On 2012-03-31, Christian Grobmeier wrote:
>
>> Before ages when I wrote the "ChangeSet" stuff I have marked them as
>> "experimental". Have not heard any complains yet... we should discuss
>>
1 - 100 of 555 matches
Mail list logo
