So I have just installed the latest eclipse version (4.6.3) on my laptop which had 4.6.2 running before.
The problem is that all my eclipse plugin projects are now full of errors because it somehow can't resolve various bundles (swt, osgi, eclipse.core, eclipse.ui, etc).
Furthermore I have noticed that the target platform the PDE sets up as default (which is the running platform) complains that it can't find the respecive plugins either.
I don't know if these two issues are connected but it seems to me that eclipse can't find it's own plugins which would be very weird...
Does someone has an idea on how to fix this?
Related
enter image description hereI have been trying really hard to configure a pipeline debugger in eclipse. After using my digital server account in server configuration when i select my site and click 'Debug' button it gives me an error
Could not initialize class com.thoughtworks.xstream.converters.collections.TreeMapConverter
I couldn't find much help online. I even tried changing the JRE version to an older version 14.0.2 but it doesn't seem to help.
[![Image attached of error][2]][2]
enter image description here
That library seems to be a core component of the Pipeline editor. I would suggest that you ensure that your Eclipse version is compatible with the plugin if you haven't done so already.
Currently, according to the documentation it only supports:
Mars - Eclipse 4.5
Neon - Eclipse 4.6
Furthermore, you must install the correct version of the plugin for your version of Eclipse. (Though in the past I've found that older plugin versions may sometimes work in newer Eclipse builds.)
This error relates to discounted class from JRE.
So my recipe for solving the issue:
used OpenJDK v11
installed latest eclipce version
SFCC plugin v4.6
Some found issues:
with new eclipce version brakepoints are not set from JS editor only via ScriptEditor
Thank you,
Aleksandr
I had issues with running debugger, but after I installed eclipse version 2020-12 and installed UX studio plugin it started to work. maybe new versions are not compatible with plugin
I've a really strange problem here with eclipse ... I've defined a target definition within my eclipse and set it to be the active target platform.
After my workspace has been built eclipse complains about that it cannot resolve the bundle javax.inject although I can find it in the target platform ...
Here a screenshot from my target platform with the "missing" plug-in:
The strange thing is now that I also cannot find it in the run configuration as this screenshot clearly shows:
In my manifest where I've a dependency to this plug-in it also says that the bundle cannot be resolved, but when I double-click on the plug-in it opens and says that the plug-in can be found under the following directory: \.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\plugins
I've struggled all day long to solve this problem, but I couldn't find anything out except that this problem seems to occure with eclipse Juno only ... I've installed eclipse Luna and with this version it works well, but our default IDE is Juno so it needs to work with this version as well ...
I've absolutely no idea what is going wrong here because I always thought the meaning of a target platform is exactly this to resolve such dependencies between different kind of eclipse versions ...
I have RTC version 4.0.3 on a Windows 7 system. I would like to install some plugins like PMD, FindBugs, Checkstyle etc. to keep an eye on my code. Are they compatible with RTC?
I've tried installing some and they fail. FindBugs installs successfully, but it's nowhere to be seen in RTC!
Any ideas?
Looks like it's a known issue. Having RTC installed under "C:\Program Files (x86)" causes permission issues. I reinstalled into my home folder and plug-in installation works (although not for Findbugs strangely; PMD and Checkstyle are fine).
Check the different Eclipse perspectives: your plugin could be visible in the Java perspective, while being not available in the RTC one.
I have a maven plugin that transforms class bits after compilation. This plugin works precisely as designed when run from the command line. However, the problem arises in Eclipse (3.6.1) when the Maven project is building from a clean state. What happens is that I get an error message in the console informing me that my plugin has failed due to the inability to find a class that is in fact on the classpath.
As I mentioned, this plugin works perfectly well when I build from the command line, so this is a rather annoying problem that seems a bit difficult to track down.
Has anyone else ran into this problem before, and if so, is there a solution that I'm missing?
Thanks.
I can confirm that the maven eclipse plugin sometimes works different than the "console version". You can try to change the "Preferences->Maven->Installations" to your external maven installation (that what you use when running from command line). The eclipse plugin embedded version is a 3.0-SNAPSHOT (in my installation) and maybe not stable in all points.
The issue turned out to be a difference between Maven 2.x and Maven 3.x. The m2eclipse was using a version of Maven 3.x - can't remember which - and I was running a previous version. Apparently, somewhere in the version range, the plugin mojo now requires #requiresDependencyResolution . Thus, when running in m2eclipse, my plugin was not getting any of the dependencies in the project, and thus the class path was completely boned...
word...
Since adding the Blackberry Java classes from their website into eclipse, I've had it where eclipse will randomly close, with no discernible pattern, rhyme, error or reason. Here is the environment/software packages that I am using:
Windows XP SP2
Eclipse v3.5.1
Blackberry Java Plugin v1.1.1.200911111641-15
Blackberry Java SDK 4.5.0.21
I've tried the usual steps of complete uninstall and reinstallation of Eclipse and the accompanying plugins on multiple systems with the same configuration, including one that had a fresh install of Windows XP SP2. Upgrading to Eclipse 3.6 didn't work (the plugin wont' install as it's the wrong version), nor the downgrade to 3.4 for the same reason. I also increased the heap size to 512 (system has two gigs of memory) as some research into Eclipse doing this type of thing with Groovy was resolved that way, but again, no dice. Eclipse works great when the blackberry plugins are not installed, and no entries of errors or issues in the event log are helping to show what the issue with these plug-ins might be.
So if anyone has ran into this issue, and even better, has a solution, I'd love to hear about it. Thanks in advance.
EDIT: An additional to my issue, autoComplete with the Blackberry SDK seems to make this extremely unstable, like almost a guaranteed crash. Is this fixable at all?
For anyone that loads this question up trying to find a solution, I've never found a fix. It seems to be a bug with this version of the IDE. If there is a fix, please post.
Did you try to downgrade Eclipse to 3.4 (Ganymede)? I experienced similar issues when I tried upgrading Eclipse to something greater than 3.4.2.
I think the problem is with the plugin, not the IDE. Eclipse has always been stable for me until I installed the BB plugin. Since then it crashes all the time. Since I've installed the release (non-beta) version of the plugin that was recently released I can't even get my project to build.
This could be a manifestation of this bug in Eclipse. Check your C:\eclipse directory for files like hs_err_pidxxxx.log. The file goes on to explain this error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x753ba053, pid=3144, tid=5820
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [USP10.dll+0x1a053]
I've been experiencing this as well. It's completely debilitating. It causes Eclipse to just up and crash out of nowhere (and programming in a language as verbose as Java without Content-Assist is insane).
The bug has been fixed in Eclipse 3.6M7, but unfortunately I can't get the JDE Plug-in to install in the latest release candidate.
This is a known issue with Eclipse 3.5.X and has been fixed for 3.6.0
Bug Ticket link on Eclipse Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283503
Looks like we are stuck with this until the next update to the BB Eclipse plugin.