On 5/4/2010 12:51 AM, P T Withington wrote:
Sounds right.
Ok, then I'll change the sources.
I am no ant wizard, so these kinds of oversights are probably my fault. Some day we should go even further and update our JavaCC so we don't need to compile the output as 1.4 Java.
I've run some test with newer JavaCC versions (4.2, 3.2, 3.1) and only with 3.1 it was possible to complete the 'preloader' and 'lfcs' ant targets in WEB-INF/lps/lfc/build.xml. JavaCC 3.2 failed when running 'lfcs', with 4.2 it wasn't even possible to complete 'preloader'.
Unfortunately, version 3.2 was the first version with Java5 support.
On 2010-05-03, at 18:42, André Bargull wrote:The generated CSS-Parser files are placed into org/openlaszlo/css, shouldn't they get into org/openlaszlo/css/parser? From the ant target: --- <target name="css-parser" depends="init" unless="css-parser.uptodate" description="Run JavaCC to create the css-parser *.java files."> <mkdir dir="${buildsrc.1.4}/${pkg.css.parser}"/> <javacc target="${src}/${pkg.css}/CSSParser.jj" outputdirectory="${buildsrc.1.4}/${pkg.css}/" javacchome="${JAVACC_HOME}" /> </target> --- The ant target creates the org/openlaszlo/css/parser directory, but all generated class files are placed into org/openlaszlo/css. This seems to be wrong somehow. Making this a bit more consistent would be nice...
