I'm trying to use javaparser plugin of JQAssistant using command line. I have done the following:
Copied "jqassistant.plugin.javaparser-1.8.0.jar" to "plugin" folder.
I also noticed plugin has runtime dependency to "com.github.javaparser:javaparser-core:3.6.25". So I copied "javaparser-core-3.6.25.jar" to plugin folder too.
But when I try to scan a Java file I get the following error:
"ANTLR Tool version 4.9.2 used for code generation does not match the current runtime version 4.7.2"
The ANTLR version bundled with JQAssistant is 4.9.2 but plugin is expecting older version 4.7.2.
Has anyone been able to use javaparser plugin?
Some plugins (not only javaparser) indeed depend on JARs bundled with jQAssistant. Sometimes there are version conflicts, that's why it can only be guaranteed that Kontext E plugins with a certain version (let's say 1.8.x) are compatible with jQAssistant with the same major and minor version (so jQA 1.8 in this case). If you use javaparser 1.8.0 with jQAssistant 1.8.0 (which comes with org.antlr-antlr4-runtime-4.7.2), it works.
Related
I got the error that states "Unsupported class file major version 57" while trying to build LibGdx project, along with few other notifications. Same happens when trying to build using IntelliJ idea.
I have no idea how to fix that.
"Unsupported class file major version 57" means your version of Java is incompatible with the one with which Gradle was compiled. You have to make sure that the Java version you are using is compatible to the Gradle version you are using. I guess you have either to downgrade your Java version or upgrade the Gradle version.
I had Dart 2.1 v, then i update with
brew upgrade dart
After that i can check dart version:
brew info dart
Everything its fine, now is 2.7 v. But when i want to create a new project on IntelliJ IDEA still with 2.1v, i know i need to change, but on preference options "languages & Frameworks" Dart is not there.
You don't have to/can not change the Dart version for new projects in IntelliJ settings. Just be sure to use the correct Dart SDK path (e.g. the SDK that you have updated to 2.7) when creating a new project.
In pubspec.yaml you can see that the Dart version is >= 2.0.0 && < 3.0.0, so the project always uses the Dart version of the specified SDK. Thus your projects will always use the latest version of Dart 2.x. All minor updates within version 2.x are backward compatible, so there is no problem to always use the latest version.
While trying to generate build we get some plugin dependencies. When trying to add them in .product file, It shows plugin version as 0.0.0 by default. We have a situation to add more than one version of same plugins.
We tried to manually change 0.0.0 to the required version from the dependencies. We are successfully able to launch the application. But while trying to generate a build we get some errors.We have the required plugins installed.
If anyone knows how to add different versions, the help is much appreciated.
Edit:
Image showing the problem
This is the problem we are facing
The solution we tried
We tried manually changing version number but creates error during build generation
I'm not sure that this scenario is supported by PDE Build, because it sounds exotic a bit.
You can try to use different features to introduce different version of bundle.
But I think that more promissing strategy will be to "align" your dependencies, i.e. in your case it is better to select the version of GMF that uses the right Batik version.
Otherwise sooner or later you will get "blocking" bundle with singleton:true in your dependency tree, as #greg-449 mentioned.
Also, please have a look at this question: Tycho | How to build multiple version of same plugin using tycho
See my answer there:
https://stackoverflow.com/a/62426443/9062163
In fact the details I mentioned in my other answer where the result of a successful integration of Sirius 6.0.1 in an Eclipse RCP based on Photon. The troubles came from the integration of Batik 1.7 and 1.6 in the same product, the latter version being forced by the GMF version I use. I also needed some batik plugins of versions 1.8.0 and 1.9.1 for other reasons.
In intellij idea 16 EAP 144.3357.4 I have a pure Kotlin cmd project currently refusing to run with this error:
The binary version of its metadata is 1.0.1, expected version is 1.1.0
The project runs on the command-line - I invalidated caches and restarted Idea - nothing helped. Anyone had the same problem and found a way to get it working?
The problem seems to be mismatch between the kotlin library used in your project and the version of the plugin are not compatible.
Check the Kotlin plugin version and you'll most likely see something similar to:
Version: 1.0.0-rc-1007-IJ143-11
Then check the version of the Kotlin libraries by looking into META-INF/build.txt or META-INF/MANIFEST.MF and it'll most likely be other version like 1.0.0-beta-4589.
To resolve the problem update Kotlin libraries to version 1.0.0-rc-1007 which can be found in this maven repository: https://dl.bintray.com/kotlin/kotlin-eap.
Kotlin compiler marks each .class with #kotlin.Metadata to indicate, among others:
The version of the bytecode interface (naming conventions, signatures) of the class file annotated with this annotation.
That is how the compiler detected incompatibilities.
I am using the osmorc plugin in IntelliJ to build OSGI modules. This allows me to define a bundle version. I would like the bundle version to include a timestamp for each build, 1.0.1.201204241456 for example.
Can osmorc support this?
I think the plugin uses bnd under the covers, then you should be able to use 1.0.1.${tstamp}
You can format the printout, see http://www.aqute.biz/Bnd/Macros
However, I am not 100% sure it (still) uses bnd under the covers