IDP, pre-compiling jsp's

[Steven Carmody]

On 7/12/14 5:41 PM, Ian Young wrote:
>> I don't see anything in the pom file that looks like a java
>> version property.
>
> Try adding something like this to the <properties> element at the
> top
of your POM file:
>
>          <maven.compiler.source>1.7</maven.compiler.source>
>          <maven.compiler.target>1.7</maven.compiler.target>
>
> See if that changes things.
>

Thanks, Ian. I tried that; unfortunately, it didn't change the result. 
Looking at the age, and the version of the plugin I've tried using (ie 
2.0-alpha-3), I fear that it should be considered petrified. Sigh.

I've found another approach, and its doing better. This plugin (JspC):

https://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/jasper/JspC.html

manages to compile the JSP files and produce java. Its an ant task, so I 
have to use maven-antrun-plugin to actually run it. But, it does compile 
the jsp's into java.

Couple of problems, tho:

1) this plugin doesn't seem to produce any output to the console. Any 
ideas on how to make that happen ?

2) this plugin takes invalid input and copies it to the output java 
file. I added the string "THIS WILL FAIL ON COMPILE" into the middle of 
the javascript, and jspc copied this to the java file it created.

Perhaps jspc placed an error in its output, if I could find that (see #1 
above)

The JspC.html page includes a long list of Fields -- should I add some 
relevant items from that list to the jasper element in my pom.xml ? ( eg 
failOnError, some other item ) ?

Thanks for your patience.