We had a build failure with 2.4, but it was a problem on our side: One bundle A has an additional.bundle header containing bundle B, and B is just not part of the aggregator.
Works fine in PDE, but of course not in Tycho.
I guess the support for that header cannot be disabled via some option? I think there are quite some projects using additional.bundle for “IDE-time dependencies”, like running
MWE workflows in Xtext etc.. When used together with tycho target platform filtering, this was a nice trick to have stuff in the target only for the IDE (Junit, MWE, Xtext, …), but not for the product you build. Looks like I need to figure out a new workaround
for that.
Mit freundlichen Grüßen / Best regards
Michael Keppler
Engineering Application Software - Chapter CI/CD and Common Infrastructure Components
T +49 711 3423-2429
Michael.Keppler@xxxxxxxx
ETAS GmbH, ETAS/ESW-CI
Borsigstraße 24, 70469 Stuttgart, Germany
www.etas.com
ETAS – Driving Embedded Excellence
Managing Directors: Christoph Hartung, Günter Gromeier, Götz Nigge
Chairman of the Supervisory Board: Dr. Walter Schirm
Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 19033
Von: tycho-user <tycho-user-bounces@xxxxxxxxxxx>
Im Auftrag von Mickael Istria
Gesendet: Montag, 19. Juli 2021 19:13
An: tycho-dev <tycho-dev@xxxxxxxxxxx>; list, Tycho <tycho-user@xxxxxxxxxxx>
Betreff: Re: [tycho-user] Please test staged tycho