Community
Participate
Working Groups
In some configurations it's not possible to avoid having jars appear multiple times on the classpath (*). The result is a significant problem, e.g., see http://www.glassbox.com/forum/forum/viewthread?thread=92 I believe this is a normal condition and the warning should be replaced with a INFO level AspectJ trace message instead. However, I'd be happy with an option to suppress this warning (e.g., a dreaded Xlint option?) (*) Notably on some servers resources in jars in the bootstrap classpath are found multiple times. I've found that the bootstrap classpath is, for some servers, the only location where a jar file can be placed to be shared across all loaders in the system.
Also, I don't want to suppress all warnings to suppress this one.
Created attachment 54733 [details] This patch makes duplicate jar files a debug-level message, not a warning, since I believe it's a normal, valid configuration.
This message and the accompanying logic was added to help solve a genuine configuration problem. I am reluctant to hide a message that 90% of the time indicates that the user has made a mistake and I don't like abusing Xlint. Can you tell me how issuing this message caused the OutOfMemoryError that was reported?
something we can do here?
unsetting the target field which is currently set for something already released
