-
Notifications
You must be signed in to change notification settings - Fork 13
Split libraries into independent Gradle projects #93
Split libraries into independent Gradle projects #93
Conversation
2b3d29d
to
4646917
Compare
Question for you @notmandatory: do you think the license files should be added to each of the directories? It feels that way to me, just so there is no mistaking it (even though it's sort of obvious). |
414bb98
to
5450c08
Compare
bdk-jvm/plugins/README.md
Outdated
@@ -0,0 +1,16 @@ | |||
# Readme | |||
The purpose of this directory is to host the Gradle plugin that add tasks for building the native binaries required by bdk-jvm, and building the language bindings files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
language nit
The purpose of this directory is to host the Gradle plugin that add tasks for building the native binaries required by bdk-jvm, and building the language bindings files. | |
The purpose of this directory is to host the Gradle plugin that adds tasks for building the native binaries required by bdk-jvm, and building the language bindings files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 5450c08
I found one very small language nit.. but other than that looks good. I locally tested the android and jvm build and test maven tasks on my Mac M1.
Looks like you also may need to do a rebase. |
5450c08
to
d603932
Compare
Description
This PR refactors the repository into two directories, each containing separate libraries as completely independent Gradle builds/projects.
Note that in order to be really careful I fixed the CI publishing workflow but brought it back to simply publishing to the staging repository (it's easy to make a typo and send the compiled binaries to the wrong directory) so that we can check them and see that everything is in the right place before publishing if we trigger the workflow and everything works well we can just make a quick fix that does the full publishing and merge that on the day of the release.
Notes to the reviewers
This is a big refactor so I want to make sure I think of everything:
Checklists