slachiewicz opened a new issue, #13306: URL: https://github.com/apache/maven/issues/13306
### Affected version 4.0.0-rc-7; unchanged on `master`. ### Bug description A packaging contributed through the `org.apache.maven.api.spi.PackagingProvider` SPI is never found. [`DefaultPackagingRegistry.lookup`](https://github.com/apache/maven/blob/master/impl/maven-core/src/main/java/org/apache/maven/internal/impl/DefaultPackagingRegistry.java) consults only the Sisu `LifecycleMapping` component for the id and returns empty without one; the `List<PackagingProvider>` passed to the constructor is never read by `lookup`. The TODO in that method explains the Sisu lookup, not why the providers are skipped. Observed while porting maven-acr-plugin to the Maven 4 API (#13302): registering `app-client` with a `PackagingProvider` plus `TypeProvider` and removing `META-INF/plexus/components.xml` fails with `Unknown packaging: app-client`. maven-acr-plugin, maven-rar-plugin, maven-jmod-plugin and maven-jlink-plugin therefore still register their packaging with Maven 3 components. #2277 rewrites this method too, but keeps the `LifecycleMapping`-only lookup. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
