cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <vadim.gritse...@verizon.net>
Subject Re: [Proposal] Splitting JDK dependent code [was: Re: Javac task design problems]
Date Tue, 25 Feb 2003 15:19:49 GMT
Carsten Ziegeler wrote:

>One solution to avoid filtering our java-code because of jdk-dependencies
>is to separate this code into different source directories.
>For example for the databases block that uses ant filtering we could
>generate three directories:
>blocks/databases/java - the common code
>blocks/databases/java1.2 - the AbstractEqslConnection.java for JDK 1.2/1.3
>

I think that because Avalon (IIRC) could not be run under 1.2, and 
because 1.3 almost (99.9%) everywhere available (see POLL), we should 
write simply 1.3 and do not mention 1.2 anymore.


>blocks/databases/java1.4 - the AbstractEqslConnection.java for JDK 1.4 and
>above
>
>This is then similar to our libs directory.
>
>This solution would not only remove the need of filtering but would also
>make the source directly usable within your favorite IDE.
>

OTOH, it will increase maintanence - you have to maintain two copies...

Vadim



>What do you think?
>  
>
>Carsten
>
>Carsten Ziegeler
>Open Source Group, S&N AG
>



Mime
View raw message