The InjectP2MavenMetadataHandling option (values ignore, inject, validate) is fully implemented: the enum and TargetPlatformConfiguration.setP2MavenMetadataHandling(...) exist, and P2DependencyResolver honors each mode. However, DefaultTargetPlatformConfigurationReader never reads it from target-platform-configuration, so the setter has no callers and the value is permanently stuck on the default, validate.
In validate mode, P2DependencyResolver.resolveDescriptorWithValidation(...) calls dependenciesResolver.resolveArtifact(...) for every mapped p2 artifact. On a large target platform that is one remote Maven lookup per plugin and feature across all configured repositories, each miss logging Mapping P2 > Maven Coordinates failed: ... (and the related Unable to create Maven project for p2.eclipse.plugin:... warnings). This adds significant build time and log noise, with no way to turn it off.
Wire the existing <p2MavenMetadataHandling> option into DefaultTargetPlatformConfigurationReader (same pattern as referencedRepositoryMode) so users can set inject (map coordinates without remote resolution) or ignore. The default can stay validate for backward compatibility.
The
InjectP2MavenMetadataHandlingoption (valuesignore,inject,validate) is fully implemented: the enum andTargetPlatformConfiguration.setP2MavenMetadataHandling(...)exist, andP2DependencyResolverhonors each mode. However,DefaultTargetPlatformConfigurationReadernever reads it fromtarget-platform-configuration, so the setter has no callers and the value is permanently stuck on the default,validate.In
validatemode,P2DependencyResolver.resolveDescriptorWithValidation(...)callsdependenciesResolver.resolveArtifact(...)for every mapped p2 artifact. On a large target platform that is one remote Maven lookup per plugin and feature across all configured repositories, each miss loggingMapping P2 > Maven Coordinates failed: ...(and the relatedUnable to create Maven project for p2.eclipse.plugin:...warnings). This adds significant build time and log noise, with no way to turn it off.Wire the existing
<p2MavenMetadataHandling>option intoDefaultTargetPlatformConfigurationReader(same pattern asreferencedRepositoryMode) so users can setinject(map coordinates without remote resolution) orignore. The default can stayvalidatefor backward compatibility.