Community
Participate
Working Groups
In some release scans I do, I noticed that the google.inject source bundle was being listed as a "java bundle". Which means the scan detected a .class file. I downloaded latest version, and see package-info.class is included. I'm guessing it should not be. Not sure if it'd hurt anything?
I was looking to see if there was a "package-info" class in the actual code, and do not see one there ... but do see a lot of other "package-info.java" files in the source bundle. Not sure if it was an intentional artifact of original builders? Or ... if simple mistake? My advice would be to remove it from the source bundle, but doubt it really causes any problems (other than causing a false positive in code scanners :) So, will set as minor and let Sebastian investigate original jars/contributions our Orbit versions came from.
This appears to have been an issue with com.google.inject.source 2.0.0 , which did indeed contain com/google/inject/util/package-info.class . However, this was not shipped anymore with our Neon contribution. We also now ship com.google.inject 3.0.0. Marking as CLOSED (FIXED).