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

poms: Replace hardcoded version by §{project.parent.version}? #3575

Closed
kt86 opened this issue Nov 19, 2024 · 0 comments · Fixed by #3618
Closed

poms: Replace hardcoded version by §{project.parent.version}? #3575

kt86 opened this issue Nov 19, 2024 · 0 comments · Fixed by #3618
Assignees
Labels

Comments

@kt86
Copy link
Contributor

kt86 commented Nov 19, 2024

          @Janekdererste :

Shouldn't we use this expression §{project.parent.version} in all poms instead of the hard-code version 2025-.... in all dependencies in the different poms?
Then, the version it is only there once per pom.

I know, that in practice this does not make a huge difference, as soon, as the update is done by search/replace all... but is looks a bit cleaner for me.

Originally posted by @kt86 in #3574 (comment)

@kt86 kt86 moved this to inbox / to discuss in MATSIM advanced weekly hackathon Nov 19, 2024
@kainagel kainagel closed this as completed by moving to To Be Reported in MATSIM advanced weekly hackathon Nov 25, 2024
@kainagel kainagel reopened this Nov 25, 2024
@kt86 kt86 closed this as completed in #3618 Dec 2, 2024
@kt86 kt86 moved this from In Progress to To Be Reported in MATSIM advanced weekly hackathon Dec 2, 2024
@kt86 kt86 assigned kt86 and unassigned Janekdererste Dec 2, 2024
@kainagel kainagel moved this from To Be Reported to Done in MATSIM advanced weekly hackathon Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

3 participants