[ROL-2153] Upgrade to Struts 2.5.21 when released

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.0.0
• Fix Version/s: 6.0.0
• Component/s: User Interface - General
• Level of effort: upgraded to 2.5.22 and all ASM related error messages went away.
• Assignee: David Johnson
• Reporter: David Johnson
• Created: 06/Oct/19 22:07
• Updated: 09/Dec/19 23:33
• Resolved: 09/Dec/19 23:33

Description

Upgrade to 2.5.21 before releasing Roller 6.

Upgrading may elimniate the error message below, which is seen when running Roller 6 via Docker Compose but does not prevent Roller from functioning properly:

roller_1      | 22:21:58.976 [main] ERROR org.apache.struts2.convention.DefaultClassFinder - Unable to read class [org.apache.roller.weblogger.ui.struts2.editor.EntryEdit]
roller_1      | java.lang.UnsupportedOperationException: This feature requires ASM7
roller_1      | 	at org.objectweb.asm.ClassVisitor.visitNestMember(ClassVisitor.java:236) ~[asm-7.0.jar:7.0]
roller_1      | 	at org.objectweb.asm.ClassReader.accept(ClassReader.java:651) ~[asm-7.0.jar:7.0]
roller_1      | 	at org.objectweb.asm.ClassReader.accept(ClassReader.java:391) ~[asm-7.0.jar:7.0]
roller_1      | 	at org.apache.struts2.convention.DefaultClassFinder.readClassDef(DefaultClassFinder.java:462) ~[struts2-convention-plugin-2.5.20.jar:2.5.20]
roller_1      | 	at org.apache.struts2.convention.DefaultClassFinder.<init>(DefaultClassFinder.java:93) [struts2-convention-plugin-2.5.20.jar:2.5.20]
roller_1      | 	at org.apache.struts2.convention.PackageBasedActionConfigBuilder.buildClassFinder(PackageBasedActionConfigBuilder.java:395) [struts2-convention-plugin-2.5.20.jar:2.5.20]
roller_1      | 	at org.apache.struts2.convention.PackageBasedActionConfigBuilder.findActions(PackageBasedActionConfigBuilder.java:377) [struts2-convention-plugin-2.5.20.jar:2.5.20]
roller_1      | 	at org.apache.struts2.convention.PackageBasedActionConfigBuilder.buildActionConf

If upgrading does not fix this, then we should document the above issue as a "known issue"