|Re: [tycho-user] Please test staged tycho|
I'd expect that optional dependencies generally ignored overall
unless there is also a non-option dependency somewhere else.
Should they be greedy?
my assumtion was that the new impl would treat these optionally
Am 20.07.21 um 16:16 schrieb Keppler Michael (ETAS/ESW-CI) via tycho-user:
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.
Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle, Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef SchuermannAufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald Goertz, Eric SwehlaSitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen (Germany)Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621
_______________________________________________ tycho-user mailing list tycho-user@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user
Back to the top