https://bugzilla.redhat.com/show_bug.cgi?id=1937950
Phil Wiggum <p1mail2015(a)mail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|high |medium
--- Comment #3 from Phil Wiggum <p1mail2015(a)mail.com> ---
After some testings I would like to change the caption of this bug to:
'Eclipse Plugin Environment is not correct'
If I start a fresh Fedora Eclipse the 'Target Platform' has 574 plugins.
After installing a HelloWorld-plugin (build-ed by 2020-12 from Eclipse) I get
778 plugins.
Removing the HelloWorld-plugin I get 777 plugins.
So now with a little help from HelloWorld-plugin Eclipse has found a number of
plugin belonging to the core of Eclipse.
No there reason why I would like to change the caption.
Another plug-in developed by 2020-12 from Eclipse is not working or recognized
by Fedora-Eclipse at all.
One line in the MANIFEST.MF differ here from HelloWord:
Import-Package: org.eclipse.cdt.ui
I can find that package in
/usr/share/eclipse/droplets/cdt/plugins/org.eclipse.cdt.ui_6.7.1.202006250915.jar
My proposal is that if Eclipse is repacked in a different way as the original
Eclipse the 'Target Platform' must match in all setups.
Some maybe useful stuff for who ever would like to dig in to this.
Monitoring what Eclipse is doing while the scanning take place during startup.
strace -f eclipse 2>&1 | grep eclipse | grep -E 'open|stat' | grep -vE
'\.png|\.bak|\.htm|\.gif|\.log|\.tmp' | grep -E
'/usr/lib/eclipse/plugins"|dropins|/home/user'
Also:
https://wiki.eclipse.org/Equinox/p2/P2_Fragments
I lower this bug to 'Medium' because I'm switching over to the official
Eclipse
version instead.
--
You are receiving this mail because:
You are on the CC list for the bug.