|Re: [tycho-dev] [platform-releng-dev] 4.8.0 I-Build: I20180424-2000 - BUILDFAILED|
as of now I think missing BREE means fallback to default BREE (which was recently changed to JavaSE-9 in Tycho 1.2.0-SNAPSHOT)
Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.2.0-SNAPSHOT:compile (default-compile) on project org.eclipse.ui.examples.navigator: Fatal error compiling: option -bootclasspath not supported at compliance level 9 and above -> [Help 1]Looks like -bootclasspath is added by default in such cases but this is not compatible with the new default.
one could probably argue that useJDK=BREE along with a missing manifest BREE should be considered an error (or at least a warning)
ïOn 25.04.18, 09:08, "platform-releng-dev-bounces@
eclipse.orgon behalf of Aleksandar Kurtakov" <platform-releng-dev-bounces@ eclipse.orgon behalf of akurtako@xxxxxxxxxx> wrote:
Â Â On Wed, Apr 25, 2018 at 9:37 AM, Mickael Istria
Â Â <mistria@xxxxxxxxxx> wrote:
Â Â This is caused by the fact that the bundle doesn't specify a BREE and fails back to default one (JavaSE-9 now). Specifying BREEs would avoid this error.
Â Â It might be a bug in Tycho in some specific case, but it's IMO better to use this opportunity to cleanup our bundles by adding BREEs where missing.
Â Â I've added BREE to the bundle in question and build is restarted. There is more fundamental question though:
Â Â What should be Tycho behavior when building bundle that doesn't have BREE specified but we have useBREE=true?
Â Â Cheers
Â Â ______________________________
Â Â tycho-dev mailing list
Â Â tycho-dev@xxxxxxxxxxx
Â Â To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Â Â https://dev.eclipse.org/
Â Â --
Â Â Alexander Kurtakov
Â Â Red Hat Eclipse Team
_________________To change your delivery options, retrieve your password, or unsubscribe from this list, visit
platform-releng-dev mailing list