First, thanks for implementing my previous proposals, java-config is much improved. Additional proposals: 1) Ability to remove a package from classpaths no matter where it is in the classpath. 2) When a user upgrades a library the old version is still in the classpaths. Add a switch to java-config that will take a package name as argument, search for occurrences of that package in the current classpath, remove it and add the new version to the classpath. Another version of this could be used by build scripts to do that for system classpath on emerge update. Reproducible: Always Steps to Reproduce: 1. 2. 3.
More readible version of 2): When a user upgrades a library the old version is still in the classpaths. Add a switch to java-config that will take a package name as argument, search for occurrences of that package in the current classpath, remove it and add the new version to the classpath. Another version of this could be used by build scripts to do that for system classpath on emerge update.
*** This bug has been marked as a duplicate of 47697 ***
This bug has clarification on it and it's marked as a blocker for 31468 so I'm going to mark the other one the dupe.
*** Bug 47697 has been marked as a duplicate of this bug. ***
won't
