I have noticed that the JBoss RMI API project has inconsistencies regarding the license designation.
The POM itself mentions LGPL 2.1, but in the JAR in a LICENSE file and the file headers the GNU GPL v2.0 is specified with classpath exception.
The change to the license information in the POM was made in this commit, between version 1.0.1.Final and 1.0.2.Final. There is a reference to the issue ticket JBEE-83 in the title.
Furthermore, there was once an issue with the ID JBEE-189, in which the license problem was pointed out, but unfortunately the issue itself can no longer be found. However, a mailing list archive can still be used to view status changes to the ticket before it disappeared.
There is also an issue on the Github project page about the license problem, but unfortunately no maintainer has responded. That is why I am now creating this ticket here.
When checking the file headers, we also noticed two classes that were not marked as GNU GPL v2.0 with Classpath Exception:
org.jboss.com.sun.corba.se.impl.javax.rmi.RemoteObjectSubstitution
org.jboss.com.sun.corba.se.impl.javax.rmi.RemoteObjectSubstitutionManager
The relevant classes were also added after version 1.0.1.Final and contain their own header without any specific license information. It is therefore also unclear under which license these files are actually licensed with regard to the different license details mentioned.

In summary, the license information of the project are inconsistent and the license under which the aforementioned, later added classes are actually licensed is completely unclear.
Under which license is the project in the current version 1.0.6.Final? Under which license are the two classes in question licensed? Can the inconsistent information be corrected? Should I create a corresponding pull request on Github myself? If so, with which specific corrections and how can a corrected version be published?

Thank you very much.