license-tool-plugin fails with Tycho 3.0.0-SNAPSHOT for M2E

[HannesWell]

While the license-tool-plugin works perfectly fine for the M2E build with Tycho 2.7.5 it fails when Tycho 3.0.0-SNAPSHOT is used, because it cannot vet dependencies like the following:

[INFO] p2/orbit/p2.eclipse.plugin/org.osgi.service.repository/1.1.0.201505202024
[INFO] p2/orbit/p2.p2.installable.unit/org.eclipse.equinox.executable_root.cocoa.macosx.x86_64/3.8.1800.v20220720-1949
[INFO] p2/orbit/p2.p2.installable.unit/org.eclipse.equinox.executable_root.gtk.linux.x86_64/3.8.1800.v20220720-1949
[INFO] p2/orbit/p2.p2.installable.unit/org.eclipse.equinox.executable_root.win32.win32.x86_64/3.8.1800.v20220720-1949
[INFO] p2/orbit/p2.p2.installable.unit/org.eclipse.platform_root/4.25.0.v20220831-1800
[INFO] p2/orbit/p2.p2.installable.unit/org.eclipse.rcp_root/4.25.0.v20220831-1800

Many of them are created by Eclipse projects and therefore should be inherently vetted. When I ask the plug-in to create vetting requests, those requests fail because the source cannot be found: https://github.com/eclipse-m2e/m2e-core/pull/931#issuecomment-1256949793

Therefore the assumption is that the dash license-tool searches for the wrong metadata and has to be adjusted to changes in Tycho. Some more context can be found here: https://github.com/eclipse-m2e/m2e-core/pull/932

[waynebeaton]

What's the deal with the "p2.p2" (p2.p2.installable.unit)?

I noticed that the tool had created some reviews for those bundles, but when I ran the build myself, they didn't come up and I assumed that it was an anomaly.

[HannesWell]

What's the deal with the "p2.p2" (p2.p2.installable.unit)?

I have to admit I'm just the messenger here and not familiar with the exact details. @laeubi probably knows it better.