Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <19857.195.226.6.75.1096905234.squirrel@195.226.6.75>
In-Reply-To: <200410041203.i94C33pg019884@ags01.agsoftware.dnsalias.com>
References: <16128.195.226.6.75.1096890382.squirrel@195.226.6.75>
    <200410041203.i94C33pg019884@ags01.agsoftware.dnsalias.com>
Date: Mon, 4 Oct 2004 09:53:54 -0600 (CST)
Subject: RE: Compile errors with 2.1.x
From: "Antonio Gallardo" <agallardo@agssa.net>
To: dev@cocoon.apache.org
User-Agent: SquirrelMail/1.4.3a-1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

Carsten Ziegeler dijo:
> Antonio Gallardo wrote:
>> I think in this "special" case we can remove the jisp
>> support. Remember there were problems using jisp. So, I think
>> even users using deprecated stuff should avoid using jisp, if
>> they expect stability. And at least, we cannot also update
>> the jar because of the new GPL. Then we have only 2
>> options:
>>
>> 1-Stay with the buggy code, even when we know about that or...
>> 2-Remove the buggy code. Currently, we have 2 new cache solutions.
>>
>> I will prefer (2).
>>
>> Do you think we need a vote for that? Or to request users
>> feedback (in users mailist)?
>>
> No, I don't think we need a vote - just do what you think is best :)
> But I agree, that we can remove the code in this case - we too many
> cache solutions anyway.

Thanks for the answer. I will try to solve that today.. I hope it would
not be too dificult... ;-)

BTW, Remember I owe you 3 beers! I expect to pay you in Ghent! :-D

Best Regards,

Antonio Gallardo

>
> Carsten
>