After installing STS successefuly on Juno, i opened a new MVC project, fixed the errors in the sample STS project by adding all the required spring jars, and now there are 2 problems:
I can't get the option: "Run on server" (altough i did set a tomcat's server in the workspace).
With every step i make (clean, delete etc') i'm getting the follwing error:
Errors occurred during the build.
Errors running builder 'Faceted Project Validation Builder' on project 'First_STS_Project'.
Could not initialize class org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
Errors running builder 'Validation' on project 'First_STS_Project'.
org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
This is not a local problem on my specific workspace, because i getting the same error in my second PC as well.
I don't recommend JUNO since it has many bugs and it also has a bad impact in performance. If you're in Windows, try to use short paths when installing the plugins or selecting the workspace. I have similar issues when working in windows. If I create a workspace in c:/users/Marcelo/Documents/java/workspaces, I always get issues, but whenever I change to "c:/workspaces" directly, works perfectly. Try with Eclipse Indigo instead. Also try to use the latest version of tomcat. If any of the previous recommendations fix the issue, (that could be weird), try to install the STS plugin again but check all the features, maybe a component is missing.
Related
STS is showing an "useless" error when trying to create a new project. I did chose to ignore it and it did not cause any issues with the build , however just to nitpick , I would like to find a way to fix this error.
I have already tried setting the maven configurations within Eclipse and it still doesnt work.
I was using the embedded Maven within STS container. On changing the maven directory preferences within STS albeit to one running an older version solved the issue.
I am having slight difficulties as of late with my eclipse installation. Necessary Background information: We decided to use a specific version of the Spring Tool Suite (3.8.1 to be precise) with a specific set of plugins as our common developing environment.
So what we did is this, we fetched the 3.8.1 STS, modified the default config so work with our gradle plugins and then repacked that so it could be easily distributed in our network.
After this, we installed the plugins in one of the clients and then pushed the plugins and dropins folder onto our network share as well, so we could easily update the plugins without having to repack the entire thing every time we decide on a plugin upgrade.
This worked fine on almost all machines, except one, but we this that has something to do with the fact that the user in question has a second version of the Spring Tool Suite on his Computer.
However, roughly 2 days ago, I had to reset my installation because I carelessly updated too many modules and was unable to use the installation history to revert to the previous setting.
After I removed my current installation and purged the workspace, I reinstalled, reimported my projects and tried to work. This went fine until I tried to open a Spring Bean Configuration xml file with the provided Spring config editor - My IDE showed just an empty tab without title or content. After that, I tried to open the same file with any other internal XML editor, all showed the same - an empty tab. When creating a new Java Project, all XML Files are opened and displayed correctly though. But as soon as I try to open an XML file with the Spring Config Editor, I cannot open XML files in that project at all - except with a regular text editor.
Plus, sometimes my workspace gets addled by that so it generates an error and prevents eclipse from even starting.
Does anyone have any idea why this could be happening and what to do against it?
More Specs:
STS Version: 3.8.1
Eclipse Version: Eclipse Neon
Plugins: (all fetched on Jan 11, 2017)
Buildship Gradle Integration
Minimalist Gradle Editor
EclEmma & JaCoCo
SonarLint
Eclipse Metrics
Thymeleaf Content Assist
JBoss Community Plugins
A solution here was to use STS -clean, as that cleanes the data one most often misses.
in this case, it was workspace metadata that seems to have caused the error.
I recently let STS update itself from 3.1 to 3.5 and now I'm getting errors regarding the MatchLocator class. I'm not sure what MatchLocator is, but it appears to be a core Eclipse service.
When I open STS I get 'Initializing Java Tooling' has encountered a problem.
An internal error occurred during: "Initializing Java Tooling".
org/eclipse/jdt/internal/core/search/matching/MatchLocator
After it's open I get an error marker for each applicationContext.xml in each project that says
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/core/search/matching/MatchLocator
No lines are marked, just that it's a "Spring Beans Problem"
When I close STS I get Problmes occurred while trying to save the state of the workbench with details:
An internal error occurred during: "Initializing Java Tooling".
org/eclipse/jdt/internal/core/search/matching/MatchLocator
I've tried downloading a fresh copy of STS 3.5 to a separate directory and each of my workspaces still have this error so I suspect the problem is in the .metadata directory. A couple other Stack Overflow posts have recommended deleting the workspace .metadata or .metadata\.plugins directories and letting Eclipse rebuild them for that workspace but that didn't fix it either.
I'm running on a Mac with these plugins: m2e Maven Integration and associated plugins, Scala IDE, STS and StartExplorer.
Is there a way to restore the missing MatchLocator files?
Fixed this by removing this file in each workspace:
[workspace]/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
Opening STS from the command line (on mac: ./STS.app/Contents/MacOS/STS -clean) and viewing stack traces on startup led me to this answer: https://stackoverflow.com/a/13884461/1637003
Now all the random ways this bug was manifesting itself have gone away: JUnit tests not running, cmd+clicking to open declarations not working, various MatchLocator errors on startup and shut down.
One of the simplest solution for this problem is that we have to launch a new eclipse IDE and again we install STS tool plugin then import your project.
It works well and u get free from errors.
I have a web project working in eclipse juno using tomcat 7 on one machine. I exported this project to subversion, and imported it into a fresh workspace of eclipse juno on another machine which also has tomcat 7 installed. To fix errors, I then set up the runtime "Apache Tomcat v7.0" on the second machine, and selected Projects/Clean/Clean all.
Now, my project has a list of libraries that includes "Apache Tomcat v7.0 [Apache Tomcat v7.0]", under which are listed all the jars in my tomcat installation, including servlet-api.jar, which eclipse is able to tell includes the package javax.servlet.http. However, I have hundreds of compiler errors from my source of the form "The import javax.servlet.http cannot be resolved" etc. Short of deleting and recreating the project (which might fix the second machine, but I worry that it will stop the project working on the original machine) what can I do to fix this?
Correction: the machines are running eclipse juno, not indigo as I previously stated.
If you did a refresh on the tree and a clean/build and the errors still exists, it must be the case, that they are not within the build path (check .classpath file).
So even though you may have checked it before, you should go there again and see if they are on the build path and maybe delete it and include them again.
Additionally, maybe this article about the specific problem helps.
Turns out that this is a fairly simple and annoying but otherwise harmless eclipse bug -- it seems as though the list of libraries that constitutes a particular runtime is cached when the project is loaded, and doesn't get updated if the library list changes (e.g. because the runtime didn't exist when the project was imported, but was created afterwards). Restarting eclipse causes it to reload the list, after which a project clean gets rid of the errors.
I am currently working with a product that is built onto Eclipse version 3.4.2.
I am trying to install the jaxb builder plugin, but it is not working.
So far I have tried:
Unzipping the folder into the Eclipse plugins folder and then restarting Eclipse
The restarting Eclipse using the -clean flag
Unzipping the folder into the product's (built onto Eclipse) plugin folder and then restarting with and without -clean
Unzipping the folder into the dropins folder and then restarting Eclipse
I think that it may be possible that this version of jaxb builder doesn't support my version of Eclipse, but I can't figure out how to find that information. I tried emailing the address on the "Contact Us" page, but it came right back to me.
Is it possible that the product has been discontinued? How can I find out?
Discontinued? I don't know but the last build is from 2011-05. It's built against Eclipse 3.4 (see plugin.xml). What do you mean be "not working"? Exceptions? Entries in Eclipse error log/view?
Turns out it was the application's fault. I'm not exactly sure what the problem was, but when I did the exact same thing in a regular Eclipse environment, it came up with no issues.
I will edit if I get more information.