What this, suddenly impossible to compile the code??
B4J Version: 10.20
Parsing code. (0.56s)
Java Version: 14
Building folders structure. (0.04s)
Compiling code. (0.94s)
Compiling layouts code. (0.00s)
Organizing libraries. (0.00s)
Compiling generated Java code. Error
src\GISIQON\EasyMedia\easyeditimages.java:4: error: package com.drew.imaging does not exist
import com.drew.imaging.*;
^
Note: src\GISIQON\EasyMedia\easyeditimages.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
only showing the first 1 errors, of 8 total; use -Xmaxerrs if you would like to see more
I'm still struggling with compilation errors. It's getting uncomfortable, I wonder how I'm going to get started again. I think it's some type of virus, although no security program reacts and warns of something like that. ctrl P dont help!
I use ExifTool for read metadata!
Yes, but there have been many problems with other compilation stops, often with a red screen, but not so long-lasting.
After a couple of compilations, it has worked.
I use java 14.0.1 and b4j 10.20 as well as windows11.
Have always upgraded to the latest versions, worked well.
I wonder if this is a virus.
I have another computer that runs on Windows 10. On that I run the server solution.
It first showed this compilation error, but it released after a few minutes, but not on the development machine.
I don't understand what you mean by easy media jar, how old it is?
The problem is solved!
It was because < sign had come in a Dim declaration, 'Dim < as string' The compiler did not detect the error and java complained about that declaration. Java does not have the explanation where in the code the error occurs. By comparing the code files and backup files with the WinMerge tool, I was able to locate where the error was.
The problem is solved!
It was because < sign had come in a Dim declaration, 'Dim < as string' The compiler did not detect the error and java complained about that declaration. Java does not have the explanation where in the code the error occurs. By comparing the code files and backup files with the WinMerge tool, I was able to locate where the error was.