JDK-8005688 : jar reorder classlists need to be made Profile aware
  • Type: Enhancement
  • Component: performance
  • Sub-Component: libraries
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2013-01-04
  • Updated: 2016-06-17
  • Resolved: 2016-06-17
Related Reports
Relates :  
JDK-7032729 - Re-validate that jar reordering is a performance benefit
Description
The jar reorder classlists stored in the source repository are for a full JRE rt.jar. When building the SE Compact Profiles the set of excluded types overlaps with the types in the classlist. This resulted in numerous warnings that an included type was also excluded, and so this warning was disabled as part of the Compact Profiles work.

The classlists need to be made profile-aware. But also see JDK-7032729 as to whether this whole jar reordering business is worthwhile in the first place.
Comments
JDK-8150044 moved generation of classlists to build time and initially limits what is put in the to java.base and java.logging, which coincidentally is part of the java compact1 profile, thus no warnings are emitted for most images - and only a few for an image limited to only java.base.
17-06-2016
Changing to an enhancement request. The determination of whether jar re-ordering is still beneficial (JDK-7032729) upon which this request depends is also an enhancement request.
18-04-2013