Ed Merks

I'm at Shinjuku Station and I see many long roads. I must pick and choose. Others of course do the same, and choose differently. :-)

I think finding the call hierarchy of org.eclipse.equinox.p2.metadata.expression.IMatchExpression.isMatch(T) will find such places. E.g., Oomph has method like this for determine if a task's filter matches the current OS: ``` @SuppressWarnings("restriction")...

Your cross projects email and the referenced issue suggest this switch was necessary for some "latest fixes" and for "Java 19 to work". I'm curious which latest fixes are needed...

Ah, I see. So you expect to need/want Java 17 soon and switching to that would require a major version increment so you might as well do this as part...

To fix problems like this I always use the approach described here: https://wiki.eclipse.org/Eclipse_Oomph_Authoring#How_to_find_a_P2_repository_at_Eclipse_using_the_Repository_Explorer Unfortunately they don't provide very nice sites. I.e., there is no site with just the latest release...

The latest implementation doesn't do this anymore.

@laeubi This issue is fixed now.

Note that because a p2 does not have access to a key server (by default) if we are going to record the signature, we'd better also record the public key...

Yes, I encountered this with EMF's build yesterday and was pulling my hair out about the cause... I can (and should?) probably fix/change this in Orbit if I promoted to...

I assume Tycho is looking at these p2 metadata properties and is trying to use them to resolve dependencies: ``` ``` Is that correct? It looks like the only place...