[tycho-user] p2.inf confuses tycho, can it be ignored during resolution?

[Stephan Herrmann]

Hi,

I have a pretty involved build successfully running on PDE/Build since 15 years. :)

During shy attempts to migrate this build to tycho I'm currently blocked
because tycho chokes on some of my p2.inf files.


One p2.inf intentionally creates a non-greedy cyclic dependency between
a feature patch and its plugin:
http://git.eclipse.org/c/objectteams/org.eclipse.objectteams.git/tree/org.eclipse.jdt.core/META-INF/p2.inf
(This p2.inf ensures that the plug-in cannot be accidentally installed without installing also the patch feature).
Tycho plainly rejects this cycle.


Another p2.inf had been provided by Pascal Rapicault in https://bugs.eclipse.org/432700
to allow us setting a startLevel. Here tycho complains that it cannot
resolve the artificial unit created as
units.0.id = org.eclipse.objectteams.otequinox.configuration


I would be happy, if tycho could just ignore those p2.inf during resolution
and pick it up only when creating metadata.
Is this possible already? If not, would it make sense as an RFE?

Otherwise, I'm afraid tycho would need to become much smarter to actually
accept these files, which are legal by the rules of p2.

thanks,
Stephan

[Sievers, Jan]

not sure but maybe

https://wiki.eclipse.org/Tycho/p2iu.xml

could help.
https://wiki.eclipse.org/Tycho/Release_Notes/0.23#Packaging_Type


Regards
Jan


On 04.11.18, 18:40, "tycho-user-***@eclipse.org on behalf of Stephan Herrmann" <tycho-user-***@eclipse.org on behalf of ***@berlin.de> wrote:

Hi,

I have a pretty involved build successfully running on PDE/Build since 15 years. :)

During shy attempts to migrate this build to tycho I'm currently blocked
because tycho chokes on some of my p2.inf files.


One p2.inf intentionally creates a non-greedy cyclic dependency between
a feature patch and its plugin:
http://git.eclipse.org/c/objectteams/org.eclipse.objectteams.git/tree/org.eclipse.jdt.core/META-INF/p2.inf
(This p2.inf ensures that the plug-in cannot be accidentally installed without installing also the patch feature).
Tycho plainly rejects this cycle.


Another p2.inf had been provided by Pascal Rapicault in https://bugs.eclipse.org/432700
to allow us setting a startLevel. Here tycho complains that it cannot
resolve the artificial unit created as
units.0.id = org.eclipse.objectteams.otequinox.configuration


I would be happy, if tycho could just ignore those p2.inf during resolution
and pick it up only when creating metadata.
Is this possible already? If not, would it make sense as an RFE?

Otherwise, I'm afraid tycho would need to become much smarter to actually
accept these files, which are legal by the rules of p2.

thanks,
Stephan
_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tycho-user