I want to use Intellij 13.1.6 as my go app IDE, but there are some problem I can't sovle yet.
The default version of go support plugin installed on Intellij is 0.9.15, but in this version, there are some bugs so that I can build project successfully.
So I try to build the go-plugin jar by myself follow this article:
https://content.pivotal.io/blog/setting-up-the-google-go-plugin-with-intellij-idea-13-on-os-x-10-8-5
But when I click Prepare Plugin Module 'google-go-language' For Deployment, it shows errors cause some method can't be found. As the following figure
I think the problem is the version of my Intellij lack of some lib so that I can't build go-plugin jar successfully. How do I fix this?
Appreciate any replies.
Intellij Version: 13.1.6
JDK Version: 1.7
Go-plugin on GitHub: the latest commit on master branch (0261ffa)
The latest version of the Go plugin code requires IntelliJ IDEA 14.
Related
I worked with Lombok without any problems until Today, when my Intellij was automatically updated to the latest version 2020.3 30th, November build. After that, any Lombok annotations is not recognised anymore.
My Java project still build from command line with Maven but annotations are completely ignored in the project and cannot run any unit tests manually.
Things I tried so far:
Reinstalled the Lombok plugin
Restarted Intellij
Restarted the laptop
Invalidated the cache
Re-cloned the project from github
Checked that the annotation processor is enabled
Nothing worked. What could have happened? Any idea on what I can try to do?
To summarize go to IntelliJ Preferences (Cmd + ,)
Preferences -> Build, Execution, Deployment -> Compiler
search for this option:
User-local build process VM options (overrides Shared options):
and add this value:
-Djps.track.ap.dependencies=false
A work around is here, until they fix the actual problem:
https://youtrack.jetbrains.com/issue/IDEA-250718#focus=Comments-27-4418347.0-0
(see screenshoot for IJ fix)
I was using Lombok fine with 2020.2 and plugin, but in 2020.3.1 it should be (and it is) included
...but I had compilation errors like Cannot resolve symbol 'log' (when using #Slf4j)
I solved the problem deleting .idea from project and opened it again...
edit: it happened to me again today with new checkout (we do not have .idea in Git) and I had similar problem. Not sure if that was a fix, but I checked the plugin (it is not on screenshot above), it started working after, but I built it from cmd (Maven) and tried few other things, so I'm not sure what is a real fix
My problem was related to my lombok version
Before upgrade my IntelliJ to 2020.03 my lombok version was 1.18.10 and the lombok plugin 0.32-EAP
After upgrade my lombok dependency to 1.18.16 it start work again without any issues. Looks like the plugin is not bundled yet in the community edition.
I don't if is necessary, but my first action was to uninstall the plugin when I read the README on Lombok Plugin repo
Please check in: Lombok plugin settings you didn't disable it unintentionally.
Seems like lombok is not bundled in Community edition of 2020.3 version. Fix is expected in 2020.3.1 version.
From Lombok plugin GitHub issue
Sorry guys, I have to confirm, it was forgotten to add it properly
into the last community build. See bug on Jetbrains Yourtrack:
https://youtrack.jetbrains.com/issue/IDEA-257311
The Ultimate 2020.3 version contains lombok plugin as expected per
default.
lombok plugin should be included in both IntelliJ distribution
(Ultimate and Community) starting with 2020.3 release. Something get
wrong, we are working to fix it.
Fix is now planned for IntelliJ Community release 2020.3.1
Update
2020.3.1 Community is released and contains lombok plugin by default now
I managed to make it work on a gradle project (Intellij 2020.3.2)
by using exactly this in build.gradle :
annotationProcessor 'org.projectlombok:lombok:1.18.18'
implementation 'org.projectlombok:lombok:1.18.18'
I think important point is to declare it as "annotationProcessor" to include it in the gradle build.
I did not even have to mess around with "User-local build process VM options" and even "Enable Annotation Processing" is not ticked in Intellij Settings.
So I guess that gradle is taking care of the Lombok generation, and not IDEA.
but at least it finally works after hours lost trying to fix IntelliJ.
This is the problem with lombok, whenever IntelliJ provides upgrade lombok starts crying. Same happened with IntelliJ 2020.2
Now there are 2 solutions
Wait till the developers of lombok provide upgrade compatible with IntelliJ 2020.3
Downgrade IntelliJ to previous working version. For me IntelliJ 2020.2 worked perfectly fine.
Installing Lombok plugin and enabling the annotation processor should do the needful. If still issue persists then i think you should report a bug and see what they reply.
I am getting below error in intellij for a gradle project. I am importing existing gradle project and trying refresh it in gradle window.
Error:No such property: GradleVersion for class: JetGradlePlugin
Please advise.
I had this problem while upgrading to java 11.
I had to downgrade gradle from 5.0 to 4.10.3.
Then I needed to upgrade to the latest version of Intellij Idea.
You'll probably just need to upgrade Intellij.
edit: Downgrading gradle is the fix. The Intellij version didn't matter.
You need at least Idea 2017.3 to work with Gradle 5.0+, earlier versions are not compatible because of implicit import being removed in version 5.0. See related youtrack ticket
After a couple of days, I found a solution to this.
1)First, find the Gradle version (gradle -v), In my case, Gradle version was 4.1.
2)Then in the android studio change my Gradle version to 4.1
(File --> Project Structure -> Project)
3)Click ok Button.
that's it :)
This worked for me.
Go to 'Settings -> Build, Execution, Deployment -> Build Tools -> Gradle'
And select 'Use local gradle distribution'
I just had to downgrade gradle from 5.1.1 to 4.10.3 to resolve it. However it caused an another error: “cannot resolve symbol R” in Android Studio. I was using gradle 3.3.0. It was the main culprit. Gradle 3.2.1 removed the error.
it's work downgrade gradle from 5.1.1 to 4.10.3
This was happend to me after i fromat my lap and after installing android 3.1 i tryed to open my projects then this error came
This worked for me:
unstall the android studio > reinstaleled it and updat to the leatest version > upadate gradle
I am getting some errors that had been fixed according to the 6.18 release notes and was hoping to bump the dependency version to fix the issue, but when I mvn install the project now, I get a build error
Classes found in the wrong directory: {META-INF/versions/9/com/teamdev/jxbrowser/chromium/swing/internal/AWTHelper$1.class=com.teamdev.jxbrowser.chromium.swing.internal.AWTHelper$1, META-INF/versions/9/com/teamdev/jxbrowser/chromium/swing/internal/NativeLinux.class=com.teamdev.jxbrowser.chromium.swing.internal.NativeLinux, META-INF/versions/9/com/teamdev/jxbrowser/chromium/javafx/internal/NativeMac.class=com.teamdev.jxbrowser.chromium.javafx.internal.NativeMac, META-INF/versions/9/com/teamdev/jxbrowser/chromium/javafx/internal/dialogs/ColorDialog.class=com.teamdev.jxbrowser.chromium.javafx.internal.dialogs.ColorDialog, META-INF/versions/9/com/teamdev/jxbrowser/chromium/internal/JavaVersion.class=com.teamdev.jxbrowser.chromium.internal.JavaVersion, META-INF/versions/9/com/teamdev/jxbrowser/chromium/swing/internal/AWTHelper.class=com.teamdev.jxbrowser.chromium.swing.internal.AWTHelper, META-INF/versions/9/com/teamdev/jxbrowser/chromium/swing/internal/Native.class=com.teamdev.jxbrowser.chromium.swing.internal.Native, META-INF/versions/9/com/teamdev/jxbrowser/chromium/internal/X509CertificateFactory.class=com.teamdev.jxbrowser.chromium.internal.X509CertificateFactory, META-INF/versions/9/com/teamdev/jxbrowser/chromium/swing/internal/AWTHelper$InstanceHolder.class=com.teamdev.jxbrowser.chromium.swing.internal.AWTHelper$InstanceHolder, META-INF/versions/9/com/teamdev/jxbrowser/chromium/javafx/internal/Native.class=com.teamdev.jxbrowser.chromium.javafx.internal.Native, META-INF/versions/9/com/teamdev/jxbrowser/chromium/internal/OS.class=com.teamdev.jxbrowser.chromium.internal.OS}
I have cleared my maven cache and tried versions 6.18-6.20 but I can only build with 6.17 and below. My license file claims to work for versions 6.X, so I would assume that is not the issue.
Thanks!
Starting from the version 6.18, JxBrowser provides multi-release jars, so it is able to work with both Java 8 and Java 9. And it seems that the maven used to build the application does not support the MR-JAR's, so it generates a build error. So you need to upgrade Maven version.
I am new to Eclipse RCP and plugin development so please don't be cruel.
I am using Maven and I have a remote repository. Yesterday Eclipse was fine but today it got messed up and I imported all the projects again so I reconfigured all but I can't get out of this problem. We use e(fx)clipse 2.5 but I installed the 3.0 version of it because I didn't find the link to install it via Eclipse.
Could you please tell me how I add a dependency? There is something that I am missing there?
Thank you
Adding the location http://download.eclipse.org/releases/oxygen/ to your target platform should fix the errors.
I've been using Eclipse for programming and testing Storm just fine, however, I created an SVN account, where I commit the project, and for that, I needed the SVN plugin for Eclipse. It worked, but after that, i get this message on a popup error window when I try to launch:
Referenced classpath provider does not exist:
org.eclipse.m2e.launchconfig.classpathProvider
I realised that in the "configure" menu, the option "convert to maven project" (right click on project) disappeared. The "runAs" options for the java topology doesn't run with this error, and the "pom.xml" cannot be run as maven.
Possible fix tried:
I tried to reinstall all maven builders to Eclipse(it doesn't let me to unninstall).
I tried to rebuild config by:
mvn eclipse:clean eclipse:eclipse
None of this worked, my Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Mars.1 Release (4.5.1)
Build id: 20150924-1200Eclipse Java EE IDE for Web Developers.
On Ubuntu Gnome 14.04.
As I said, it was running perfect until I installed SVN plugin.
EDIT
I realised that I have installed two plugins of m2e:
Maven integration for Eclipse (Luna and newer)1.5
Maven integration for Eclipse (Luna)1.5.0
Both in marketplace, but I have no way to uninstall them, it says:
[plugin] cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled.
EDIT 2
In the "Installation History" within the "Help>Installation details" menu, I saw that "Maven integration for Eclipse (Luna)1.5.0" was installed by (or with) SVN plugin, so I think the problem is there, nevertheless, I can't uninstall it as I said in my first "EDIT".
If anyone has a clue about what is happening, please, help me.
Thanks in advance!
We use Subclipse in Eclipse (Kepler and Mars) without problems (Did you install Subclipse or Subversive?).
To check out projects as Maven projects, you should install a m2e connector. Subversive has one in the "Discovery" catalog while for Subclipse there is a separate update site.
If your eclipse plugin configuration is somehow broken, I would start again with a virgin eclipse (Mars.1, Mars.2 or Neon) which already contains m2e in version 1.6 or 1.7. Then you can install Subclipse or Subversive and try again.
Workaround proposal: simply don't deal with SVN within eclipse!
Instead, you can use "git svn" on ubuntu.
Meaning: with git svn you can create a local git repository, that allows you to commit/fetch to a remote SVN server. But to your eclipse ... that repository looks a common of garden GIT repository.
In other words: using that tool, you can still connect to SVN (although I don't understand why anybody would want to do that in 2016); but you have all the features of git available to you as well (including full support within eclipse; without installing any additional plugins).