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

Add MergedProperties #226

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add MergedProperties #226

wants to merge 2 commits into from

Conversation

jpenilla
Copy link
Member

No description provided.

jpenilla added a commit to PaperMC/Paper that referenced this pull request Nov 29, 2023
This is an alternate way to share dependency versions between api & server to version catalogs (#9974), which have the problem where any catalog change that impacts the generated accessor ABI will cause the entire paperweight pipeline to run again (which makes it impractical for our use case)

If we decide to go forward with this, will need to merge PaperMC/paperweight#226 and make a paperweight release first.
@MiniDigger
Copy link
Member

I wonder if there should be a duplicate check, if a property is defined in multiple property files, that could lead to really meh to find issues and should never be acceptable anyways?

@jpenilla
Copy link
Member Author

jpenilla commented Nov 29, 2023

Hm, probably. The more I think about this though the more I start to think we should just pull the versions out of the patches and go with a version catalog in the root project. It should be pretty trivial for forks to pull it in similar to the generated api.

(would need to check if this would cause forks to run the pipeline again after applying patches)

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.

2 participants