[MNG-8583] Missing SISU bean definitions from maven-resolver-provider

[gnodet]

JIRA issue: MNG-8583

The beans are not recognized by Sisu as the needed META-INF file is missing.

[elharo]

Any chance the OOM is related?

Error:  Java heap space -> [Help 1]
java.lang.OutOfMemoryError: Java heap space
    at org.apache.bcel.classfile.Constant.readConstant(Constant.java:86)
    at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:89)
    at org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:224)
    at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:132)
    at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:185)
    at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyzeRoot(JarClassesAnalysis.java:165)
    at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:114)
    at org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:228)
    at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1209)
    at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:518)
    at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:233)
    at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:82)
    at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:167)
    at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:289)
    at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:226)
    at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:348)
    at org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:194)
    at org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:143)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:146)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:339)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:310)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:214)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:179)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run(MojoExecutor.java:168)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute(DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:165)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:110)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:60)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleStarter.execute(DefaultLifecycleStarter.java:123)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:311)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:225)

[elharo]

What's the impact of this? If this is a bug, why did it not break any tests? Is a test missing?

[gnodet]

What's the impact of this? If this is a bug, why did it not break any tests? Is a test missing?

It did not break any tests because it's not used anymore in the standard use cases. I saw it while testing https://github.com/smallrye/smallrye-beanbag which boots a custom resolver.

[elharo]

Ok, can we add a test that fails without this?