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

Inconsistent dependency versions across modules. #1725

Open
chaicho opened this issue Mar 21, 2024 · 5 comments
Open

Inconsistent dependency versions across modules. #1725

chaicho opened this issue Mar 21, 2024 · 5 comments
Assignees
Labels
enhancement New feature request or improvement on an existing feature status: Needs triage Applied to all new issues

Comments

@chaicho
Copy link

chaicho commented Mar 21, 2024

Describe the problem

Currently some modules of gtfs-validator are using the same dependency. However, some of these dependencies' versions are not centrally managed and therefore cause discrepancy. This increases the maintenance workload and may lead to dependency conflict for downstream projects. So it's better to align the versions of the dependencies if the discrepancy is not intentional.

The affected dependencies are listed below.

  1. org.apache.commons:commons-lang3 has version 3.6 in processor but version 3.0 in core and processor/notices
  2. com.google.auto.service:auto-service has version 1.0-rc4 in processor but version 1.0.1 in processor/notices
  3. com.google.flogger:flogger and com.google.flogger:flogger-system-backend has version 0.6.0 in all modules , but version 0.5.1 in output-comparator

Proposed solution

Align the versions of the dependencies to ensure consistency and avoid possible conflicts. And if it's possible, manage the versions of the dependencies centrally.

If you could kindly tell me whether these actions are intentional, I'd be happy to help :).

Alternatives you've considered

No response

Additional context

No response

@chaicho chaicho added enhancement New feature request or improvement on an existing feature status: Needs triage Applied to all new issues labels Mar 21, 2024
Copy link

welcome bot commented Mar 21, 2024

Thanks for opening your first issue in this project! If you haven't already, you can join our slack and join the #gtfs-validators channel to meet our awesome community. Come say hi 👋!

Welcome to the community and thank you for your engagement in open source! 🎉

@chaicho
Copy link
Author

chaicho commented Apr 8, 2024

@jcpitre Could you help me review this issue? Many thanks :)

@jcpitre
Copy link
Contributor

jcpitre commented Apr 8, 2024

@jcpitre Could you help me review this issue? Many thanks :)

Hi @chaicho, this issue is assigned to me but unfortunately I will have limited availability for the next 2 weeks. Is this something you consider urgent?

@chaicho
Copy link
Author

chaicho commented Apr 8, 2024

Hi @chaicho, this issue is assigned to me but unfortunately I will have limited availability for the next 2 weeks. Is this something you consider urgent?

Hi @jcpitre, thanks for getting back to me. While it's not urgent, it would be helpful to have confirmation on the discrepancy so that I can address it accordingly, either by fixing it locally or raising a pull request myself :).

I completely understand the situation, and I don't want to add any unnecessary pressure. If it's too much to handle right now, I'm more than willing to wait until you have more time available :).

@emmambd emmambd assigned davidgamez and unassigned jcpitre Apr 15, 2024
@davidgamez
Copy link
Member

Hi @chaicho, I took a pick, and as you mentioned, there are a few discrepancies in the dependencies' versions. I don't have the complete picture of why versions defer, but they don't seem to be on purpose. Having centralized versions for the dependencies is very helpful and reduces maintenance issues/conflicts. This is a good time for this change, as we will have enough time to test it before the next GTFS release. If you have time to work on this issue, we will welcome and review your PR. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature request or improvement on an existing feature status: Needs triage Applied to all new issues
Projects
None yet
Development

No branches or pull requests

3 participants