On Mon, Mar 18, 2019 at 3:20 PM Mat Booth <fedora(a)matbooth.co.uk> wrote:
Eclipse in Fedora has dropped support for 32 bit architectures. The
newest builds of Eclipse 4.11 for F30 and newer reflect this and are built for 64 bit
architectures only.
By now I have touched most Eclipse plug-in packages to limit their availability to the
same architectures as Eclipse itself. If you own a package that is not an Eclipse plug-in
but it does have a build or runtime dependency on Eclipse, then you will need to follow
suit and make your package also exclude 32 bit architecture. If your package simply
depends on Eclipse/Equinox for OSGi APIs, then you might be better switching your package
to build against the OSGi APIs provided by the osgi-core/osgi-compendium packages instead
to stay available on all architecture. Feel free to ping if you are unsure how to proceed.
I'd like to follow up on this. Right now many Java packages fail to
install and/or build on 32-bit arches (primary and secondary) in
Fedora 30 and rawhide to install or build.
For example, for Apache Log4j (one of basic libraries that many other
packages depend on):
Problem: package log4j-2.11.1-3.fc30.noarch requires
mvn(org.eclipse.persistence:javax.persistence), but none of the
providers can be installed
- conflicting requests
- nothing provides mvn(org.eclipse.osgi:org.eclipse.osgi) needed by
eclipselink-persistence-api-2.1.0-7.fc30.noarch
Java modules (maven, ant, javapackages-tools) are not affected by this
issue and they continue to work and build on 32-bit arches.
--
Mikolaj Izdebski