I have a local Eclipse RCP project on my Windows machine. One of my remote repositories is used for development and the other for staging during release. The tools used during build and release are Maven, Git, SSH and GitHub. I can build and run tests without any issues: but when I perform a release prepare: I end up with
Tag: eclipse-rcp
Why can’t Maven Tycho find the correct JDK in toolchains.xml?
I have made a simple RCP application to test Maven builds. My question is why Maven Tycho can’t find the JDK’s defined in the toolchain and how can I fix those issues? My RCP plugin uses JDK-15 and I believe that the target-platform brings the dependencies to JDK-11 and JDK-16. I run ‘mvn clean verify’ and everything seems ok except
NullPointer when Injecting eclipse Services in e4
Quick version for the impatient: When starting an Eclipse RCP Application a Part in a plug-in throws a NullPointerException because the following lines did not seem to work, as partService seems to be …
SWT DateTime – read date and time from two widgets
Imagine two widgets: and Would would be the most efficient way to read date and time from the two widgets into a single Date variable? Edit: The following solution that I have in mind is far from being elegant. I hope that there is a better way to do this. Answer For Java 8 and later you can use LocalDateTime:
Eclipse plug-in: Custom plugin.xml like editor
I’ve been trying to mimic the plugin.xml editor in my own Eclipse plug-in. I want a graphical editor for a custom file type. The same way in which PDE has a specific form/editor to open plugin.xml. From what I understand I can implement a text Editor and link a file type to open in a particular editor. To add a
Eclipse Memory Analyzer – Leak Suspects Report doesn’t point to MY classes – why?
I’m trying to determine whether or not I have a memory leak in my webapp. I’m using VisualVM and JMeter to load test and watch the heap. I saved a heap dump to file and downloaded Eclipse Memory Analyzer yesterday…after much frustration with VisualVM, I thought Eclipse would pinpoint the leak, if any, better than VisualVM. I opened the heap