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

Use ForgeFlower #33

Open
jamierocks opened this issue Jan 8, 2018 · 2 comments
Open

Use ForgeFlower #33

jamierocks opened this issue Jan 8, 2018 · 2 comments

Comments

@jamierocks
Copy link
Contributor

  1. Cleanup existing patches
  2. Start using ForgeFlower
@jamierocks jamierocks self-assigned this Jan 8, 2018
@caseif
Copy link
Member

caseif commented Oct 9, 2019

The primary blocker to this at the moment is ForgeFlower's use of gitpatcher. Gradle forbids the same plugin to be used twice within a project, so we'd need to figure out how to convince it to build it as a subproject while still applying patches to both projects.

@jamierocks
Copy link
Contributor Author

Possible solution to to have a repo with Forge's changes applied that we can reference rather than the actual repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants