mvn clean test running from command line says , No Compiler is provided in this environment , perhaps you are running on JRE rather than a JDK.
Selected Installed JRE's as latest JDK in preferences, still am getting the above error.
When running single feature file , the old code is being executed (i.e. though i comment out few steps from the scenario , they are being executed)
Same code when building with Jenkins is working fine.
Assuming windows and your actual directories may vary, make sure :
1) Your JAVA_HOME environment variable is set to .../jdk1.8/ directory
2) Your M2_HOME is set to your ../apache-maven-3.... directory
3) %JAVA_HOME%/bin & %M2_HOME%/bin are in your path
4) Check this with mvn -version, you should see something like:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00)
Maven home: C:\opensource\apache-maven-3.3.9
Java version: 1.8.0_92, vendor: Oracle Corporation
Java home: C:\PROGRA~1\Java\jdk1.8.0_92\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
Related
I have openjdk, scala and sbt, all installed via brew. I'm trying to
get setup to work on the scala track on exercism. I'm having no
troubles with Java or anything that uses the JVM like clojure, but
when I try to test my installation of scala by running the test for
the exercism hello example:
$ sbt test
I get a bunch of errors that seem to start with this:
java.io.IOError: java.lang.RuntimeException:
/packages cannot be represented as URI
My installed versions are as follows:
$ java --version
openjdk 13.0.1 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.1+9)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 13.0.1+9, mixed mode, sharing)
$ scala -version
Scala code runner version 2.13.1 --
$ sbt --version
sbt version in this project: 1.3.8
sbt script version: 1.3.8
I've looked and seen this error in a few questions but not seen a way to fix it.
I solved the issue by installing a java version of 1.8 and set JAVA_HOME towards this version.
export JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.8.0_251.jdk/Contents/Home"
I've got the same issue on IntelliJ IDEA and solved it with
Settings > Build, Exec... > Build Tools > sbt > JRE > set to 1.8.
JAVA_HOME has not resolve it in my case
In my case, in Intellij IDEA, I had JAVA_HOME as well as sbt JRE from the previous answer set to 1.8, but I completely forgot about the Project SDK, which was set to an incompatible version.
Ctrl + Alt + Shift + S > Project Settings > Project > Project SDK
Setting this to 1.8 as well as language levels of modules to 8 fixed my issues.
Intellij :
open Settings -> Build, Execution, Deployment -> Scala Compiler -> Scala Compile Server, then change the JDK to the one your project used. This solution solved my problem.
IntelliJ:
Go to File -> Settings -> Build, Execution, Deployment -> Build Tools -> sbt
Make sure Use sbt shell for build is checked
I found this S/O answer solves my issue:
This is a Scala compiler bug. Please upgrade to the latest Scala point release, 2.12.16.
I am having a strange issue. I am using maven 3.2, java 1.6 and jboss 5.1.
I am using all these old version because I have some system requirement.
I am working on web application.
I am getting an error
Fatal error compiling: tools.jar not found: C:\Program Files\Java\jre6\..\lib\tools.jar ->
imperviously it was working fine. When I made some changes in code and when I did this from that time I am getting This error.
I tried updating maven forcefully.
I tried maven install from eclipse.
Even I downloaded the missing jar and put into C:\Program
Files\Java\jre6\..\lib\ this path.
and many more still I am getting this error. please help me.
I think your eclipse is pointed to JRE not JDK. Can you point it to JDK and check?
Mistake you did is ---
Your build path is pointing to the wrong JRE directory/folder. So, you have to change the build path to JRE folder(which is inside the JDK folder) rather not the JRE folder that's available outside the JDK.
Eclipse > Select Windows > properties > Java > Installed JREs
• Select the "jreX" under the Installed JREs list > Select "Edit" or double click
• Your JRE home directory location may be pointing to something like
JRE home: C:..\Java\jre1.x --- (which is wrong)
• Point to the right directory as follows:
JRE home: C:..\java\jdk1.x\jre --- (this is right)
• Finish.
Clean your project and compile it. It should work fine :)
Need your help in fixing the maven compilation issue. I am not able to run any maven commands on my project. I am getting the following exception. Maven version used is
Maven home: C:\Program Files (x86)\maven\apache-maven-3.0.4\bin\..
Java version: 1.7.0_09, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_09\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Maven Command Used
mvn -o package and mvn package
Exception Stacktrace :-
Exception in thread "main" java.lang.StackOverflowError
at org.sonatype.aether.util.graph.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:88)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:198)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:202)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:202)
Please give some idea to fix this issue.
Looks like a bug of Maven 3.0.4.
Upgrade to Maven 3.2.1 resolved that for me.
I am new to Eclipse Juno using the Gradle Integration for Eclipse plugin. I am at a loss why gradle works perfectly from the command line and as an external tool; but in Eclipse Juno Package Explorer menu: gradle task it fails constantly with the following stack trace:
Error while initializing classpath container
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.5/userguide/gradle_daemon.html
Please read below process output to find out more:
java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.(File.java:423)
at org.gradle.api.internal.classpath.EffectiveClassPath.findAvailableClasspathFiles(EffectiveClassPath.java:41)
at org.gradle.api.internal.classpath.EffectiveClassPath.(EffectiveClassPath.java:32)
at org.gradle.api.internal.classpath.DefaultModuleRegistry.(DefaultModuleRegistry.java:61)
at org.gradle.api.internal.classpath.DefaultModuleRegistry.(DefaultModuleRegistry.java:55)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:41)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:32)
at org.gradle.launcher.daemon.bootstrap.GradleDaemon.main(GradleDaemon.java:22)
Could not fetch model of type 'EclipseProject' using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.5-bin.zip'.
The env variables for GRADLE_HOME, GRADLE_USER_HOME, PATH are all setup correctly. From the command line gradle -v returns:
Gradle 1.6
Gradle build time: Tuesday, May 7, 2013 9:12:14 AM UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Ivy: 2.2.0
JVM: 1.7.0_45 (Oracle Corporation 24.45-b08)
OS: Windows 7 6.1 amd64
Eclipse version:
Eclipse Java EE IDE for Web Developers.
Version: Juno Service Release 2
Build id: 20130225-0426
OS is Win7 64 on amd64 platform with 4GB of system memory so it show not be a memory issue and there are no gradle daemons running when I get the above stack trace in Eclipse Juno.
I have exhausted all means on the web, this site, and my team to resolve the issue. I need some help please.
Windows 7 sets the user.home as a UNC path.
Add -Duser.home=x:\ to your Eclipse INI file where "x" is a local drive name.
That should solve your problem
If you are using the Gradle plugin, ensure it is pointing to the correct Gradle installation. I get the error you show when I use the embedded Gradle that comes with Spring Tools Suite.
I'm a Python and PyDev newbie. My environment is OS X 10.6.11, Eclipse Indigo, PyDev 2.7.1, Python 2.6 and 3.3.
Starting from any perspective (PyDev, Java, others), selecting New->Project->PyDev->PyDev Project results in an endless spinning color beachball. The only way out is to Force Quit Eclipse.
Starting from the PyDev perspective, if I select New->Project, and then select General->Project, the same crash occurs.
My only recourse seems to be to create a generic project from, say, the Java perspective, then right-click the project in the package explorer view and choose PyDev->Set as PyDev Project, then switch to the PyDev perspective, then configure the project folder manually.
Am I missing something in my installation? Is this a known problem with PyDev?
Very similar problem here. Commenting out in case there's any follow up.
I'm using Kubuntu 15.04, Eclipse 3.8, Python 2.7 and 3.4, and what I assume is PyDev 4.2 or 4.3.
I am also a newbie, trying django framework. Creating a new PyDev-django project crashes Eclipse. When opening it again, I cannot continue creating or import it.
Here is some info about the crash, thank you for your help.
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc966da042d, pid=9132, tid=140503295805184
#
# JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
# Java VM: OpenJDK 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 2.5.6
# Distribution: Ubuntu 15.04, package 7u79-2.5.6-0ubuntu1.15.04.1
# Problematic frame:
# C [libgobject-2.0.so.0+0x3342d] g_type_check_instance_is_fundamentally_a+0xd
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again