-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect transitive dependencies for supported libraries #75
Comments
Actually, |
Hmm, maybe I did not phrase this very clearly. I am just wondering why it is necessary for supported libraries to re-declare all dependencies from the Maven POM inside of the JSON library descriptor? In all of the supported libraries, they need to declare the dependencies in the JSON like so:
These edit: Maybe the current behaviour makes sense. I guess it probably shouldn't import the transitive closure of all dependencies by default. |
Yes, I understand. I think, these transitive dependencies may be safely deleted, it just needs to be checked. |
I can confirm this now works as expected, previously there was some issue detecting dependencies that seems to have been fixed. Some of the officially supported libraries (e.g. Spark) submitted before the fix still include the transitive deps. Thanks! |
I wonder if there is a way to import transitive dependencies by default for supported libraries imported with the
%use
keyword in the same way as the@file:DependsOn(<coordinates>)
/@file:Repository(<absolute-path>)
syntax does. Why is it necessary to re-declare all the transitive dependencies for supported libraries in thejson
library descriptor like so?The text was updated successfully, but these errors were encountered: