Hi
You may also find https://bugs.eclipse.org/bugs/show_bug.cgi?id=569379
relevant if you move on from an old Tycho to avoid IPlatformRunnable.
It would appear that something in the auto-POM logic ignores the
MANIFEST.MF BREE and instead picks one from an explicit pom.xml BREE so
avoid vintage BREEs in test plugins.
Inconsistent org.eclipse.jdt.core.prefs between plugins can also be a
problem. Maybe OOMPH can avoid this.
If you use JDT's @NonNull annotations it is essential that you set
deriveReleaseCompilerArgumentFromTargetLevel false.
Regards
Ed Willink
On 19/03/2021 08:33, Wim Jongman wrote:
Thanks, Ed! I was just starting to convert some builds to 4.20.
On Fri, Mar 19, 2021 at 9:17 AM Ed Merks <ed.me...@gmail.com
<mailto:ed.me...@gmail.com>> wrote:
BREE 1.6 and when I moved them to BREE 1.8, that magically
avoided the
Tycho compile errors. Probably others won't have such a problem, but
maybe good to keep in mind.
Maybe: https://bugs.eclipse.org/bugs/show_bug.cgi?id=561363
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=561363>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
