Ok,
editing conf/web.xml and adding compiler=modern does not change anything.
"modern" is extracted from tomcat 7 & ant documentation
https://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html#Introduction
https://ant.apache.org/manual/Tasks/javac.html
(extract from vanilla conf/web.xml, see com
On 27/09/2016 10:50, agharta wrote:
> Hi,
> Thanks for reply.
>
> This could be a nice test to do. And i do it :-)
>
> Sorry my poor skill, how to set Jasper to use javac?
> And vice-versa, how to set ant to use Eclipse?
Jasper to use javac:
- set the compiler init parameter in $CATALINA_BASE/co
Hi,
Thanks for reply.
This could be a nice test to do. And i do it :-)
Sorry my poor skill, how to set Jasper to use javac?
And vice-versa, how to set ant to use Eclipse?
Thanks a lot,
Best regards,
Agharta
On 09/27/2016 11:45 AM, Mark Thomas wrote:
On 27/09/2016 09:58, agharta wrote:
So
On 27/09/2016 09:58, agharta wrote:
> So, errors comes up only at runtime compilation. Why?
Compiler differences. Pre-compilation uses Javac. Runtime compilation
uses the compiler from Eclipse (by default).
Another option to consider would be to run Tomcat on a JDK and configure
Jasper to compi
Another take,
Doing a pre jsp compilation via ant task, jasper2 gives me no jsp error
(only warnings).
Here the netbeans integration (adapted from
https://tomcat.apache.org/tomcat-7.0-doc/jasper-howto.html#Web_Application_Compilation
).
Forced absolute tomcat path.
file="/home/agharta/ne
Hi, sorry to borrow you, don't hate me.
One question: will this implementation breaks 7.0 tree compatibilityor not?
Let me explain:
from 7.0.1 to 7.0.70 any Tomcat upgrade is backward compatible ( for my
requirements).
Any upgrade means a simple drop in war in webapps folder, for me.
Now
Ah,
Sorry i had not found it.
My mistake.
Cheers,
Agharta
Il 26 settembre 2016 17:37:03 CEST, Mark Thomas ha scritto:
>On 26/09/2016 16:32, agharta wrote:
>
>
>
>> I've searched cause on tomcat official changelog between .70 and .72
>but
>> without success.
>>
>>
>> So the question is: why?
>
On 26/09/2016 16:32, agharta wrote:
> I've searched cause on tomcat official changelog between .70 and .72 but
> without success.
>
>
> So the question is: why?
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
The same error handling changes are in 7.0.72.
Mark
