Skip to content
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

Prune some test worker dependencies #29217

Merged
merged 1 commit into from
May 28, 2024

Conversation

jvandort
Copy link
Member

The eventual goal is for ForkedTestClasspathFactory to not need a hard-coded list of gradle modules for worker classpaths. We should be able to generate that automatically based on the real dependencies of the test worker's runtime classpath.

This commit begins to clean up the dependency graph of the test classpath, removing some dependencies on Gradle modules and external dependencies that don't necessarily need to be there. There is still quite some work to do, but this starts the process.

Reviewing cheatsheet

Before merging the PR, comments starting with

  • ❌ ❓must be fixed
  • 🤔 💅 should be fixed
  • 💭 may be fixed
  • 🎉 celebrate happy things

@lptr
Copy link
Member

lptr commented May 27, 2024

Can we move this forward?

@jvandort jvandort force-pushed the jvandort/testing/prune-dependencies branch 3 times, most recently from eb019ea to 7cb355f Compare May 28, 2024 15:10
@jvandort
Copy link
Member Author

@bot-gradle test this

@bot-gradle
Copy link
Collaborator

I've triggered the following builds for you. Click here to see all build failures.

@jvandort jvandort self-assigned this May 28, 2024
@jvandort jvandort added this to the 8.9 RC1 milestone May 28, 2024
The eventual goal is for ForkedTestClasspathFactory to not need a hard-coded list of gradle modules
for worker classpaths. We should be able to generate that automatically based on the real dependencies
of the test worker's runtime classpath.

This commit begins to clean up the dependency graph of the test classpath, removing some dependencies
on Gradle modules and external dependencies that don't necessarily need to be there. There is still
quite some work to do, but this starts the process.
@jvandort jvandort force-pushed the jvandort/testing/prune-dependencies branch from 7cb355f to fc494af Compare May 28, 2024 15:59
@jvandort
Copy link
Member Author

@bot-gradle test this

@bot-gradle
Copy link
Collaborator

I've triggered the following builds for you. Click here to see all build failures.

@jvandort jvandort marked this pull request as ready for review May 28, 2024 16:16
@jvandort jvandort requested review from a team as code owners May 28, 2024 16:16
@jvandort jvandort requested a review from big-guy May 28, 2024 16:16
@jvandort jvandort added this pull request to the merge queue May 28, 2024
@bot-gradle
Copy link
Collaborator

The merge queue build has failed. Click here to see all failures.

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 28, 2024
@jvandort jvandort added this pull request to the merge queue May 28, 2024
Merged via the queue into master with commit 3ad1c45 May 28, 2024
53 checks passed
@jvandort jvandort deleted the jvandort/testing/prune-dependencies branch May 28, 2024 22:12
sb.append(")");
}

return sb.toString();
}

// Can be replaced with String.join when workers are updated to run in JDK 8.
private static String join(Set<String> strings, String delimiter) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about CollectionUtils.join(...)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants