Tag Archives: eclipse

Idea ignores compilation errors and runs in eclipse compilation mode

1. Enter file settings compiler java compiler

Modifying the configuration:
use compiler: change javac to eclipse
select “processed on errors” in eclipse options

Change project bytecode version to 6

   Enter project configuration: project structure – & gt; Project   -& gt; Project name interface

Setting: Project language level: setting 6 version

Set run/debug configurations

Run/Debug Configurations

For web projects, set “before launch” to “make, no error check” (the default should be make)
for ordinary projects, set “before launch” to “build, no error build” (the default should be build)

  Return to the editing area and click build – & gt; build Project

Eclipse Error: Could not create the Java Virtual Machine Error:A fatal exception has occurred

As a Xiaobai, this is a real headache. What you find on each platform is inconsistent, such as deleting three java files under system32, reconfiguration, etc. Finally, you find that Java becomes version 17? Just uninstall

(java17 has been uninstalled, so there is no control panel — program — uninstaller)

After uninstall

Just configure the Java environment normally

Exception record. When eclipse starts, an error is reported when workspace is opened

When eclipse starts, an error occurs when you open workspace

Problem Description:

Jump out: Eclipse an error has occurred. See the log file

resolvent

Check the log file and find the following error message:
! Message frameworkevent error
solution: CMD command and CD command jump to the eclipse.exe file. After running the command eclipse.exe - clean , the software will be opened automatically. Select workspace again to start normally

Error when opening jeesite project in eclipse

Cause analysis: there is an error in the jar package. You need to re import the jar package
first click the jeesite project, and then open properties → Java build path → libraries

Then remove all jar packages that report errors, click apply and close, select all jar packages in the Lib directory, and right-click build path to re import jar packages

errors are still reported for individual files after re introduction, as follows

The reason is that some packages are not included after Java se 9.0. If they are used, they need to be imported manually
a link is given below. You can go to this website to download the required packages by yourself
http://www.java2s.com/Code/Jar/CatalogJar.htm

[RFID] OctaneSDKJava Eclipse Error: Error occurred during initialization of boot layer

Question details

Errors are reported as follows:

Error occurred during initialization of boot layer
java.lang.module.FindException: Unable to derive module descriptor for C:\Users\tongx\eclipse-workspace\OctaneSDKJava\lib\OctaneSDKJava-1.22.0.30-jar-with-dependencies.jar
Caused by: java.lang.module.InvalidModuleDescriptorException: JDOMAbout$Info.class found in top-level directory (unnamed package not allowed in module)

Attempt method 1 (failed)

In jdk9 and above, modules are introduced. Therefore, if a separate running class is created in the default package, it cannot be compiled. There is no such problem in jdk8; If you still want to run separate classes in the default package, delete module-info.java in the SRC folder.

But my java is version 1.8, and my attempt failed

Try method 2 (feasible)

Here, we have adopted the methods of other big men:


end

How to Solve JAVA Error: error: A JNI error has occureed

Java error reporting

Notebook eslip ide error

error: a JNI error has occurred
solution:

Cause: this problem is caused by the error that the Java class file compiled by the higher version of JDK attempts to run on the lower version of JVM
method 1:
ensure that the versions of JVM (Java command) and JDK (javac command) are consistent. If it is a Windows version, enter the Java – version and javac – version commands on the command line to check whether the versions are consistent
if the versions are the same: see method 2.

If the versions are inconsistent: modify the environment variable classpath,
and then delete and uninstall the unnecessary versions in the system
Restart, delete javac, and regenerate the generated *. Class (* represents the main class name)
method 2:
if they are consistent, but still can not solve the problem, you must not compile directly with javac on the command line, but with compilers such as eclipse and NetBeans. Because many compilers come with javac instead of the compiler in the operating system. If your compiler is eclipse, you need to set the JDK version in the project properties by

-->java compiler --> Enable project specific settings -->
compiler compliance level

Set the compiler compliance level to the same version as the JVM (the version shown in Java – version on the command line).

Error in pom.xml file of sub module of Maven aggregation project

Today, when writing a sub module of a project, I found that the pom.xml of the sub module has been reporting errors. I checked that the jar package in the warehouse has been successfully downloaded. Other reasons have been eliminated, but I can’t find the reason. So Baidu searched for a method useful for my project (the development tool is eclipse). First, select the parent project of the aggregation project, right-click – run as – maven clean
then, after running successfully, you can see a build success message on the console
. Then, right-click – run as – Maven install

again, After running successfully, you can see that the console also has a build success message

finally, right click the parent project – maven – update project, and the error of pom.xml of the child project is successfully solved

reference website: https://blog.csdn.net/weixin_ 42428357/article/details/82014472

[Solved] Docker Error: Error response from daemon: driver failed programming external connectivity on endpoint

Error Message:

docker: Error response from daemon: driver failed programming external connectivity on endpoint kibana (16b783b436c6fc895f51866efea8a25c5748f7b3a78db1ec2cb0364e28e7feef): (iptables failed: iptables –wait -t nat -A DOCKER -p tcp -d 0/0 –dport 5601 -j DNAT –to-destination 172.17.0.4:5601 ! -i docker0: iptables: No chain/target/match by that name.
(exit status 1)).

Solution:
Docker reboot
You can register the iptables chain
Restart the Docker container

systemctl restart docker

[Solved] JAVA Error: Error occurred during initialization of boot layer java.lang.module.FindException

Create new project error:
Error occurred during initialization of boot layer
java.lang.module.FindException: Error reading module: /Users/chenyue/eclipse-workspace/FirstBlood/bin
Caused by: java.lang.module.InvalidModuleDescriptorException: operear_test.class found in top-level directory (unnamed package not allowed in module)

Solution:
Delete the module-info.java in the directory bar