[
https://issues.apache.org/jira/browse/HADOOP-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536388#comment-15536388
]
Kihwal Lee commented on HADOOP-13671:
-------------------------------------
The current trunk build has this:
{noformat}
[WARNING] Unable to process class org/apache/hadoop/hdfs/StripeReader.class in
JarAnalyzer File /home1/kihwal/devel/apache/hadoop/hadoop-hdfs-project/
hadoop-hdfs-client/target/hadoop-hdfs-client-3.0.0-alpha2-SNAPSHOT.jar
org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
pool: 18
at org.apache.bcel.classfile.Constant.readConstant(Constant.java:146)
at org.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:67)
at
org.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:222)
at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:136)
at
org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClassesAnalysis.java:92)
...
{noformat}
> Fix ClassFormatException during trunk build.
> --------------------------------------------
>
> Key: HADOOP-13671
> URL: https://issues.apache.org/jira/browse/HADOOP-13671
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Kihwal Lee
>
> The maven-project-info-reports-plugin version 2.7 depends on
> maven-shared-jar-1.1, which uses bcel 5.2. This does not work well with the
> new lamda expression. The 2.9 depends on maven-shared-jar-1.2, which works
> around this problem by using the custom release of bcel 6.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]