Skip to content

Make the mavenTest integration test more robust #3315

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

Closed
wants to merge 8 commits into from

Conversation

dkhalanskyjb
Copy link
Collaborator

Now, it checks explicitly that the classes it analyzes were taken
from the local Maven repository. Additionally, the build script was
tweaked so that accidentally setting the dependencies for this
subproject is ignored.

mvicsokolova and others added 8 commits May 31, 2022 16:11
Now, it checks explicitly that the classes it analyzes were taken
from the local Maven repository. Additionally, the build script was
tweaked so that accidentally setting the dependencies for this
subproject is ignored.
classpath += mavenTestClasspathConfiguration
/* the order is this way because the first match is used, and if we ever accidentally add the wrong dependencies to
this source-set, they shouldn't override the dependencies to the local Maven repository */
classpath = mavenTestClasspathConfiguration + classpath
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

With this, I was unable to make the new check fail, even trying to specify the dependencies for this source set in various places.

@qwwdfsad
Copy link
Member

qwwdfsad commented Jun 8, 2022

Is it left as a draft intentionally?

@dkhalanskyjb
Copy link
Collaborator Author

Yes. If we decide to make integration-testing a separate project, this becomes irrelevant.

@mvicsokolova mvicsokolova force-pushed the integration-test-branch branch from 3dcca74 to d8bc9e4 Compare June 10, 2022 10:22
Base automatically changed from integration-test-branch to develop June 15, 2022 17:22
@qwwdfsad qwwdfsad closed this Jun 22, 2022
@dkhalanskyjb dkhalanskyjb deleted the more-robust-mavenTest branch May 17, 2023 12:34
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.

3 participants