On Sat, 2005-10-01 at 22:13 +0200, Joerg Hohwiller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Simon,
>
> Simon Kitching wrote:
> > On Sat, 2005-10-01 at 02:47 +0200, Joerg Hohwiller wrote:
> >
> >>As I have checked with offical releases ant seems
> >>to be the master and mav
On Fri, 2005-09-30 at 22:22 +0200, Joerg Hohwiller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jörg Schaible wrote:
> > Hi Jörg,
> Hi,
> >
> > Joerg Hohwiller wrote on Thursday, September 29, 2005 10:21 PM:
> >
> > [snip]
> >
> >>But none of the individual tests failed (see bel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Simon,
Simon Kitching wrote:
> On Sat, 2005-10-01 at 02:47 +0200, Joerg Hohwiller wrote:
>
>>As I have checked with offical releases ant seems
>>to be the master and maven is just there for other reasons (maybe the site
>>generation).
>
>
> Yes,
On Sat, 2005-10-01 at 02:47 +0200, Joerg Hohwiller wrote:
> As I have checked with offical releases ant seems
> to be the master and maven is just there for other reasons (maybe the site
> generation).
Yes, this is the case.
Up until now, commons-logging has always been built with Ant, with Mave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
> [snip]
> So I will adopt the build-process so the AbstractLogger will be included in
> the
> API jar. I suppose I have to do this in the ant and in the maven build
> configuration.
> [snip]
Just to point this out: the API jar already conta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I debugged deep into and found the problem:
The testcase seems to create an own classloader and load the minimal classes
(jcl-api and -tests) for the test with that. Next it tries to get the Logger
instance via the LogFactory. Since it is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg Schaible wrote:
> Hi Jörg,
Hi,
>
> Joerg Hohwiller wrote on Thursday, September 29, 2005 10:21 PM:
>
> [snip]
>
>>But none of the individual tests failed (see below).
>
>
> [snip]
>
>
>>[junit] Tests run: 7, Failures: 2, Errors: 0, Time
Hi Jörg,
Joerg Hohwiller wrote on Thursday, September 29, 2005 10:21 PM:
[snip]
>
> But none of the individual tests failed (see below).
[snip]
> [junit] Tests run: 7, Failures: 2, Errors: 0, Time
> elapsed: 0,06 sec
[snip]
Seems, there are two ... :)
- Jörg
---