OS: 64x Windows 7
IDE: IntelliJ IDEA 12.1.4
After activating the plugins log4j and IdeaSpring, IntelliJ wants to restart itself. While restarting IntelliJ, there are 2 messages which prompt that either log4j and IdeaSpring couldn't be initialized.
How can I set up my IntelliJ that those 2 plugins work?
Messages:
Plugin IdeaSpring failed to initialize and will be disabled:
Could not load API connector for IntelliJ IDEA build #IC-129.713
Please restart IntelliJ IDEA.
and
Plugin IdeaSpring failed to initialize and will be disabled:
com.intellij.javaee.ExternalResourceManager.addStdResource(Ljava/lang/String;Ljava/langString;Ljava/lang/Class;)V
Please restart IntelliJ IDEA.
IdeaSpring is a third-party plugin which wasn't adapted to the API changes in IDEA 9 (note that it hasn't been updated since 2006) Please report the problem to the plugin vendor (http://www.yanaware.com/)
BTW, Intellij Idea has its own Spring support - why do you need using third-party plugins?
The answer to the question is: you shouldn't. The plugin you're trying to install IdeaSpring) is from 2006. You should use the Ultimate Version of IntelliJ, which has excellent Spring support. The free version doesn't.
The same for the other plugin; it's also very old, and probably doesn't work anymore. I'm not sure if you need that one, since IntelliJ also has support for most of the XML log4j provides.
I'd say: try the Ultimate version, and either buy it or try to get a free version if you're working on a Open Source project.
Alternatively, if you can't spare the money, you could have a look at SpringSource Tool Suite, which is pretty decent too, but at least it doesn't cost money, and it does have support for Spring.
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 have installed Apache Netbeans IDE 10.0 on Linux Mint, and followed this recommendation to activate JEE support ( https://superuser.com/questions/1404517/how-to-enable-java-ee-in-apache-netbeans-ide-10 ). I have restarted Netbeans and JEE annotations are marked as errors "Incompatible types : Path cannot be converted to annotation". This happens with all Java EE annotations, and I don't know how to solve this.
I have tried to do clean and build but still the same. Here is a screen shot of some sample errors:
You are having problems because the solution you followed for the accepted answer to the superuser question How to Enable Java EE in Apache Netbeans IDE 10 is wrong.
That answer advises you to use an Update Center to download some plugins used in NetBeans 8.2. That was an appropriate workaround on NetBeans 9, but wrong for NetBeans 10 since the appropriate plugins you need are already available (on the Tools > Plugins > Available Plugins tab), and you just need to install them. You don't need to obtain any plugins from any Update Center for Java EE, and doing so will probably be harmful.
See this SO answer to the SO question How to create Web Application in Apache Netbeans 10? for details on which of the available plugins need to be installed.
Notes:
I think you should first reinstall NetBeans 10 if possible, to start with a clean environment.
If that is not possible you should first uninstall those NetBeans 8.2 plugins you added to NetBeans 10, and then restart NetBeans.
Although the SO answer I linked to is for a slightly different question, the solution applies equally to your problem.
Although not related to your question at all, you might consider also upgrading to Apache NetBeans to version 11.1 if that is possible. If you did that you would still follow exactly the same process detailed in the linked answer for installing the Java EE plugins.
I just downloaded the latest Spring Tools 4 package, 4.3.2 RELEASE. My code base makes widespread use of AspectJ, and every time I try to import a project, I get a "Marketplace solutions available" dialog saying my IDE is missing natures to properly support my projects. It offers org.eclipse.ajdt.ui.ajnature as a solution, but the marketplace won't install it. When I try to access it directly through the Eclipse marketplace in my browser, I get an error dialog saying it's not compatible with this version of Eclipse. I'm using Java 11 on Linux. It's a little hard to figure out which version of Eclipse is embedded in this tool, but it appears to be Eclipse Equinox. Thanks for any help or suggestions.
The link provided by howlger http://download.eclipse.org/tools/ajdt/48/dev/update was the missing piece of information. That solves the problem, everything builds.
I'm rather new to IntelliJ IDEA and Grails in general. I just started a new Project, selected my project JDK (11.0.1) and Gradle distribution (4.10.2). Whenever I try to run the project, I get this error:
Error initializing classpath: Could not determine java version from
'11.0.1'. java.lang.IllegalArgumentException: Could not determine java
version from '11.0.1'. at
org.gradle.api.JavaVersion.toVersion(JavaVersion.java:68) at
org.gradle.api.JavaVersion.current(JavaVersion.java:78) at
org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(UnsupportedJavaRuntimeException.java:29)
at
org.gradle.tooling.internal.consumer.ConnectorServices.checkJavaVersion(ConnectorServices.java:66)
at
org.gradle.tooling.internal.consumer.ConnectorServices.close(ConnectorServices.java:53)
at
org.gradle.tooling.internal.consumer.DefaultGradleConnector.close(DefaultGradleConnector.java:57)
at
org.grails.cli.gradle.cache.CachedGradleOperation.call(CachedGradleOperation.groovy:78)
at
org.grails.cli.GrailsCli.populateContextLoader(GrailsCli.groovy:525)
at org.grails.cli.GrailsCli.initializeProfile(GrailsCli.groovy:508)
at
org.grails.cli.GrailsCli.initializeApplication(GrailsCli.groovy:306)
at org.grails.cli.GrailsCli.execute(GrailsCli.groovy:269) at
org.grails.cli.GrailsCli.main(GrailsCli.groovy:159)
All other discussions of the problem I found suggested changing the Gradle distribution, which I already did. I would be so happy if anybody could help me out here.
Cheers!
May be your java configuration is not correct. If not correct follow this steps.
Goto File-> Project Structure.
Change SDK
Or gradle version is not matching jdk 11 then skip this answer.
Besides the issue with Gradle above, if you're trying to run a Grails project I don't think you can do that with JDK higher than version 8.
Even the latest Grails (3.3.8 as of this writing) is still based on SpringBoot 1.5 which does not support newer JDK, I don't know if there's a special trick to make it work.
I had to delete the .gradle directory and restart Intellij.
I use Eclipse Indigo for java development but I want to experiment with scala. Since I have to download a nightly build to run on Eclipse : http://scala-ide.org/download/nightly.html is this safe ?
Is there a chance the plugin can corrupt my eclipse installation since the plugin is not a full blown release as yet ?
I run the latest Scala milestone with no problems right now, which is probably safer than the nightly, and has better highlighting features. If you do run into trouble you can always revert to a previous installation state in Eclipse, so I would consider it safe
The plugins architecture is designed so that Eclipse is protected from instability, unless they maliciously delete files on your installation, I doubt they would break Eclipse permanently. To be extra careful you can make a backup of your eclipse directory.
Nighly builds gives developers a chance to use latest features (not certified to be working on all environments) of the plugin which are not yet made available to end users. In general they work fine but there may be few undiscovered issues. You can always rollback your installation if something goes wrong or if you find any bugs.
If your aim is to learn or develop using scala, better to use stable build. A stable scala-ide plugin is available for Eclipse Indigo. Please visit 'http://scala-ide.org/download/current.html' for more details.