I have uploaded my Eclipse project to BitBucket and decided to test how the cloning function works as I am quite new to using repositories. So I deleted the project from Eclipse and then used the "Clone a Git Repository" function to import my project back into Eclipse which worked correctly. However, there are now a few errors that pop-up in my code (errors that did not exist before) and I am trying to figure out what is causing this. Specifically:
- The method getSubmittedFileName() is undefined for the type Part
- The type ActiveSessionListener must implement the inherited abstract method HttpSessionListener.sessionCreated(HttpSessionEvent)
I thought it might be caused by using an older version than Servlet 3.0 but that doesn't appear to be the case (it's configured to Servlet 3.1 as shown in the screenshot below). What could be causing these unexpected errors in my code and how can I resolve this?
From this question, this is a Tomcat version issue.
Do check your Targeted Runtimes and Java Build Path, in order to reference Apache Tomcat v7.0.
Related
I got a project from GitHub which is a Java spring boot application running with Maven dependencies.
I am so confused why I can't run the application successfully on STS.
There's no longer a problem on my old laptop. Because I just changed my laptop, this problem only occurred on this laptop.
The details / symptoms of the issue are:
When I typed "SpringToolSuite" on my start panel, no applications were being recognized. So I have to open STS manually from Downloads (ie. its original file location). But anyways, it is just a minor issue.
In STS, annotations such as the lombok log and most of the getter/setter methods were unrecognized.
Failed to perform "Run as Spring Boot App" from STS, but it is successful when I tried to perform "mvn clean install" to create a Maven build from command prompt.
Error message: "log cannot be resolved"
I tried finding results from other posts here but to no avail.
The steps that I import the project is:
Create another folder as the workspace.
Open STS by selecting the created folder as the workspace.
Click File > Import and import as existing Maven project (as it is a Maven-built application).
I also tried to create a Maven build from command prompt, which is successful eventually.
As the situation was so strange here, please advise further what I can do. Thanks.
Lombok has a plugin for Eclipse (and therefore STS as well) that enhances the IDE with direct support for Lombok: https://projectlombok.org/setup/eclipse
Without that extension the IDE is not really able to recognize and support Lombok.
Thanks so much for your suggestions.
First of all, I've made sure my STS the latest version. I installed it from the official site https://spring.io/tools.
I downloaded the Windows one. See image.
I executed the spring-tool-suite-4-4.16.1.RELEASE-e4.25.0-win32.win32.x86_64.self-extracting.jar file afterwards. A folder with STS application inside has been generated.
Referring to your second question, I am sure I have the lombok dependency.
This is part of my pom.xml. See image.
I also performed again the "mvn clean install". It is success and error-free.
Fyi, I also make sure every setup is right, such as:
It is pointing to the same java version as what Maven points to.
In STS, the Java compliance level is the same as the java version I defined in PATH environment variable.
Also in STS, the Installed JRE is pointing to the right folder.
But as the STS is still not recognizing Spring Boot annotations. That's why it seems weird here. For example, logs are underlined red with an error message on the IDE. Getters and Setters of #Data fields are not implicitly referenced with that spring boot annotation since they're also underlined with error.
Just starting working on an existing project at work and wanted to use Visual Studio Code as my IDE (I have used it for a recent Rails project and loved it, so wanted to try with Java).
However, whenever I try to open one of the projects I receive a ton of different errors including:
When importing java.io, java.util, or anything similar, the error:
"The import of java.io (or java.util) cannot be resolved"
Existing classes have an error:
"The implicit super constructor is undefined for default constructor. Must define explicit constructor"
Other random "cannot resolve to a type" errors.
All of these seem to stem from some sort of setting error I have with VS Code but can seem to find what it is. I have already uninstalled and reinstalled the RedHat plug-in that enables the Java language for VS Code.
I have tried setting the java_home setting in the extension to the direct location of the install but that didn't work. Tried uninstalling and reinstalling java and that also didn't work.
My operating specs are as follows:
OS: macOS Sierra
VS Code version 1.15.1
JDK version 1.8.0.144
Any idea on what may be causing this? Do you think it may be an error in how I have VS Code set up or if it's an error (or rather incompatibility) with how the existing project is set up?
I ran into a similar issue. The solution was to remove everything from VS Code's workspace storage directory, which was located at $HOME/Library/Application Support/Code/User/workspaceStorage/.
I found this solution here: https://github.com/redhat-developer/vscode-java/wiki/Troubleshooting#clean-the-workspace-directory
Update: This can now be done from within VS Code as of Language Support for Java(TM) by Red Hat Version 0.33.0. Open the command palette and type "java clean" (see official description in link).
As already mentioned previously, you require to clean the project, but that is a bit difficult thing because every folder is a Guid, and you do not know which one to clear, thus requiring you to delete everything. Starting with 0.33.0 version of the plugin you can automatically do that from within the IDE as well, use CTRL + Shift + P and type, java clean, and IDE will show you the suggestion tip for, Java: Clean the Java language server workspace. Upon selection, agree and restart the IDE. It will clean the language server workspace for you.
Another approach can be, the Maven tools within the IDE. If you have this plugin installed, you can use the side bar and utilize the Maven project helper options to perform actions like, clean, install, and package etc. For example, here is the project I am having and the options this shows,
That can be used, graphically, to manage your Maven-based projects. Also, this would work with the Java Extension Pack, not sure yet as to how it would behave with other extensions.
For me: CMD + Shift + P
Then type "Java: Clean Java language Server Workspace"
Note: This will reload/restart vscode as well.
Update:
This appears to not fix it anymore for me. In my case I am using a gradle project, and needed to set the rootProject.name in the settings.gradle to be the same as the folder name that the project is in.
I faced this issue after creating a whole Java project in one computer and then trying to run it on another computer.
After doing everything said in the other answers, what really made VS Code compile was to open each single project java file in VS Code and save it (a simple Ctrl + S). Maybe there is a simpler way of doing it, but that is what worked for me and I hope this helps anyone stuck in this issue.
Press ctrl+shift+p
then search 'java clean' and click 'java: clean java language server workspace' then click restart IDE.
I found another simple trick at least to get rid of "cannot be resolved to a type" errors which were coming from older workspaces and wrong project files I guess?. I just ran an empty main(), with the body commented out, while still keeping my local package / import commands at the start - no errors. After commenting in again, the project compiled without errors. Perhaps this refreshing effect might also help in this context?
I had to clean this folder to get it working on Windows
%APPDATA%\code\Local Storage
Specs: Linux Mint 18.3, Eclipse 2019-06, Groovy 2.5.8, Java 11
I started a Groovy project, and created a package "test" under the "source folder". Under test I put a file, "test.groovy". This file looks like this:
package test
It's got a horrid white-cross-in-a-red-box. The error message is:
Multiple markers at this line:
- The type groovy.lang.MetaClass cannot be resolved. It is indirectly referenced from required .class files
- The type groovy.lang.GroovyObject cannot be resolved. It is indirectly referenced from required .class files
I have tried multiple strategies: restarting Eclipse, cleaning the project, removing and putting back the JRM for the project. Nothing doing.
There are a few cases of this error when I Google, but mostly they appear to be from years and years ago, on an active bug list, so I presume resolved.
Any ideas what's going wrong?
NB according to my notes, I have had this problem before a couple of times with Gradle projects, and the problem was resolved by going Gradle --> Refresh for the project. But this is a (pure) Groovy project, not Gradle, and the "Refresh" option is not available.
By the way, when I look at this problem in the "Problems" the error type is said to be "Java Problem".
later
It's been suggested that the cause might be Java 11. This is an interesting idea. However, Groovy 2.5.x in itself is not incompatible with Java 11. Firstly, I have no problem running this at the CLI, and no problem with Eclipse-based Gradle projects configured with Java 11 and Groovy 2.5.x, using Groovy as the language of the app and testing files. Crucially, of course, the Gradle wrapper chooses its own Groovy version, and in such circs the user chooses their own Groovy version for their executables as a dependency in build.gradle. So Eclipse Groovy-handling is mercifully "bypassed".
I am thus beginning to suspect that the Groovy-Eclipse add-in may be the culprit. Amazingly enough, and I was surprised by this, I downloaded and set up the 2019-12 Eclipse package, completely separately, and tried to create a Groovy project in it. Even after several attempts to install both the "release" and "snapshot" versions of Groovy-Eclipse for this version of Eclipse (i.e. here), I cannot start the simplest of Groovy projects in that IDE.
So my suspicions are circling around this theory that Groovy-Eclipse is unable to work properly with Java 11. Only problem is that you might expect to find such a bug as one of the issues, but there is nothing.
Add "requires org.codehaus.groovy;" to your module-info.java
I'm trying to do some modification to the service layer of my portlet (e.g adding a column or a finder to a table in the service.xml). No matter what I do, when I build services it all goes good(no errors) but when I try to deploy or make the war, many errors appear. In this case I was just adding a new column (note2) to an already existent table
The method getNote2() is undefined for the type ESFShooterAffiliationChrono
or this:
The method getNote2() of type ESFShooterAffiliationChronoModelImpl must override or implement a supertype method
I'm working on Eclipse Luna 4.4.0, liferay IDE 3.1.2, Java JDK 1.7.0 67. I've set Compliance to 1.7 in eclipse and both "ant.build.javac.source" " ant.build.javac.target" to 1.7 in build.properties.
I think there must be something wrong with the service builder. I tried starting over with a new workspace and a fresh Plugin SDK, even with the 6.2 GA6 but with no avail. I've also tried deleting all generated service class before doing the service build but without success.
Can you give me any advice on how to solve this?
Most likely, you have some old code around and embedded in your dependencies. Search for a -service.jar named after your plugin, e.g. your-portlet-service.jar.
This might also happen when both a your-portlet-service.jar and the WEB-INF/services folder are on your build path. The compiler and the editor might pick up different versions. And when you build through Ant, Ant might pick a third variation for the precedence.
Check your eclipse and your Ant build path.
I get this error during compile-time of my GWT project, there is no such folder as 'gwt-UnitCache' to delete, as suggested in the following questions
Weird GWT compile error
exception in GWT RPC app
I'm using IntelliJ IDEA (IDE), SmartGWT EE (Framework), JBoss AS (Server) and JPA
Here's the error log:
If you change the value of your <module rename-to='<appname>'> in .gwt.xml it will give the same error :) but then you can just delete your gwt-unitCache and all is ok :)
IntelliJ IDEA stores GWT cache files in other location than <ProjectFolder>/gwt-unitCache, which is a default directory for a cache if you are using, for example, Eclipse with GPE (Google Plugin for Eclipse).
In IDEA, GWT cache should be located by default at <your_home>/.IntelliJIdea12/system/gwt (IntelliJ IDEA 12, Linux). For other operating systems you can check Project and IDE Settings.
If you delete mentioned gwt folder contents, IntelliJ will create a new cache, which in turn might solve your Failure in unit cache... (and similar Unable to read from byte cache) problem.
I had the same problem with Eclipse.
Unfortunately looks like the only solution is the one given by Crowlix.
I tried to delete gwtCache and Temp files, but nothing worked.
The problem only got fixed when deleting the entire project and re-importing it.
I was able to fix it by systematically removing, compiling and re-adding every artifact piece.
If you're having this problem, make sure you have a structure like this:
lib contains your compile-time libraries
I am face off this same error, this tip doesn't works for me, moreover, I keep about looking for a solution, and finally, I got this advice:
Java stack overflow error
I tried with -Xss1m, but the error persists, I keep on trying, my final value was -Xss5m
I am using GWT 2.5.1 and IntelliJ 12.
I've got same problem building a project with maven.
Usign both suggestion of Nishant and #iVieL:
$ export MAVEN_OPTS="-Xms512m -Xmx1024m -Xss32m"
$ mvn clean package
you must clean your project first (Project -> Clean)
then remove /gwt-unitCache
then rebuild it.