-
Notifications
You must be signed in to change notification settings - Fork 6
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
Break Gradle plugin out of pbj-core and pbj-compiler #260
Comments
rbair23
added a commit
that referenced
this issue
May 31, 2024
rbair23
added a commit
that referenced
this issue
Jun 15, 2024
rbair23
added a commit
that referenced
this issue
Jun 27, 2024
rbair23
added a commit
that referenced
this issue
Jun 27, 2024
rbair23
added a commit
that referenced
this issue
Jun 28, 2024
rbair23
added a commit
that referenced
this issue
Jun 28, 2024
rbair23
added a commit
that referenced
this issue
Aug 21, 2024
rbair23
added a commit
that referenced
this issue
Aug 21, 2024
rbair23
added a commit
that referenced
this issue
Aug 21, 2024
rbair23
added a commit
that referenced
this issue
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PBJ project has a funky build due to the fact that it builds a plugin, and that plugin is part of the pbj-compiler project. I think we could instead rearrange the project such that:
The compiler depends on the runtime, the gradle plugin depends on both, and the helidon plugin depends on all three. There would be a single multi-project gradle build, and each of the above would be a different module.
The text was updated successfully, but these errors were encountered: