cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: [HEADS-UP] Cocoon 2.2 and java 1.5 revisited.
Date Mon, 09 Oct 2006 06:30:23 GMT
1. I don't see the point. There was a -1 that is unlikely to be changed.
2. Since we will be distributing binaries with Maven - I would think 
that as long as all the Cocoon components are compiled with JDK 1.4 and 
none of the core dependencies require more than that that things should 
be OK.  A Cocoon user who is OK with Java 5 is certainly free to use 
Qdox 1.6 (or whatever) in their build and at runtime - assuming, of 
course, that the component in question has maintained binary compatibility.


Antonio Gallardo wrote:
> Hi:
> I was updating some jars for cocoon 2.1.0. Qdox[1] version 1.6 was 
> released in August 2006 (we are using now qdox 1.5) and it is 
> distributed only for java 1.5! I know qdox is not the most used block, 
> but it rings a bell!
> Cocoon 2.2 is not released and we will start to find such cases more 
> often than what we would like to believe. I mean we will have more 
> compatibility problems with other libraries that will being released 
> for java  1.5. It means we will have serious problems updating, it 
> will be a serious pain updating them. Also, we should take into 
> account that java 1.6 is just around the corner. So I will be glad if 
> given this fact, we should reconsider to set 1.5 as the minimal 
> version for cocoon 2.2.
> Another fact: we claim cocoon 2.1 is java 1.3 compatible, but in 
> practice, we have some blocks that don't work with java 1.3. Some of 
> them even break the compilation and the user needs to start excluding 
> this blocks. This is our current situation. Have we plans to repeat 
> this for cocoon 2.2 for 1.4 vs. 1.5 o 1.6?
> Given this facts, I ask you: Should we call for a new votation about 
> the minimal java version for cocoon 2.2?
> Best Regards,
> Antonio Gallardo.
> [1]

View raw message