[BUILD-219] Clirr maven plugin can fail on Java 8 (e.g. main, UI, pages, etc.) Created: 28/Jan/16 Updated: 05/May/17 Resolved: 18/Nov/16 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | POMs 32 |
| Fix Version/s: | POMs 33 |
| Type: | Task | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | clirr, maven, selected-for-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | Make build system Java 8 ready |
| Sprint: | Basel 70 |
| Story Points: | 1 |
| Description |
|
When running mvn clirr:clirr directly or when generating the site (which includes the clirr report) one might run into the folloing error: [INFO] org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 18
Additionally, one might see:
Caused by: java.lang.NullPointerException
at org.codehaus.mojo.clirr.ClirrReportGenerator$ApiChangeComparator.compare(ClirrReportGenerator.java:64)
at org.codehaus.mojo.clirr.ClirrReportGenerator$ApiChangeComparator.compare(ClirrReportGenerator.java:57)
Which is due to an ApiChange being initialized to null. Both bugs (see links below) have been fixed in org.codehaus.mojo:clirr-maven-plugin:2.8 and we should therefore update our plugin to this latest version. |