It throws me this error every mdk file i use
Description Resource Path Location Type
Could not run phased build action using connection to Gradle distribution 'https://services.gradle.org/distributions/gradle-6.8-bin.zip'.
Initialization script 'C:\Users####\eclipse-workspace.metadata.plugins\org.eclipse.buildship.core\init.d\eclipsePlugin.gradle'
Could not compile initialization script 'C:\Users####\eclipse-workspace.metadata.plugins\org.eclipse.buildship.core\init.d\eclipsePlugin.gradle'.
startup failed:
General error during semantic analysis: Unsupported class file major version 61
java.lang.IllegalArgumentException: Unsupported class file major version 61
Related
everytime i add google_maps_flutter package i always get this error but in another project it's fine.
Please help...
FAILURE: Build failed with an exception.
* Where:
Build file 'C:\flutter\.pub-cache\hosted\pub.dartlang.org\google_maps_flutter-2.1.2\android\build.gradle'
* What went wrong:
Could not compile build file 'C:\flutter\.pub-cache\hosted\pub.dartlang.org\google_maps_flutter-2.1.2\android\build.gradle'.
> startup failed:
General error during conversion: Unsupported class file major version 61
java.lang.IllegalArgumentException: Unsupported class file major version 61
ErrorOccuredDuringInitializationofbootlayer I keep getting this error when I run
my test:
Error occurred during initialization of boot layer
java.lang.module.FindException: Unable to derive module descriptor for
C:\Users\Bonfire.eclipse\org.eclipse.platform_4.12.0_867647348_win32_win32_x86_64\plugins\com.beust.jcommander_1.72.0.jar
Caused by: java.lang.IllegalArgumentException:
com.beust.jcommander.1.72.0: Invalid module name: '1' is not a Java
identifier
How can I fix it?
Add TestNG Library to classpath in buildpath ( not to module path). It will work fine.
To avoid this error, do not add TestNG library in the project or src folder. Try adding it into the package. To do so , follow the below mentioned procedure.
Right click on the package, click Build Path->Configure Build Path, go to Libraries tab, select Classpath and click on Add Library to select TestNG.
This error message...
Error occurred during initialization of boot layer java.lang.module.FindException:
Unable to derive module descriptor for C:\Users\Bonfire.eclipse\org.eclipse.platform_4.12.0_867647348_win32_win32_x86_64\plugins\com.beust.jcommander_1.72.0.jar
Caused by: java.lang.IllegalArgumentException: com.beust.jcommander.1.72.0: Invalid module name: '1' is not a Java identifier
...implies that there was an issue with the java classpath.
As per the discussion Launch with java 11 fails: Error: Could not find or load main class with Caused by: java.lang.ClassNotFoundException: with there are some issues with some particular classpaths for java-11 and the launch fails if:
The classpath contains a folder with spaces
The classpath length is larger than 32767 characters.
Where as java-8 works fine.
Reference
Unable to import org.openqa.selenium.WebDriver using Selenium and Java 11
Outro
Eclipse plugin: TestNG testcase does not run with Jdk11
Need to add 1.8 version library
Remove TestNG from build path library and add again
Recheck - the issue should be resolved.
I got same issue and I solved it. When creating the project, don't create module-info.java. When the project was already created with the module-info.java, deleting this file didn't help me.
I just created new project without module-info.java, and all works good now.
Best option to resolve this:
Find all file and folder starting with . e.g. — .metadata / .setting and delete them.
Add all the JARS.
Add testNG Libraries.
Execute it.
Done.
Can no longer build my application due to an issue with a dependent class of ruta-maven-plugin:2.6.1. I've tried to use multiple version of ASM including 5.0.2 and 6.2. These version are dependencies of Apache Tika 1.17/18/19.
Here is the full build failure message:
Failed to execute goal org.apache.uima:ruta-maven-plugin:2.6.1:generate (default) on project DAnE-Pipeline: Execution default of goal org.apache.uima:ruta-maven-plugin:2.6.1:generate failed: Failed to read candidate component class: URL [jar:file:/home/fm/.m2/repository/org/apache/uima/ruta-core/2.6.1/ruta-core-2.6.1.jar!/org/apache/uima/ruta/resource/TrieXMLEventHandler.class]; nested exception is org.springframework.core.NestedIOException: ASM ClassReader failed to parse class file - probably due to a new Java class file version that isn't supported yet: class path resource [org/xml/sax/helpers/DefaultHandler.class]; nested exception is java.lang.IllegalArgumentException -> [Help 1]
I feel like I've tried everything. Any help will be appreciated!
I re-read Peter's suggestion above. I was adding a newer Spring dependency in my project, but not in the "scope of the plugin". Once I created the Spring dependencies there, it worked! Thanks, Peter.
When I am trying to start sbt, it fails throwing an IO exception.
Version of SBT - 1.1.2
Version of Scala - 2.12.6
Error:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[info] Loading project definition from C:\Users\username\IdeaProjects\projectname\project
[info] Loading settings from build.sbt ...
[info] Set current project to example (in build file:/C:/Users/username/IdeaProjects/projectname/)
[error] server failed to start on local:sbt-server-ad238fc8ee352b69065c. java.io.IOException: Could not create lock for
\\.\pipe\sbt-server-ad238fc8ee352b69065c_lock, error 231
Analysing the source of the throw it seems error code 231 refers to Windows error:
ERROR_PIPE_BUSY
231 (0xE7)
All pipe instances are busy.
The pipe cannot be accessed because another process is using it, so try closing down IntelliJ and any other SBT server running, and try again later. Perhaps even reboot the machine, and then start a single system SBT server (not IntelliJ), and see if the issue persists.
We are in the process of migrating our application from 3.7.2 to 4.3.2, but facing few issues during pde-build. Though I can get the application to build and launch and work well from the Eclipse 4.3.2 IDE itself, the command line build fails with messages about many missing plugins, compile failures etc.
In the log file there are lots of missing plugin messages, but the Eclipse 4.3.2 folder I am providing for the pde build has all these missing jars in it's plugins folder. I have confirmed this by searching for the actual jar names in the Eclipse SDK directory unzipped by the build for its later consumption.
These are the messages from the log after the pde-build target is run:
[eclipse.generateFeature] Some inter-plug-in dependencies have not been satisfied.
[eclipse.generateFeature] Bundle org.eclipse.cdt.core.nl1:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.core_[5.5.0,5.6.0) has not been found.
[eclipse.generateFeature] Bundle org.eclipse.cdt.core.nl2a:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.core_[5.5.0,5.6.0) has not been found.
[eclipse.generateFeature] Bundle org.eclipse.cdt.core.nl2:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.core_[5.5.0,5.6.0) has not been found.
[eclipse.generateFeature] Bundle org.eclipse.cdt.core.nlBidi:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.core_[5.5.0,5.6.0) has not been found.
[eclipse.generateFeature] Bundle org.eclipse.cdt.debug.core.nl1:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.debug.core_[7.3.0,7.4.0) has not been found.
[eclipse.generateFeature] Bundle org.eclipse.cdt.debug.core.nl2a:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.debug.core_[7.3.0,7.4.0) has not been found.
[eclipse.generateFeature] Bundle org.eclipse.cdt.debug.core.nl2:
[eclipse.generateFeature] Host plug-in org.eclipse.cdt.debug.core_[7.3.0,7.4.0) has not been found.
I also get errors related to compile failures after all those missing plugin messages:
[83 units compiled]
[javac] ----------
[javac] 1. ERROR in C:\vobs\chechand_CM_cm521\vobs\build\toolkit\plugins\com.app.ecm.configmgr.engine\src\com\app\ecm\configmgr\engine\util\XmlDoc.java (at line 0)
[javac] /* app Confidential
[javac] ^
[javac] ***The type java.lang.Class cannot be resolved. It is indirectly referenced from required .class files***
*[javac] ----------
[javac] 1 problem (1 error)
[javac] Compilation failed. Compiler errors are available in C:\vobs\chechand_CM_cm521\vobs\build\toolkit\plugins\com.app.ecm.configmgr.engine/#dot.log
BUILD FAILED
C:\Users\Administrator\chechand_Common_3PT_3\vobs\fnet_3pt\eclipse\4.3.2\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\scripts\productBuild\productBuild.xml:43: The following error occurred while executing this line:
C:\Users\Administrator\chechand_Common_3PT_3\vobs\fnet_3pt\Eclipse\4.3.2\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\scripts\build.xml:105: The following error occurred while executing this line:
C:\Users\Administrator\chechand_Common_3PT_3\vobs\fnet_3pt\Eclipse\4.3.2\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\templates\headless-build\customTargets.xml:12: The following error occurred while executing this line:
C:\Users\Administrator\chechand_Common_3PT_3\vobs\fnet_3pt\Eclipse\4.3.2\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\scripts\productBuild\allElements.xml:20: The following error occurred while executing this line:
C:\Users\Administrator\chechand_Common_3PT_3\vobs\fnet_3pt\Eclipse\4.3.2\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\scripts\genericTargets.xml:118: The following error occurred while executing this line:
C:\Users\Administrator\chechand_Common_3PT_3\vobs\fnet_3pt\Eclipse\4.3.2\eclipse\plugins\org.eclipse.pde.build_3.8.100.v20130514-1028\scripts\genericTargets.xml:123: The following error occurred while executing this line:
C:\vobs\chechand_CM_cm521\vobs\build\toolkit\features\org.eclipse.pde.build.container.feature\build.xml:30: The following error occurred while executing this line:
C:\vobs\chechand_CM_cm521\vobs\build\toolkit\features\org.eclipse.pde.build.container.feature\build.xml:16: The following error occurred while executing this line:
C:\vobs\chechand_CM_cm521\vobs\build\toolkit\features\com.app.ecm.configmgr.ui.feature\build.xml:63: The following error occurred while executing this line:
C:\vobs\chechand_CM_cm521\vobs\build\toolkit\features\com.app.ecm.configmgr.ui.feature\build.xml:19: The following error occurred while executing this line:
C:\vobs\chechand_CM_cm521\vobs\build\toolkit\plugins\com.app.ecm.configmgr.engine\build.xml:329: The following error occurred while executing this line:
C:\vobs\chechand_CM_cm521\vobs\build\toolkit\plugins\com.app.ecm.configmgr.engine\build.xml:290: Compile failed; see the compiler error output for details.
I have searched through the forum but didn't find anything related to issues I am facing.
Edit: I have added Bundle-RequiredExecutionEnvironment= JavaSE-1.7 in my MANIFEST.MF for my product but I still face this issue.
Thank you for the help.