First, a +1 for the RCP/RAP package... seems to work in my short smoke test.
Then to the second question. You are correct, we've never been using a category.xml or anything like categorization for aggregating all EPP IUs into a single p2 repository. I don't remember the exact details, but I think the problem was similar to what we see now, i.e. too many artifacts were duplicated. Instead I used the tycho-p2-extras-plugin to mirror a selection of relevant IUs to a central p2 repository in releng/org.eclipse.epp.config/parent/product/pom.xml, or follow the following link here:
I've regenerated the catalog and tested installs with it. All
that works reasonably, so I think it's not a super horrible
problem. Also, I've committed the catalog changes already so
anyone installing 2022-09 with any installer will be installing M2
already...
Note too that a quick side-by-side comparison indicates that it's
just duplicate content between the train repo and the EPP repo, so
I don't think this will be at all problematic for p2 in general.
Duplication is common...
So I would recommend we just go with this and revisit/fix the
issue at a leisurely pace so that you don't spend today scrambling
and re-spinning.
But that's just my feeling and it's your call to make. So if you
still want me to disable "make visible", I'll do as you ask.
What do you think?
Regards,
Ed
On 05.08.2022 13:40, Jonah Graham
wrote:
Hi Ed,
I will look into this as soon as possible. I guess
it is the tycho or Java version change. Sorry I missed this.
I recommend disabling make visible job until we
resolve this issue.
I noticed the features because this breaks assumptions
in Oomph's product catalog generator, but the
duplication is also present for the bundles, though
there is much less duplication there...
Looking at the commit history, I don't see anything
that stands out as having caused this effect since M1.
Is this perhaps a side effect of having only a single
child in the composite now? Or perhaps the updated
versions of various things such as Maven and Tycho
behave differently now? My guess would be the Tycho
version change, but I can't really understand from all
the poms what exactly determines the content of the EPP
repository. There is no category.xml as far as I can
tell.
Regards,
Ed
On 05.08.2022 01:26, Jonah Graham wrote:
Hi everyone,
Our next milestone build is available for testing: EPP
2022-09 M2
Only issue to report is that a couple of 3rd party
libraries in Eclipse Platform have gone backwards
version number + signature wise. I have reported
that issue.
Please test and send your +1 to this mailing list.
+1s are optional as the package will be published
anyway.
Last +1 received for each package and platform
(apologies if I missed one of your +1 emails, just
let me know and I will update Last Recorded +1) I
have highlighted those packages/platforms that I
haven't seen any confirmation in this release cycle
on.