Could you please provide additional information on what Eclipse version was being run? I was not able to reproduce it on Trusty using Eclipse 3.8.1-5.1 on Trusty (AMD64).
Steps to test:
1. Run Eclipse, create a Java Project (not sure this was needed), close
2. Manually rename any jar file inside a JRE/JDK lib that is configured in Eclipse (eg. icedtea-audio.jar <-> pulse-audio.jar)
3. Start Eclipse again
4. Verify that Eclipse did properly detect the new/renamed jar files for any and all configured JRE's
I believe the original error was actually on Eclipse and not OpenJDK. Eclipse should have been able do detect JAR changes on a JRE environment and update its internal state accordingly. Since it is behaving in the expected way now it should be safe to close this.
Could you please provide additional information on what Eclipse version was being run? I was not able to reproduce it on Trusty using Eclipse 3.8.1-5.1 on Trusty (AMD64).
Steps to test:
1. Run Eclipse, create a Java Project (not sure this was needed), close
2. Manually rename any jar file inside a JRE/JDK lib that is configured in Eclipse (eg. icedtea-audio.jar <-> pulse-audio.jar)
3. Start Eclipse again
4. Verify that Eclipse did properly detect the new/renamed jar files for any and all configured JRE's
I believe the original error was actually on Eclipse and not OpenJDK. Eclipse should have been able do detect JAR changes on a JRE environment and update its internal state accordingly. Since it is behaving in the expected way now it should be safe to close this.
Thanks!