Replies: 4 comments 4 replies
-
I noticed you are using a combination of a target+repository references, this makes it a bit hard to follow whats going on, is there are strong reason to do so? The source level has nothing to do with the target platform but might be derived from your bundles BREE, can you check that all your bundles are using JavaSe-11 as BREE, have the correct JRE set in the classpath and your build is using a JDK11 or is configured with a corresponding one in toolchains.xml? |
Beta Was this translation helpful? Give feedback.
-
This is the issue you should look at carefully. There is no reason for this to happen and I suspect it's an issue in your end. Check you build files for anything that would enforce a 1.5 source level, it's not default Tycho behavior. |
Beta Was this translation helpful? Give feedback.
-
No, I'm running on Fedora Linux 34, but the build also fails on
https://ci.eclipse.org/atl/job/mmt-atl-pr/84/console
…On Tue, Feb 1, 2022 at 8:07 AM Christoph Läubrich ***@***.***> wrote:
I think this could be related to #598
<#598> are you running on a mac?
—
Reply to this email directly, view it on GitHub
<#554 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB2VGFFYWDXOJPMMLAQ4ZTUY6BC3ANCNFSM5MSHBLDA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
ATL has since migrated to github, and I've had to revisit the Jenkins build pipeline. In this context, I've managed to get ATL to build using Tycho 4.0.8, such that it can be built against the latest Eclipse codebase. See also: I've added a target platform definition with an explicit targetJRE to get around the problem of having various bundles in the dependency graph that require a lower version JRE than its upstream dependencies. This is typical for OSGi bundles that want to be able to build against older versions of the Eclipse codebase. |
Beta Was this translation helpful? Give feedback.
-
In order to build ATL against the latest Eclipse release plug-ins, I've started the effort to port it to JavaSE-11 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=576366). Only a few changes were required in the source code, and I got ATL to build fairly quickly within the Eclipse IDE.
The tycho build is another matter, however. When updating to the latest tycho release (required for JavaSE-11), it spits out the following error:
https://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting suggests that the target definition is inconsistent. I've since been experimenting with target platform definitions, and adding "JavaSE-11" as targetJRE seems to solve the dependency resolution problems, but then switches the Java compiler to version 1.5 source level (
@Override
on interface methods, multi-catch not supported):The PR can be found at https://git.eclipse.org/r/c/mmt/org.eclipse.atl/+/189434
Does anyone have any idea what is going on?
P.S. I found #205, but that removing the target definition is the starting situation in this case.
Beta Was this translation helpful? Give feedback.
All reactions