Stefano Mazzocchi wrote:
Torsten Curdt wrote:
As you say: that one is excalibur related. But Berin already fixed that
one [1] But AFAIK it's not yet even checked in and thereby far away
from
being relased. IIRC we wanted to go with release versions only - right?
A very big temptation though :-
Carsten Ziegeler wrote:
Torsten Curdt wrote:
Hurray!
By using composition rather than inherritance I removed the
the dependency to the jvm. No split code anymore :)
Thanks for pointing me on that Berin.
Everything *should* work as before. And at least on
my machine the samples are working.
Pleas
Torsten Curdt wrote:
As you say: that one is excalibur related. But Berin already fixed that
one [1] But AFAIK it's not yet even checked in and thereby far away from
being relased. IIRC we wanted to go with release versions only - right?
A very big temptation though :-/
If Avalon is not confide
On 20.Mar.2003 -- 11:09 PM, Torsten Curdt wrote:
> Hurray!
>
> By using composition rather than inherritance I removed the
> the dependency to the jvm. No split code anymore :)
Kool!
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7
As you say: that one is excalibur related. But Berin already fixed that
one [1] But AFAIK it's not yet even checked in and thereby far away from
being relased. IIRC we wanted to go with release versions only - right?
A very big temptation though :-/
If Avalon is not confident enough to release i
Torsten Curdt wrote:
But we currently have the dependency to the split excalibur datasource
package. So we can't remove the dependency from the build system
right now, right?
As you say: that one is excalibur related. But Berin already fixed that
one [1] But AFAIK it's not yet even checked in an
Great! Thanks!
Just one question:
But we currently have the dependency to the split excalibur datasource
package. So we can't remove the dependency from the build system
right now, right?
As you say: that one is excalibur related. But Berin already fixed that
one [1] But AFAIK it's not yet even
Torsten Curdt wrote:
> Hurray!
>
> By using composition rather than inherritance I removed the
> the dependency to the jvm. No split code anymore :)
>
> Thanks for pointing me on that Berin.
>
> Everything *should* work as before. And at least on
> my machine the samples are working.
>
> Please
Torsten Curdt wrote:
> Hurray!
>
> By using composition rather than inherritance I removed the
> the dependency to the jvm. No split code anymore :)
>
> Thanks for pointing me on that Berin.
>
> Everything *should* work as before. And at least on
> my machine the samples are working.
>
> Please
ups.. I meant "dependent" ;)
--
Torsten
Hurray!
By using composition rather than inherritance I removed the
the dependency to the jvm. No split code anymore :)
Thanks for pointing me on that Berin.
Everything *should* work as before. And at least on
my machine the samples are working.
Please test!
cheers
--
Torsten
11 matches
Mail list logo