[news.eclipse.newcomer] Re: Installed 3.3, lost XML editor

[Michel Gutierrez <michel.gutierrezNOSPAM@xxxxxxxxx>]

Well, setting up Cocoon to work within eclipse is not an easy task and 
requires that you compile cocoon outside of Eclipse (while running it 
from Eclipse). And for some reasons, compiling cocoon with 1.6 did not 
succeed (i don't remember the exact error), while the same compilation 
under 1.4 did work without any problem. I could certainly have compiled 
Cocoon on 1.4 and run it on 1.6, but i didn't think of this soon enough 
and now java 1.6 refuses to install again on my system with an error 
message saying that an unexpected error occured and i should contact my 
vendor :( I'm a linux guy and debugging that kind of issue on Windows is 
really a pain for me !

I agree that there must be ways to configure properly both Eclipse and 
Cocoon to run with 1.6, but i already spent too much time setting up my 
environment and i took the decision - shame on me ! - to focus on my 
customer's project rather than the environment and i don't have the 
feeling to have lost much reverting to Eclipse 3.2.

/mig

Eric Rizzo wrote:
> Michel Gutierrez wrote:
> > That's it !
> >
> > I had to switch back to java 1.4 because Apache Cocoon does not 
> > compile on java 5.
> >
> > Will i be able to use eclipse 3.2 (+WTP and XML editor !) with Java 1.4 ?
>
> As Ed says, there is no reason to run Eclipse on 1.4 just because a 
> project you want to build does not need/work with it. Just set up that 
> one project to use 1.4.
> Still, I'd like to hear more about Apache Cocoon not compiling with Java 
> 5. All Java releases are supposed to be backwards compatible; there's 
> nothing that should prevent code not written for JDK 1.5 from compiling 
> in it.
>
> Eric