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
Currently dependencies are added to the java.class.path in a strict order, most notably: import dependencies go before external dependencies. This prevents the ability of users to package their config files alongside the application and have changes in them take effect without explicitly removing these configs from .jar resources (because JVM will search java.class.path for these resources and will find unchangeable configs in executable, before the configs in package).
The text was updated successfully, but these errors were encountered:
I think that the order in dependencies of jet plugin should be respected in java.class.path. This way reordering dependencies in jet plugin will take affect on java.class.path directly
Currently dependencies are added to the
java.class.path
in a strict order, most notably: import dependencies go before external dependencies. This prevents the ability of users to package their config files alongside the application and have changes in them take effect without explicitly removing these configs from .jar resources (because JVM will searchjava.class.path
for these resources and will find unchangeable configs in executable, before the configs in package).The text was updated successfully, but these errors were encountered: