i am trying to created a build in CloubBees BuildHive. my maven is using 1.7 JDK and when i try to build i am getting following exception
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Failure executing javac, but could not parse the error:
javac: invalid target release: 1.7
Usage: javac <options> <source files>
use -help for a list of possible options
Anyone tell me how to change the JDK version ?
Duplicate of Does buildhive from CloudBees have JDK 7 I think. It is on our to-do list to set JDK 7 as the default.
Related
After upgrading to jooq 3.17.1 I get the following error:
Error:
/home/runner/work/waste-coordinator/waste-coordinator/webapp/target/generated-sources/jooq/com/myapp/portal/backend/jooq/tables/LoadView.java:[521,84]
text blocks are not supported in -source 11 Error: (use -source 15
or higher to enable text blocks)
It appears to me that it is generating source that is not compatible with JDK11. Is there a flag in the generator somewhere that can make it generate JDK 11 compatible code?
Edit: now I am getting the following compile error
[ERROR] COMPILATION ERROR : [INFO]
------------------------------------------------------------- [ERROR] /usr/local/code/sferion/WasteCoordinator/data/src/main/java/com/wastecoordinator/data/JOOQGenerator.java:[4,24]
cannot access org.jooq.codegen.GenerationTool bad class file:
/Users/benstpierre/.m2/repository/org/jooq/jooq-codegen/3.17.1/jooq-codegen-3.17.1.jar(/org/jooq/codegen/GenerationTool.class)
class file has wrong version 61.0, should be 55.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
Is jooq 3.17 not compatible with JDK 11?
You can download the right distribution to work with JDK 11 from here if you're licensed:
https://www.jooq.org/download/versions
Note that starting from jOOQ 3.17, the jOOQ Open Source Edition increased the baseline JDK version to Java 17, see:
https://github.com/jOOQ/jOOQ/issues/12430
https://blog.jooq.org/3-17-0-release-with-computed-columns-audit-columns-pattern-matching-reactive-transactions-and-kotlin-coroutine-support/
jOOQ is a bit early here, given that Spring will increase their own baseline only later in 2022:
https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6
But jOOQ will continue to provide paid support for older JDKs for quite a while, still. At the same time, jOOQ 3.14 - 3.16 will receive patches for another while, too.
I'm having issues when trying to run the Android Emulator with Appcelerator. I'm new to this program and not having much luck finding an answer on how to fix this error. My app development knowledge up til now is Xcode and Apache Cordova. I've uninstalled/reinstalled Appcelerator along with different versions of Node with no luck. iPhone runs fine, so I'm guessing it's something with Java, but I can't figure out how or where to find it or fix it.
I'm running Appcelerator v7.1.2 with Node v8.16.0 and npm v6.4.1. Any help is greatly appreciated!
Below is what it is showing when I try to run for Android.
[INFO] : Deploy type: development
[INFO] : Building for target: emulator
[INFO] : Building for emulator: Pixel_2_XL_API_29
[INFO] : Targeting Android SDK API: 29
[INFO] : Building for the following architectures: arm64-v8a, armeabi-v7a, x86
[INFO] : Signing with keystore: /Users/user/Library/Application Support/Titanium/mobilesdk/osx/8.3.0.GA/android/dev_keystore (tidev)
[INFO] : Debugging disabled
[INFO] : Profiler disabled
[INFO] : Transpile javascript: true
[INFO] : Generate source maps: true
[INFO] : Forcing rebuild: /Users/user/Documents/Appcelerator_Studio_Workspace/MyFirstApp/build/android/build-manifest.json does not exist
[INFO] : Starting Hyperloop assembly
[INFO] : [Hyperloop] Generating system metabase
**[ERROR] Application Installer abnormal process termination. Process exit value was 1
[ERROR] : hyperloop:generateMetabase: Failed to generated metabase: warning: [options] bootstrap class path not set in conjunction with -source 6
error: Source option 6 is no longer supported. Use 7 or later.
error: Target option 6 is no longer supported. Use 7 or later.
[ERROR] : An error occurred during build after 735ms
[ERROR] : warning: [options] bootstrap class path not set in conjunction with -source 6
[ERROR] : error: Source option 6 is no longer supported. Use 7 or later.
[ERROR] : error: Target option 6 is no longer supported. Use 7 or later.**
As a different user has the same question and provided additional information it is likely that it is the same issue:
use Java 1.8
use Node 10.13.x
especially the Java version is required. Node might work in a newer version but the official supported version is 10.13.x at the moment
I was working happily in InteliJ with scala 2.10 and Java 1.7 - and am in the process of trying to upgrade to scala 2.11 and Java 1.8
I'm on Ubuntu 14 -- and javac shows
update-alternatives --config javac
There are 2 choices for the alternative javac (providing /usr/bin/javac).
Selection Path Priority Status
------------------------------------------------------------
0 /usr/lib/jvm/java-8-oracle/bin/javac 4 auto mode
1 /usr/lib/jvm/java-7-oracle/bin/javac 3 manual mode
* 2 /usr/lib/jvm/java-8-oracle/bin/javac 4 manual mode
As I have both java 7 and 8 installed.
I'm trying to import a Play 2.3 project (using the IntelJ SBT auto import) and am getting the error
Error while importing SBT project: ... at xsbt.boot.Boot$.main(Boot.scala:20) at xsbt.boot.Boot.main(Boot.scala) [error] sbt.IncompatiblePluginsException: Binary incompatibility in plugins detected. [error] Note that conflicts were resolved for some dependencies: [error] com.github.mpeltonen:sbt-idea [error] commons-io:commons-io [error] org.apache.commons:commons-lang3
......
I'm not sure how to progress investigating this; but my thinking is
From - Sbt plugin binary incompatibility - it could relate to the version on SBT that inteliJ is using?
Another thought was; Is the InteliJ Scala Plugin specific to a Java version (7 vs 8?) If so - how do I make sure InteliJ gets the correct one? I tried re-installing the plugin; but that didn't change anything.
Thanks
Brent
Ah; I just had to update Project Settings to use 1.8!
I am new to Breeze (http://www.scalanlp.org/) and Scala in general. Please help to generate
Eclipse project for Breeze with sbt. I have Eclipse plugin for sbt installed.
When I try sbt eclipse it fails with the following errors. What is
wrong?
Thanks!
> ~/Distrib/Scala/breeze-master>sbt
[info] Loading global plugins from /home/an/.sbt/plugins
[info] Loading project definition from /home/an/Distrib/Scala/breeze-
master/project
[info] Set current project to breeze (in build file:/home/an/Distrib/
Scala/breeze-master/)
> eclipse
[info] About to create Eclipse project files for your project(s).
[error] java.util.NoSuchElementException: None.get
[error] Use 'last' for the full log.
> last
...
...
[debug] Project dependencies for configuration 'compile':
Success(List(breeze-math))
[debug] Project dependencies for configuration 'test': Success(List())
java.util.NoSuchElementException: None.get
at scala.None$.get(Option.scala:274)
at scala.None$.get(Option.scala:272)
at com.typesafe.sbteclipse.core.Eclipse$.relativize(Eclipse.scala:
498)
at com.typesafe.sbteclipse.core.Eclipse$$anonfun$srcEntry
$1.apply(Eclipse.scala:252)
at com.typesafe.sbteclipse.core.Eclipse$$anonfun$srcEntry
$1.apply(Eclipse.scala:249)
at scalaz.effects.IO$$anon$3$$anonfun$pure$1$$anonfun$apply
$23.apply(IO.scala:118)
at scalaz.effects.IO$$anon$3$$anonfun$pure$1$$anonfun$apply
$23.apply(IO.scala:118)
at scalaz.FreeFunctions$$anonfun$return_$1.apply(Free.scala:181)
at scalaz.FreeFunctions$$anonfun$return_$1.apply(Free.scala:181)
at scalaz.Pure$$anon$19$$anon$2.apply(Pure.scala:76)
at scalaz.Functor$$anon$15$$anon$45.apply(Functor.scala:84)
at scalaz.Free$class.go$1(Free.scala:73)
at scalaz.Free$class.run(Free.scala:76)
at scalaz.Free$Gosub.run(Free.scala:18)
at scalaz.effects.IO$class.unsafePerformIO(IO.scala:13)
at scalaz.effects.IO$$anon$2.unsafePerformIO(IO.scala:113)
at com.typesafe.sbteclipse.core.Eclipse$.onSuccess(Eclipse.scala:149)
at com.typesafe.sbteclipse.core.Eclipse$$anonfun$action
$4.apply(Eclipse.scala:105)
at com.typesafe.sbteclipse.core.Eclipse$$anonfun$action
$4.apply(Eclipse.scala:105)
at scalaz.Validation$class.fold(Validation.scala:7)
at scalaz.Success.fold(Validation.scala:82)
at com.typesafe.sbteclipse.core.Eclipse$.action(Eclipse.scala:105)
at com.typesafe.sbteclipse.core.Eclipse$$anonfun$eclipseCommand
$2.apply(Eclipse.scala:81)
at com.typesafe.sbteclipse.core.Eclipse$$anonfun$eclipseCommand
$2.apply(Eclipse.scala:81)
at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply
$2.apply(Command.scala:60)
at sbt.Command$$anonfun$applyEffect$1$$anonfun$apply
$2.apply(Command.scala:60)
at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply
$3.apply(Command.scala:62)
at sbt.Command$$anonfun$applyEffect$2$$anonfun$apply
$3.apply(Command.scala:62)
at sbt.Command$.process(Command.scala:90)
at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(MainLoop.scala:
71)
at sbt.MainLoop$$anonfun$next$1$$anonfun$apply$1.apply(MainLoop.scala:
71)
at sbt.State$$anon$2.process(State.scala:170)
at sbt.MainLoop$$anonfun$next$1.apply(MainLoop.scala:71)
at sbt.MainLoop$$anonfun$next$1.apply(MainLoop.scala:71)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18)
at sbt.MainLoop$.next(MainLoop.scala:71)
at sbt.MainLoop$.run(MainLoop.scala:64)
at sbt.MainLoop$$anonfun$runWithNewLog$1.apply(MainLoop.scala:53)
at sbt.MainLoop$$anonfun$runWithNewLog$1.apply(MainLoop.scala:50)
at sbt.Using.apply(Using.scala:25)
at sbt.MainLoop$.runWithNewLog(MainLoop.scala:50)
at sbt.MainLoop$.runAndClearLast(MainLoop.scala:33)
at sbt.MainLoop$.runLoggedLoop(MainLoop.scala:17)
at sbt.MainLoop$.runLogged(MainLoop.scala:13)
at sbt.xMain.run(Main.scala:26)
at xsbt.boot.Launch$.run(Launch.scala:55)
at xsbt.boot.Launch$$anonfun$explicit$1.apply(Launch.scala:45)
at xsbt.boot.Launch$.launch(Launch.scala:69)
at xsbt.boot.Launch$.apply(Launch.scala:16)
at xsbt.boot.Boot$.runImpl(Boot.scala:31)
at xsbt.boot.Boot$.main(Boot.scala:20)
at xsbt.boot.Boot.main(Boot.scala)
[error] java.util.NoSuchElementException: None.get
[error] Use 'last' for the full log.
>
This is a known bug in sbteclipse: https://github.com/typesafehub/sbteclipse/issues/128
You can try commenting out the "doc" project in the Project.scala definition and see if that helps. Otherwise, I think this is a bug in sbteclipse that has to get resolved first.
Environment: hudson/sonar/maven2 in ubuntu locally with default parameters
And I got the log from hudson below, I can't figure out where is the problem.
[INFO] Sonar host: http://localhost:9000
[INFO] Sonar version: 2.0.1
[INFO] [sonar-core:internal {execution: default-internal}]
[INFO] Database dialect class org.sonar.api.database.dialect.Derby
[INFO] ------------- Analyzing Game of Life business logic module
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can not execute Sonar
Embedded error: Can not analyze the project
Cannot stop. Current container state was: CONSTRUCTED
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar
And I notice it also has problem when run it command line without hudson
mvn sonar:sonar
I got this problem with .Net plugins for Sonar.
They needed all projects to be analyzed with JDK 6 (even non-.Net projects).
This error was raised when I tried to analyze projects with JDK 5.
Here is the URL of the .Net plugins : http://docs.codehaus.org/display/SONAR/.Net+plugin
The solution I got was to fork the compiler to use a JDK5 compiler on my projects which needed to be analyzed in JDK5 and not JDK6.
See on the .Net plugins page :
Maven and Sonar dotnet plugins need Java6 (at compile time and runtime)
What the sentence does not say is that all projects in your Sonar instance must use Java6.
A JIRA has been created : http://jira.codehaus.org/browse/SONARPLUGINS-1086 .
Got the hints from http://old.nabble.com/Another-%22Current-container-state-was%3A-CONSTRUCTED%22-problem-td28172925.html#a28194257
It seems the problem is inconsistency in maven plugins in my nexus repository, when I change to mirrors.ibiblio.org and clean the .m2 directory, everything goes fine.
BUT I don't know which plugins causes this problem and the log information is so wired, will be nice if some people points which plugin cause this problem and explain the reason for this error information