Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-releng] Oh no! Build breaks from Eclipse Platform bundles usage of new language constructs and your plugins

A number of our builds post-M1 have started to fail because bundles are targeting J2SE-1.4 and calling code that explicitly uses newer classes and language features. Here’s Aleksandar’s email about it, explicitly mentioning one of the problems we’re seeing now. Whether you’ve been getting notices about it or not, please check and take corrective measures as quickly as you can.


Keep in mind that although your dependency ranges may go very far back, we’re neither building nor explicitly testing on those releases. Keep this in mind as you get your builds out of the red.


Nitin Dahyabhai



From: <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Thursday, October 17, 2019 at 9:15 AM
To: "issues, Cross" <cross-project-issues-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [cross-project-issues-dev] Eclipse Platform bundles usage of new language constructs and your plugins


Eclipse Platform starts using more and more new Java constructs (up to Java 8 for now) like try-with-resources, foreach and etc.

Bundles have their minimal versions bumped whenever BREE has been bumped so one can have clear indicator of this change.

This new features bring dependency on new classes like AutoClosable ( Java 1.7) , Iterable (Java 1.5) and probably others.

If your bundles have BREE lower than the Platform bundle they depend on and you have JVM of that level configured in Eclipse errors like "The type java.lang.Iterable cannot be resolved. It is indirectly referenced from required .class files" could be shown.

This is source level only issue if you try to build your old bundle against latest platform. People just using their prebuilt bundles won't face anything like this.

Possible fixes for this issue are:

* move your bundle to newer BREE (highest BREE of deps)

* build against proper target platform containing the oldest versions of your deps you support


I don't believe many people will face such issues but let's get this out for the sake of having it written somewhere.


Alexander Kurtakov

Red Hat Eclipse Team

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top