Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=23998&projectId=166
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 20 Nov 2007 20:33:05 -0800
Finished at: Tue 20 Nov 2007 20:33:23 -0800
Total time: 17s
Build Trigger: Schedule
Build Nu
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=23998&projectId=166
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 20 Nov 2007 20:33:05 -0800
Finished at: Tue 20 Nov 2007 20:33:23 -0800
Total time: 17s
Build Trigger: Schedule
Build Nu
On 20/11/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> sebb wrote:
> > On 19/11/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >> Rahul Akolkar wrote:
> >>> On 11/19/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> sebb wrote:
> >>>
> > There does not seem to have been a final de
What you want to do is find ones that aren't listed in the downloads.xml.
Ones that are in there should stay, ones that aren't should go away.
Hen
On Nov 19, 2007 9:49 AM, sebb <[EMAIL PROTECTED]> wrote:
> There seem to be quite a few old releases in various commons directories.
>
> I think thes
On Nov 18, 2007 6:56 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> On 11/18/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > On Nov 17, 2007 9:39 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > > On 11/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > > Author: niallp
> > > > Date: Sat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
For the records: Here is my +1.
Oliver
Oliver Heger wrote:
Here is the 3rd (and hopefully last) attempt for the release vote for
Commons Configuration 1.5.
The artifacts of the release candidate can be found at
http://people.apache.org/~oheger/commons-configuration-1.5rc3/
The site is availa
sebb wrote:
On 19/11/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Rahul Akolkar wrote:
On 11/19/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
sebb wrote:
There does not seem to have been a final decision (or even summary) of
the e-mail thread, which is a pity. Probably ought to be on t
Niall Pemberton wrote:
On Nov 19, 2007 10:31 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Three things:
1. Why change the versioning scheme for the skin? ( 1.1-SNAP -> 2-SNAP )
Do you feel that it is more like a parent pom than a component? The
skins that are maintained by the Maven project u
On 11/20/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Jörg Schaible wrote:
> > Since the JUL loggers sit in the system class path, any formatter
> > implementation *must* be available also in the system class path.
>
> Isn't this part of what JULI fixes?
>
>From the tomcat docs, looks like yes
Jörg Schaible wrote:
> Since the JUL loggers sit in the system class path, any formatter
> implementation *must* be available also in the system class path.
Isn't this part of what JULI fixes?
--- Noel
-
To unsubscribe
On Nov 19, 2007 11:18 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On Nov 19, 2007 10:31 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > Three things:
> >
> > 1. Why change the versioning scheme for the skin? ( 1.1-SNAP -> 2-SNAP )
> > Do you feel that it is more like a parent pom than a com
On Nov 20, 2007 2:30 AM, Jörg Schaible
<[EMAIL PROTECTED]> wrote:
> Phil Steitz wrote:
> > On Nov 19, 2007 11:46 PM, Jörg Schaible
> > <[EMAIL PROTECTED]> wrote:
> >>
> >> Phil Steitz wrote:
> [snip]
> >>> Any other comments on the naming, levels, use of JUL before I start?
> >>
> >> Why not using
> I'm also interested in helping, and have contributed a few patches.
> Unfortunately, as Stephen indicated, because there aren't many
> interested committers, patches tend to languish for a while before
> anyone has time to look at them. A few weeks ago, someone looked at
> the patch I submitted
I'm also interested in helping, and have contributed a few patches.
Unfortunately, as Stephen indicated, because there aren't many
interested committers, patches tend to languish for a while before
anyone has time to look at them. A few weeks ago, someone looked at
the patch I submitted
> Tickets and patches - see
> https://issues.apache.org/jira/browse/COLLECTIONS/fixforversion/12312131.
>
> Thanks for the interest - look forward to your input. Apologies in
> advance for the speed ... I'm the only real committer at the moment, and
> do not have much time to spare - however, I am
Phil Steitz wrote:
> On Nov 19, 2007 11:46 PM, Jörg Schaible
> <[EMAIL PROTECTED]> wrote:
>>
>> Phil Steitz wrote:
[snip]
>>> Any other comments on the naming, levels, use of JUL before I start?
>>
>> Why not using commons-logging? It supports trace level. JUL
> is really a pain. It is applicable
17 matches
Mail list logo
