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

Moves the repository declarations to the settings.gradle file #4161

Merged
merged 1 commit into from
Feb 21, 2024

Conversation

dlvenable
Copy link
Member

Description

This PR moves the Maven repository declarations to the settings.gradle file. This consolidates all usage there.

Additionally, this PR adds a limit the groups used by the JitPack Maven repository. This repository is only needed for the com.github.fge:json-schema-validator dependency in the Kafka plugins. Now, Data Prepper will not pull anything other than that Maven group from JitPack.

Issues Resolved

N/A

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

… maintain in one place. Also limit the groups used by the JitPack Maven repository to the one dependency that is needed. This way, we use Maven Central over it.

Signed-off-by: David Venable <[email protected]>
@asuresh8
Copy link
Contributor

Are the failing tests related to this change?

@dlvenable
Copy link
Member Author

Are the failing tests related to this change?

@asuresh8 , No. I recently noticed the Kafka 2.8.1 tests are failing. I created an issue for that: #4168.

The Java 21 build failure was probably flaky and I restarted it.

Copy link
Collaborator

@chenqi0805 chenqi0805 left a comment

Choose a reason for hiding this comment

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

LGTM. Does it mean any sub project no longer needs to specify the repositories?

@dlvenable
Copy link
Member Author

LGTM. Does it mean any sub project no longer needs to specify the repositories?

Sort of. This repositories were declared to be available to all sub-projects. So they haven't actually needed to specify them. See #4152 where I removed them from other projects. But, this is another way to accomplish something similar.

@dlvenable dlvenable merged commit 049732a into opensearch-project:main Feb 21, 2024
71 of 74 checks passed
@dlvenable dlvenable deleted the repositories-settings branch March 6, 2024 16:44
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