[tycho-dev] [platform-releng-dev] 4.8.0 I-Build: I20180424-2000 - BUILDFAILED

[Jayaprakash Arthanareeswaran]

Okay, looks like Tycho did change in the relevant area [1] in the past
week and a new version has been created.
Can somebody from Tycho team look at this please?

Regards,
Jay
[1]
https://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=80f8338fbdb4b30ebe0596de617dd72334d158a0



From: "Jayaprakash Arthanareeswaran" <***@in.ibm.com>
To: "Eclipse platform release engineering list."
<platform-releng-***@eclipse.org>
Date: 04/25/2018 08:44 AM
Subject: Re: [platform-releng-dev] 4.8.0 I-Build: I20180424-2000 -
BUILD FAILED
Sent by: platform-releng-dev-***@eclipse.org



The failure is due to the following:

21:22:29 [ERROR] 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]

Not sure whether it's tycho that's passing the boot classpath or it's
getting it from somewhere. I am investigating.

Jay




From: ***@eclipse.org
To: platform-releng-***@eclipse.org
Date: 04/25/2018 06:54 AM
Subject: [platform-releng-dev] 4.8.0 I-Build: I20180424-2000 -
BUILD FAILED
Sent by: platform-releng-dev-***@eclipse.org



Eclipse downloads:
http://download.eclipse.org/eclipse/downloads/drops4/I20180424-2000/
Build logs and/or test results (eventually):

http://download.eclipse.org/eclipse/downloads/drops4/I20180424-2000/testResults.php

_______________________________________________
platform-releng-dev mailing list
platform-releng-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_platform-2Dreleng-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=p7LUgVjsohjD8UbyHdszA45-Va0u31sTt5y9KX-eQX0&s=j8l91pOjs0YB4YX08dx7NZ9dUHGR9Nzs41O53Kcctwk&e=



_______________________________________________
platform-releng-dev mailing list
platform-releng-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_platform-2Dreleng-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=gHVnt29kV5Z3lCK_6nRjqFM6C3UVgMXxMKqWsSrcb3o&s=W_YtlOVbR6eJImYDTYm65uUbdhXv1ZRHjPCxycHnnYk&e=

[Mickael Istria]

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.

Cheers

[Aleksandar Kurtakov]

Post by Mickael Istria
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?

Post by Mickael Istria
Cheers
_______________________________________________
tycho-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-dev

[Sievers, Jan]

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)

one could probably argue that useJDK=BREE along with a missing manifest BREE should be considered an error (or at least a warning)

Regards
Jan

On 25.04.18, 09:08, "platform-releng-dev-***@eclipse.org on behalf of Aleksandar Kurtakov" <platform-releng-dev-***@eclipse.org on behalf of ***@redhat.com> wrote:



On Wed, Apr 25, 2018 at 9:37 AM, Mickael Istria
<***@redhat.com> 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-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-dev






--
Alexander Kurtakov

Red Hat Eclipse Team

[Aleksandar Kurtakov]

Post by Sievers, Jan
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)

Do you have a pointer where can the following come up from?

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.

Post by Sievers, Jan
one could probably argue that useJDK=BREE along with a missing manifest
BREE should be considered an error (or at least a warning)

I'm one of these :). Should I open a bug about this?

Post by Sievers, Jan
Regards
Jan
On Wed, Apr 25, 2018 at 9:37 AM, Mickael Istria
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.
What should be Tycho behavior when building bundle that doesn't have
BREE specified but we have useBREE=true?
Cheers
_______________________________________________
tycho-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-dev
--
Alexander Kurtakov
Red Hat Eclipse Team
_______________________________________________
platform-releng-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

[Sievers, Jan]

Post by Aleksandar Kurtakov
Do you have a pointer where can the following come up from?
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.

this is new to me. Probably best to open a bug with sample project and steps to reproduce.

The background is that with useJDK=BREE, we are using -bootclasspath arguments to be able to compile in-process against a different JDK than the one currently running
See bugs

https://bugs.eclipse.org/bugs/show_bug.cgi?id=514471
https://bugs.eclipse.org/bugs/show_bug.cgi?id=528752
https://bugs.eclipse.org/bugs/show_bug.cgi?id=483300


In particular my comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=514471#c57 :


"@JDT devs I would appreciate feedback if the approach above with -bootclasspath, -extdirs, -endorseddirs determined by forking a small Main dumping System props is fine."


Regards
Jan




one could probably argue that useJDK=BREE along with a missing manifest BREE should be considered an error (or at least a warning)




I'm one of these :). Should I open a bug about this?




Regards
Jan

On 25.04.18, 09:08, "platform-releng-dev-***@eclipse.org on behalf of Aleksandar Kurtakov" <platform-releng-dev-***@eclipse.org
on behalf of ***@redhat.com> wrote:



On Wed, Apr 25, 2018 at 9:37 AM, Mickael Istria
<***@redhat.com> 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-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/tycho-dev <https://dev.eclipse.org/mailman/listinfo/tycho-dev>






--
Alexander Kurtakov

Red Hat Eclipse Team








_______________________________________________
platform-releng-dev mailing list
platform-releng-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev





--
Alexander Kurtakov

Red Hat Eclipse Team

[Jayaprakash Arthanareeswaran]

Jan,

I just responded to your question on the bug.

Jay



From: "Sievers, Jan" <***@sap.com>
To: "Eclipse platform release engineering list."
<platform-releng-***@eclipse.org>, Tycho list <tycho-***@eclipse.org>
Date: 04/25/2018 02:51 PM
Subject: Re: [tycho-dev] [platform-releng-dev] 4.8.0 I-Build:
I20180424-2000 - BUILDFAILED

Post by Aleksandar Kurtakov
Do you have a pointer where can the following come up from?
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

Post by Aleksandar Kurtakov
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.



this is new to me. Probably best to open a bug with sample project and
steps to reproduce.

The background is that with useJDK=BREE, we are using -bootclasspath
arguments to be able to compile in-process against a different JDK than
the one currently running
See bugs

https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug.cgi-3Fid-3D514471&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=g-dusp9wjzMROLzUuYDw1Ki9MKNmT7E5_mI1DvSWYfQ&e=

https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug.cgi-3Fid-3D528752&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=jvf-Jyqy8-n9Brb9wcZBp6PzbpcVT325B0crA5iOQLo&e=

https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug.cgi-3Fid-3D483300&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=AYe94MtRoitEcoviDXtd-pT-oWjDe4Tsyl8EzJtLYnE&e=



In particular my comment
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.eclipse.org_bugs_show-5Fbug.cgi-3Fid-3D514471-23c57&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=b7YPcHYltP2-EY4lwhS7FzVhuNELcv1oqaMaW1ynu4o&e=
:


"@JDT devs I would appreciate feedback if the approach above with
-bootclasspath, -extdirs, -endorseddirs determined by forking a small Main
dumping System props is fine."


Regards
Jan




one could probably argue that useJDK=BREE along with a missing
manifest BREE should be considered an error (or at least a warning)




I'm one of these :). Should I open a bug about this?




Regards
Jan

On 25.04.18, 09:08, "platform-releng-dev-***@eclipse.org on behalf
of Aleksandar Kurtakov" <platform-releng-dev-***@eclipse.org
on behalf of ***@redhat.com> wrote:



On Wed, Apr 25, 2018 at 9:37 AM, Mickael Istria
<***@redhat.com> 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-***@eclipse.org
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit


https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_tycho-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=l8P-7FuVWdpPr47HjTJIiKczHZFad6_2lDrlQe-dP6g&e=
<
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_tycho-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=l8P-7FuVWdpPr47HjTJIiKczHZFad6_2lDrlQe-dP6g&e=
--
Alexander Kurtakov

Red Hat Eclipse Team








_______________________________________________
platform-releng-dev mailing list
platform-releng-***@eclipse.org
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit

https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_platform-2Dreleng-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=hlgTJnxURmrJ9V4mR0I-245czpWQMuBS_4p1k773NYs&e=






--
Alexander Kurtakov

Red Hat Eclipse Team






_______________________________________________
tycho-dev mailing list
tycho-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_tycho-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=LuMqcl3PU0i2olgTvkVvFthzqyc_3wGfGooplpAvFsc&m=HyJWi7Vi3B23pfHrkLeDZGe_eUHLC9cniE3VmzeUUbU&s=l8P-7FuVWdpPr47HjTJIiKczHZFad6_2lDrlQe-dP6g&e=