I get this error while building corda 4.8 on a windows 10 box using intellij:
Could not find javafx-controls-mac.jar (org.openjfx:javafx-controls:11.0.2).
Searched in the following locations:
file:/C:/Users/Admin/.m2/repository/org/openjfx/javafx-controls/11.0.2/javafx-controls-11.0.2-mac.jar
I don't want to build the mac version, how can I disable or ignore the error?
Maybe I'm missing something as far as context, but currently, you can only build corda with java 8. Java 11 is not supported yet. Take a look at this docs page for the specific tooling you need to configure CorDapps.
https://docs.corda.net/docs/corda-os/4.7/getting-set-up.html
Long story short, until corda 5 is released you'll need java 8 to build cordapps which you can install here : https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html
Related
I can't find this corda-tools-ha-utilities-.jar from internet or enterprise version, could anyone told me that how I could get it , version 4.4 to 4.7 is ok to me . thx.
For corda enterprise users you're gonna need to reach out to support as they have a specific repository for enterprise jars like the ha utilities.
The open source users can get pretty much any of the jars in their usual gradle builds. (repositories can be seen in the cordapp template here: https://github.com/corda/cordapp-template-java)
I have JDK 14 and JMeter 5.3 configured on my Windows 64 bit system But I don't see "Browser" option in "View Listeners in a Tree" in JMeter.
Any ways I can get it?
The easiest solution is just to downgrade to Oracle JDK 8 as it includes JavaFX package which is required for this Browser option to work.
However according to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure you should always be using the latest version of JRE/JMeter so if you need to be able to render the response in the View Results Tree listener go for the following steps:
Download and install OpenJFX
Set PATH_TO_FX environment variable pointing to the OpenJFX installation folder
Restart JMeter - at this point you should see the Browser option
Browser option was removed due to missing JavaFX suppport
Bug 63355 - View Results Tree: Browser view option is not Available with Java 11
You can downgrade to Java 8 (which include library) or add Java FX library manually
Felix Schumacher:
You either have to downgrade to a Oracle Java -- which includes JavaFX, or you try to integrate JavaFX into a newer Java version. openjfx.io claims to have JavaFX versions for newer Java versions.
Does anyone know how to publish a .NET Core 3.0 application for ARM64?
I can only select "linux-arm" but no "linux-arm64".
Setting linux-arm in combination with x64 also doesnt work. It says the settings are not compatible.
As stated here it should already be supported: https://github.com/dotnet/core/blob/master/release-notes/3.0/3.0-supported-os.md
The linked article points to the supported OSs, not the list of runtime identifiers. An explanation of an RID and a list of common ones can be found in .NET Core RID Catalog. The full list can be found at the CoreFX repo, in runtime.json. linux-arm64 is included but that's only the base OS. There are a lot of specific identifiers like "debian-arm64", "debian.10-arm64", "rhel-arm64" and "ubuntu-arm64". You'll have to use the RID that corresponds to your distribution.
As the RID catalog explains, a runtime identifier consists of the OS, OS version, architecture and optional extra qualifiers.
[os].[version]-[architecture]-[additional qualifiers]
ubuntu-arm64 is the generic Ubuntu version for ARM64 while ubuntu.19.04-arm64 targets Ubuntu 19.04 specifically.
There's no specific version for Raspbian. If you want to target Raspberry in general, you'll have to use linux-arm. If you want to take advantage of the 4GB RAM model, assuming you already use a 64bit OS you may be able to target linux-arm64.
The linux-arm64 isn't available from the publish profile settings, but if you build it using linux-arm and manually edit your .pubxml file afterwards, it works on the pi just fine. As the link you provided shows, it is supported. It seems it hasn't been added to the tooling yet.
Just publish as usual and then edit .pubxml
Change
<RuntimeIdentifier>linux-arm</RuntimeIdentifier>
to
<RuntimeIdentifier>linux-arm64</RuntimeIdentifier>
Then you can publish on a 64bit Raspberry pi.
So I updated to swift 3.0 and now my projects with realm 1.0.2 all give me an error.
RealmSwift compiled with older version of Swift language (2.0) than previous files (3.0)
I also tried to build a net new project and still get the build error, so I know it is not a conversion issue on the Swift side.
I found several Swift 3.0 beta users and tried to run the script to update my version to 3.0 and several other options. The last few posts appeared to use Cocoa Pods - which I don't currently use. Is that the supported fix path?
Any help or direction would be greatly appreciated.
I haven't tried it yet, but here is what should work.
Essentially, the compiler gives you a description of what went wrong. The framework was compiled with Swift 2.0, while your project or other files were compiled with Swift version 3.0 (which means you made the switch after upgrading to the new version of Xcode.
To fix this, you need to use the Realm framework compiled with a Swift 3.0 compiler. Since the Realm team doesn't yet provide a precompiled version compiled with Swift 3.0, you have to do so yourself. To do that, go to their Github repository, and follow the instructions in the README under "Building Realm":
Prerequisites:
Building Realm requires Xcode 7.3.
Building Realm documentation requires jazzy
Once you have all the necessary prerequisites, building
Realm.framework just takes a single command: sh build.sh build.
You'll need an internet connection the first time you build Realm to
download the core binary.
This should generate the Realm framework with the current compiler version, which you then just have to use to replace your current Realm framework with. After that, everything should compile as it used to.
As stated before, I don't know if this actually works, as I haven't tried it yet. I don't exactly know if Swift 3.0 is supported by Realm yet or if there are any other issues you could run into. So please let me know how this works out!
I've installed Java 8 and Spring STS on Mac. Running jjs from the command line works. However, when trying to create a new class in a Maven project in STS, the editor doesn't recognise the javafx.* package automatically.
Attached you'll find an example of an image showing that the only Label object suggested is the java.awt one.
Any idea on how I could solve this?
Regards,
M.
I think this is related to the settings of your project. If your project is created with an execution environment JavaSE-1.8, this execution environment doesn't have the javafx API defined as accessible and you would need to manually allow that. If you choose the 1.8 JRE (as a JRE, not an execution environment) in your project settings, the JavaFX API is accessible and works nicely in content-assist, quick fix, etc. This is at least the case if you create a standard Java project.