With -Xlog:classload=debug the info and debug level messages are too similar where the debug line is a superset of the info line and it looks funny to have 2 very similar log lines.

How about move the "[class loader 0x00007fbb7801bf40a 'chickentest/MyNonDefiningURLLoader']" info into the info level because IMO app developers are interested in the name and uniqueness of the class loader, not the "klass: 0x00000008012a1220 super: 0x0000000801001788" info which is more for JVM supportability.
This is b113-ish.

Here is an example:

[0.389s][info ][classload] sun.security.util.ManifestEntryVerifier source: shared objects file
[0.389s][debug][classload] sun.security.util.ManifestEntryVerifier source: shared objects file klass: 0x0000000801267770 super: 0x0000000801001788 loader: [NULL class_loader]
[0.389s][info ][classload] sun.nio.ByteBuffered source: shared objects file
[0.389s][debug][classload] sun.nio.ByteBuffered source: shared objects file klass: 0x0000000801268178 super: 0x0000000801001788 loader: [NULL class_loader]
[0.390s][info ][classload] hidden.HiddenMsgThread source: file:/tmp/ChickenLib.jar
[0.390s][debug][classload] hidden.HiddenMsgThread source: file:/tmp/ChickenLib.jar klass: 0x000000080247e828 super: 0x0000000801024e80 loader: [class loader 0x00007fbb78002290a 'chickentest/MyNonDefiningURLLoader'] bytes: 2682 checksum: a9f5af54