cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [Proposal] Splitting JDK dependent code [was: Re: Javac task design problems]
Date Tue, 25 Feb 2003 16:22:25 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
> 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.
> 
> What do you think?

big +1!

The code filtering problem is suggesting me that preprocessing source 
code is a very bad habit and we should try to avoid it alltogether!

That should turn Constants.java in a property file that Cocoon reads out 
of its own jar file when it starts.

Thoughts?

-- 
Stefano Mazzocchi                               <stefano@apache.org>
    Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------



Mime
View raw message