-
Notifications
You must be signed in to change notification settings - Fork 15
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
Access to file of DefaultUnresolvedArtifactResult in MavenDependencyExport #12
Comments
Is there an artifact on Maven Central which will show the error? Or are you seeing the issue with an artifact from an internal repo? I think a flag to control the behaviour might be best. Eg
This would allow the build to fail for unresolvable depencies, I'm not sure if that's desirable behaviour (I need to understand what an unresolvable dependency is) |
Also, have you seen this?
|
Yes, the same check is done here too: But it doesnt matter if the configuration is resolvable when the artifacts in them might not be. |
Please see the PR. |
There is an access to the file property of an unresolvable artifact in MavenDependencyExport.groovy:
https://github.com/uklance/gradle-dependency-export/blob/master/src/main/groovy/com/lazan/dependency/export/MavenDependencyExport.groovy#L154
I think the
component.getArtifacts(MavenPomArtifact).
should be extended by filtering of the artifacts so we only use resolvable ones.If i find some time i will look into that myself but currently im very busy.
Best regards, Stefan
The text was updated successfully, but these errors were encountered: