Closed quintesse closed 8 years ago
Good point, I don't really know why I did not do it for Jars… I'm sure I must have had an evident great reason…
Of course ;)
Done.
And for the existing JARs? Will we run some one-time upgrade script or something?
Or wait until they're obsolete and rely on the new ones to fix this.
It would be useful to have the list of member classes that exist in a JAR and store it in the DB just as we do for CARs. The
import-jar
command for example could then also suggest legacy modules for missing dependencies instead of only Ceylon modules as it does now.