You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 23, 2025. It is now read-only.
It looks like jar files generated using the groovy_library rule, unlike the ones generated with the java_library one, don't contain directory entries.
For instance, given a java class Test.class under the com.example package, the resulting jar file would contain the following entries (excluding the META-INF directory):
com/
com/example/
com/example/Test.class
At runtime, the following code will then work as expected, returning a URL to the jar file:
The same does not work (the URL returned is null) with a jar generated with the groovy_library rule because the only entry in it is: com/example/Test.class.
It looks like jar files generated using the groovy_library rule, unlike the ones generated with the java_library one, don't contain directory entries.
For instance, given a java class Test.class under the com.example package, the resulting jar file would contain the following entries (excluding the META-INF directory):
At runtime, the following code will then work as expected, returning a URL to the jar file:
The same does not work (the URL returned is null) with a jar generated with the groovy_library rule because the only entry in it is: com/example/Test.class.