It seems to me that I saw a not about compiling either Cocoon or Lenya
with Eclipse that pointed out that you need to set source compliance to
1.4 when compiling with 1.5. Probably to avoid the kind of problems that
you are having.
enum became a reserved word in 1.5.
Ron
Ray Allis wrote:
cocoon-2.1_20050804161305.tar.gz
... still !? fails with "... conflicts with ..."
I changed init-build.xml in two places from 1.3 to 1.5, and started
the build.
Compiling 268 source files to
/export/home/ray/cocoon-2.1/build/cocoon-2.2.0-dev/blocks/forms/dest
/export/home/ray/cocoon-2.1/src/blocks/forms/java/org/apache/cocoon/forms/event/ProcessingPhase.java:22:
as of release 1.5, 'enum' is a keyword, and may not be used as an
identifier
(try -source 1.4 or lower to use 'enum' as an identifier)
import org.apache.commons.lang.enum.ValuedEnum;
^
1 error
BUILD FAILED
--
so I stopped to ask "If the java source in the snapshot does not
compile / has never been changed, is it the incorrect source?"
Should I get bleeding-edge cocoon from somewhere else?
Ray Allis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
