Message9217

Dear Brian,

thanks for looking into this. I think, the situations described here and in http://bugs.jython.org/issue1383 are different:

The example provided here works perfectly fine if the JAVA_HOME variable is set to a Java 7 environment, whereas it breaks when JAVA_HOME is set to Java 8.

Most of the reported problems around wild card imports seem to be related to package scanning. If the packages were not scanned, wild card imports did not work at all. 

In this example the import from java.util import * works for some classes (e. g. I can construct a java.util.ArrayList or instantiate a java.util.Date). Just using static methods from the Arrays class does not seem to work.


The article on stack overflow

http://stackoverflow.com/questions/1681849/why-does-jython-refuse-to-find-my-java-package

indicates that not using wild card imports is "the recommended way" of importing classes. Is that the case? Does Jython "explicitly" discourages the use of wildcard imports? If this was the case, we could tell this to our customers in case that they report this type problem ("Why is my Jython script no longer working after switching to Java 8").

Thanks for your help

Best regards



Bernd