-
Notifications
You must be signed in to change notification settings - Fork 119
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
Would you clean up dependency tree? #507
Comments
Thanks for catching this and opening the issue! I'll investigate further and see if we can exclude some of these dependencies. |
hi @suztomo, I'm trying to reproduce the error you posted by adding the linkage checker to the enforcer rules, but I'm getting a lot of extra errors. This is the result after upgrading to v1.5.9 of
|
@shubha-rajan I see. I tried your branch and didn't face the missing artifacts problem (and saw these extra errors). The Maven enforcer rule relies on Maven to build dependency graph and therefore it does not get the same result as GoogleCloudPlatform/cloud-opensource-java#2073. Would you try running this DependencyTreePrinter in your IDE after checking out the cloud-opensource-repository https://github.com/GoogleCloudPlatform/cloud-opensource-java/blob/master/dependencies/src/main/java/com/google/cloud/tools/opensource/dependencies/DependencyTreePrinter.java#L23 and installing 1.2.4-SNAPSHOT locally? |
Thank you for the exclusion. I tried the main branch (448a353) in my local and the dependency tree looks good https://gist.github.com/suztomo/c6bb632b4af6dc8e7eb66ae35e77ae8f I tried with the failing test (GoogleCloudPlatform/cloud-opensource-java#2073) with the snapshot version but somehow it still fails. I'll dig further and will update you.
InvestigationI was only looking at com.google.cloud.sql:cloud-sql-connector-r2dbc-core when I created this issue. But there are still unresolved artifacts referenced from other artifacts in this repository (cloud-sql-connector-r2dbc-mysql and cloud-sql-connector-jdbc-sqlserver).
Memo for myself: the errors are visible only using the debugger at LinkageChecker. Even after I remove micrometer-core, there's still a dependency path to xerces-impl.
|
For GoogleCloudPlatform#507 GoogleCloudPlatform/cloud-opensource-java#2073 shows MaximumLinkageErrorsTest failing due to missing xerces-impl artifact. Explicitly excluding the dependencies that touch xerces-impl resolves the issue. Note that even after these exclusions, MaximumLinkageErrorsTest fails due to new linkage errors.
For GoogleCloudPlatform#507 GoogleCloudPlatform/cloud-opensource-java#2073 shows MaximumLinkageErrorsTest failing due to missing xerces-impl artifact. Explicitly excluding the dependencies that touch xerces-impl resolves the issue. Note that even after these exclusions, MaximumLinkageErrorsTest fails due to new linkage errors.
For #507 GoogleCloudPlatform/cloud-opensource-java#2073 shows MaximumLinkageErrorsTest failing due to missing xerces-impl artifact. Explicitly excluding the dependencies that touch xerces-impl resolves the issue. Note that even after these exclusions, MaximumLinkageErrorsTest fails due to new linkage errors.
Feature Description
I tried to add the the libraries in this repository into the BOM (GoogleCloudPlatform/cloud-opensource-java#2073) but the tool detected there's transitive dependencies that are not available in Maven Central:
Would you cleanup the dependency tree (probably excluding unnecessary dependencies)?
Alternatives Considered
N/A
Additional Context
Linkage Checker enforcer rule should reproduce the same error above:
https://github.com/GoogleCloudPlatform/cloud-opensource-java/wiki/Linkage-Checker-Enforcer-Rule
The text was updated successfully, but these errors were encountered: