Open AndrWeisR opened 3 years ago
I am not sure which Eclipse versions you are referring to, the last 3.x version is 3.8 (Juno) Or was it a typo and you are talking about Eclipse 2018-12 (4.10)? ECD should work in Eclipse 2018-12. https://en.wikipedia.org/wiki/Eclipse_(software)
If you only build the ecd-plugins, and not the ecd-features and adapt the minimum version for the Eclipse dependencies in each pom.xml
it may work. Also some apache commons plugins may be missing in older Eclipse versions, you would have to manually install them.
My mistake - it's Eclipse 4.4 (Luna). We're using a tool built on Eclipse.
I don't know if any relevant API has changed between Luna and Photon (oldest supported Eclipse version by ECD at the moment).
By modifying the dependencies in pom.xml
and META-INF/MANIFEST.MF
you may be able to build an ecd version that works in your Eclipse version.
So you are using the old Eclipse version because you use this Eclipse version for developing that tool? Or is the tool pre-compiled and integrated into Eclipse?
If you are developing an Eclipse based tool you can define an external Eclipse installation as Target Definition
that is used for getting the OSGi dependencies for a plugin project as well as for starting a plugin?
This allows to develop using a recent Eclipse version based on an older (or newer) Eclipse version.
@jpstotz I had the same issue that I am still using a outdated version of eclipse. (Because frankly there is some bugs in newer versions that I just don't like)
But I managed to install this plugin again fairly easily.
here is some step by step instructions how I did it:
We're stuck by corporate bureaucracy on Eclipse 3.10, where some of the decompilation results don't work very well. The latest ECD won't install on Eclipse 3.10. Is it possible to make ECD backwards compatible to older Eclipse versions?