Red Hat Bugzilla – Bug 986160
eclipse-platform: Move directory ownership to a different subpackage
Last modified: 2014-01-12 19:28:04 EST
Description of problem:
Currently eclipse-platform owns /usr/share/eclipse/dropins directory. This means that any package installing files under this directory needs to require eclipse-platform.
IMO this is really bad thing. I am packaging some Eclipse plugins which can be used outside of Eclipse and they shouldn't pull in the whole platform just for directory ownership.
I would suggest either creating a lightweight subpackage of eclipse (like eclipse-filesystem) without any requires, which would just own these directories, or moving ownership to filesystem package.
Version-Release number of selected component (if applicable):
Aether and Sisu are both Eclipse plugins, but also dependencies of Maven. If they require Eclipse Platform then Maven will require it too, which would be a really bad thing.
/usr/share/eclipse is not owned by any package. It should probably be owned by eclipse-filesystem too.
If it's a plugin it needs the platform. If it's installed in /usr/[lib|lib64|share]/eclipse it must be plugin.
I'm not willing to see non-eclipse things in these directories as they are crawled on startup of eclipse so this slows down startup.
The right approach is for sisu/aether/etc. to be installed in _javadir as regular jars and if needed a subpackage symlinking them eclipse specific dirs like done in findbugs-contrib.
Also are Aether and Sisu eclipse plugins or OSGi bundles? I think it's the later and OSGi bundles are not put in eclipse dirs unless needed by plugin (all the apache-commons* ane others).
I agree with Alex here:
dropins is scanned on startup by Eclipse, and only Eclipse plugins should get there.
A situation where installing maven or maven deps changes Eclipse installation is undesired.
Jars that need to be available both as plain jars and OSGi apps may apply following strategy:
* jars go into /usr/share/java and are symlinked as needed into dropins and/or /usr/lib64/eclipse/plugins by *other* (sub)packages
* goes into /usr/share/java
* symlinked by Eclipse platform into /usr/lib64/eclipse/plugins
* located in /usr/share/java/jacoco
* symlinked by eclipse-eclemma into /usr/share/eclipse/dropins/eclemma/eclipse/plugins/
If you have exactly the same jar that needs to be available as an Eclipse bundle and a plain jar, I'd recommend creating a subpackage (*-plugin) with a symlink.
I'll add the owhership to /usr/share/eclipse
OK, I understand that now.
eclipse-4.3.0-3.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing eclipse-4.3.0-3.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
eclipse-4.3.0-4.fc19 has been submitted as an update for Fedora 19.
eclipse-4.3.0-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.