[ 
https://issues.apache.org/jira/browse/MPIR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518402#comment-16518402
 ] 

ASF GitHub Bot commented on MPIR-370:
-------------------------------------

Serranya opened a new pull request #6: [MPIR-370] Upgrade bcel to avoid 
ClassFormatException
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/6
 
 
   See https://issues.apache.org/jira/browse/MPIR-370

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> org.apache.bcel.classfile.ClassFormatException when scanning log4j-api
> ----------------------------------------------------------------------
>
>                 Key: MPIR-370
>                 URL: https://issues.apache.org/jira/browse/MPIR-370
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Bug
>          Components: dependencies
>    Affects Versions: 2.9
>         Environment: java -version
> java version "10.0.1" 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
> mvn -v
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 
> 2018-02-24T20:49:05+01:00)
> Maven home: C:\Program Files\apache-maven-3.5.3
> Java version: 10.0.1, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jre-10.0.1
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>            Reporter: Peter Lamby
>            Assignee: Michael Osipov
>            Priority: Minor
>
> When running the Dependiencies report target with java 10 i get the following 
> exception:
> {noformat}
> [WARNING] Unable to process class module-info.class in JarAnalyzer File 
> C:\Users\plamby\.m2\repository\org\apache\logging\log4j\log4j-api\2.10.0\log4j-api-2.10.0.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant 
> pool: 19
>     at org.apache.bcel.classfile.Constant.readConstant(Constant.java:161)
>     at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:69)
>     at 
> org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:235)
>     at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:143)
>     at 
> org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:96)
>     at 
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:259)
>     at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1542)
>     at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:545)
>     at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:240)
>     at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:83)
>     at 
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:201)
>     at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
>     at 
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
>     at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
>     at 
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:198)
>     at 
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:147)
>     at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>     at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>     at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>     at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>     at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>     at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>     at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>     at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>     at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.base/java.lang.reflect.Method.invoke(Method.java:564)
>     at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>     at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>     at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>     at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356){noformat}
> You can find a project to reproduce the problem here: 
> [https://github.com/Serranya/ballot/tree/reportsBug]
>  
> just run mvn -Pdev clean verify site



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to