Great!
The key change here for 1.7.4 is the way the appcfg.{sh|cmd} tool finds a
javac compiler to compile the generated classes from JSP files.
Eclipse a bit complex to configure:
- there is a JVM used by Eclipse
- there is potentially a JRE/JDK configured to be used by your app engine
project
- there is potentially a JRE/JDK used by an Eclipse spawed process to run
the appcfg tool.
In this case, I think the last one was a JRE instead of a JDK.
We are updating the error message to be more clear.
The good news is that the JSP compilation phase has been dramatically
improved: it is must faster now if you have many JSPs to precompile.
Thanks.
On Monday, December 10, 2012 9:30:34 AM UTC-8, Savaş L. wrote:
>
> i tried to reproduce the error i get, on a fresh eclipse and jdk
> install with an empty project.
> there was no error, and worked well.
>
> 1.7.4 seems more strict to match/find a jdk version that is same for
> both eclipse, eclipse project, and appcfg tool.
>
> the steps i took to make my original project work:
> - i clean the WEB-INF/classes folder for my project
> - i made a clean install of jdk
> - i wrote a constant -vm path in eclipse.ini to make eclipse force to
> use specified jdk version
> - i added new jdk to path & system variable table of win 7
> - i changed munjutaglib.java to something another like munjutags.java
>
> and problems gone, i could able to deploy with 1.7.4
> thanks to Ludo, to show me a way for the solution.
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/Pm3fvRdBtfQJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
