Has anyone meet the following issue?
The file {module:secure}/app/controllers/PaxHeader/Secure.java could
not be compiled. Error raised is : Syntax error on tokens, delete
these tokens
If you open the Secure class found in the /app/controllers/PaxHeader in an IDE, does it compile?
What if you run play auto-test? does it also fail due to compilation errors?
What if you re-download the Play framework (and adjust your PATH environment variable to point to that new Play Framework distribution) and try again?
Related
dart2js error with dash_chat
One of our existing applications makes use of dash_chat, which is working on a V2, however, v2 has a fraction of the APIs implemented. The project is somewhat dormant so today we just doing housekeeping and trying to keep the project up-to-date.
I am now getting this error, and sadly I went and updated all packages and we are using FLutter 3 and Dart 2.17 in all our other projects.
Target dart2js failed: Exception: Warning: The 'dart2js' entrypoint script is deprecated, please use 'dart compile js' instead.
So not sure which of the many things I changed is ultimately the cause of this issue, which crops up when trying to build for web.
No relevant issues on the DC repo and google is being very unhelpful on this one, was hoping someone had some insight that would allow me to take the correct steps forward (or back if need be) to get around this.
TIA
I'm trying to run a simple play-scala example, but I've some problem launching activator because I have a lot of connection timeout. I've only created the application with activator and tried to launch it. No development or custom configuration. I'm using play 2.4.2.
It seems that many of the dependencies that it tries to resolve do not exist: if I try to open the url in browser I obtain only "The request path was not found".
Examples are the following:
https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.webjars/rjs/2.1.15/ivys/ivy.xml
https://repo.typesafe.com/typesafe/ivy-releases/com.typesafe.sbt/sbt-rjs/scala_2.10/sbt_0.13/1.0.7/ivys/ivy.xml
This behaviour wastes a lot of time without any value. Is it possible to avoid non-existing path or minimize connection timeout time?
Thanks,
Michele.
As suggested in the comment, please try the latest version of Play.
As of 2018, it's 2.6.16.
I am changing the installer on an application and in the install4j IDE I am getting the error "Error instantiating (class-path-to-action)". I don't know what is causing the error or what to do to fix it.
This is the second time I have come across this while using the install4j IDE, although the first time the error disappeared once I had built the project and closed eclipse.
This time round I have tried opening up the install4j file right after a restart and I am getting the same error, with no luck in getting rid of it.
Can someone enlighten me on what could be causing this, or how to fix it?
You can find more information in the file %TEMP%\install4j_error.log about the exception. Probably the class path configured on the Installer->Custom code & Resources is not correct.
I noticed my Scala IDE consuming all the available CPU... I tried to compile the project via SBT from the command line and I got the same situation.
How can I get to know what's going wrong? Is there a way to find out what file or class/object/trait is being compiled?
I'm getting the same issue in 2.10.2 and 2.10.4-RC1
I found out the problem was due to importing a library from Slick 2.0 called heterogenous.syntax. I also got a contact with the Slick developing team in order to give'em some code to investigate on.
With Vuforia's ImageTargets sample application, I tried using OpenGL ES 1.1 by setting USE_OPENGL_ES_1_1 to true in jni/Android.mk and uncommenting and changing the corresponding line in AndroidManifest.xml (). After converting the project so that it has a C++ perspective and associating ndk-build and the proper include directories, I could successfully run the application on my Android device.
However, the problem is that once I open up jni/ImageTargets.cpp, I get several errors from Eclipse, all from places where OpenGL ES 2.0 code would execute, the first one being:
Description Resource Path Location Type Symbol 'vertexHandle' could
not be resolved ImageTargets.cpp /ImageTargets/jni line 402 Semantic
Error
Sure enough, vertexHandle is defined at the top of the ImageTargets.cpp, inside the "#ifdef USE_OPENGL_ES_2_0" block. Because USE_OPENGL_ES_2_0 is not defined (per Android.mk), the code should be able to compile successfully, and sure enough, ndk-build does not report any problems. So it seems that only Eclipse reports the problems and when I run the project, Eclipse says, "Your project contains error(s), please fix them before running your application." And thus, I cannot run my application anymore. In a sense, it's kind of strange that this never occurred until I opened ImageTargets.cpp and Eclipse "discovered" the errors.
The best work-around I've found so far is to just delete or comment out those lines (that should not be causing problems because USE_OPENGL_ES_2_0 is not supposed to be defined)... Is there a better way to deal with this problem? Did I miss a setting in Eclipse that should solve this?
I've found a solution: go to the project properties -> C/C++ Build -> Discovery Options -> Check "Automate discovery of paths and symbols"