Eclipse could not detect my maven projects while adding projects in server. The projects icon is not seems to be regular one. PFB the screen shot.
Below are option I tried ,
Right click on project and selected Project Facet and made sure Dynamic Web module is selected and Java modules are checked but could not select runtimes on right side panel as below
- Is this expected behavior ?
Tried to switch other version of Dynamic Web module and reverted back to 3.0
Project build and clean
Restarted many times
Tried with other versions of eclipse
Tried with creating new workspace
Tried with deleting created server and created fresh server
Updated maven projects
Tried with other version of eclipse, 1. Neon, Luna, 2020
But none of the above worked. Has anyone faced similar problem ? if yes could you please help me to resolve this problem?
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 installed eclipse Luna.At that time Maven option was displayed in window-- preferences.Later i install spring ide.After installation maven got disappeared.pls help me to come out of this
Eclipse is well known for working oddly despite the correct settings and configuration. (As most of free IDEs').
Try to click to your project, then Configure and select Convert to Maven project.
Also clicking to your project and selecting the Clean may help since it removes all the files that are generated automatically.
So I upgraded to Spring Source Tool Suite 3.6.2, and I've been having a few problems. The current one is now for some projects I get incomplete context menus:
Some notes:
It's only for some projects, not all
The items that are blank vary, sometimes the full menu shows up
I've tried STS.exe -clean
I've tried deleting the .metadata folder
I've tried changing the theme
It appears to correlate with SVN projects where the Team menu item never shows up
To elaborate on the last point, all 20 or so of my projects are on SVN. For the ones where the menu seems funky (at least on the 5 or so I tested), when I could get the full menu to show up, the Team menu doesn't. This is even on a fresh STS install without SVN Connectors.
I just tested a new install of STS, and things were working fine until after restarting after an install of IvyDE. Ivy is needed for some of the projects, I haven't analyzed the correlation yet. I will try to remove that and report back.
This is also happening for two other people on my team, with brand new computers (and thus, workspaces).
It was IvyDE. Specifically the 2.2.0.final-201311091524-RELEASE version (takes breath). I'm going to try to find a version that works. My SVN stuff is not causing any problems.
Update
I've fixed my issues. I used a development build from the CI trunk build artifact site at: https://builds.apache.org/job/IvyDE-updatesite/lastSuccessfulBuild/artifact/trunk/build/
The versions included were:
Apache Ivy 2.5.0alpha_20141106222552
Apache Ivy Ant Tasks 2.5.0alpha_20141106222552
Apache IvyDE 2.3.0beta1-201409280037-hudson-296
Apache IvyDE Resolve Visualizer 2.3.0beta1-201409280037-hudson-296 (Optional)
Note that I tried just updating IvyDE to 2.5a, but still had issues. Updating Ivy fixed all my issues so far.
I filed a bug with Apache: https://issues.apache.org/jira/browse/IVYDE-377
I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?