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

[Enhancement] Move the version variables of third-party middlewares from gradle.properties to build.gradle #5008

Open
2 of 3 tasks
Pil0tXia opened this issue Jun 20, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request good first issue Issues for first-time contributors

Comments

@Pil0tXia
Copy link
Member

Search before asking

  • I had searched in the issues and found no similar issues.

Enhancement Request

Currently, the version definitions of third-party middleware for connectors and storage plugins are in the gradle.properties file. Dependabot does not upgrade the versions in the gradle.properties file because it is considered a configuration file for the Gradle JVM itself, rather than a part of dependency management. This has led to most connectors lagging behind the latest versions, reducing their usability.

Describe the solution you'd like

There are several reasons to move the version variables of third-party middleware to build.gradle:

  1. The gradle.properties file can be edited and modified by users to match the middleware versions they are using. However, whether modifying gradle.properties or build.gradle, it requires recompiling from the source code or replacing the binary package with the target version.
  2. Higher versions of the SDK are often backward compatible with lower versions of the middleware. However, when upgrading to higher version dependencies, the API of lower version source code may change. Using Dependabot for small-step upgrades reduces the upgrade cost.

If there are any issues, feel free to discuss.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Pil0tXia Pil0tXia added enhancement New feature or request good first issue Issues for first-time contributors labels Jun 20, 2024
Copy link
Contributor

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.

@github-actions github-actions bot added the Stale label Sep 18, 2024
@melisolmez
Copy link
Contributor

Hello, can ı work on this issue ?

@github-actions github-actions bot removed the Stale label Sep 23, 2024
@Pil0tXia
Copy link
Member Author

@melisolmez Of course, welcome to Apache EventMesh community.

@DheerajBishnoi
Copy link

@melisolmez Do you need any help in this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Issues for first-time contributors
Projects
None yet
Development

No branches or pull requests

3 participants