Extensions Library Modularization #84
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexjhawk
force-pushed
the
dev/2.0.0-modular
branch
3 times, most recently
from
30bc678 to
ad63997
Compare
alexjhawk
force-pushed
the
dev/2.0.0-modular
branch
from
ad63997 to
c605c9a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While this project may introduce significant variations between the Maven environment provided by the starter project, the goal with modularization is to maintain our existing library code but make it lighter.
By modularizing, connectors can selectively import the required library modules without the overhead of including the remaining modules (both during runtime and in overall Jar size).
It is expected that this PR will cause several build failures. These will be addressed/resolved using upgrades to the automation to support the modular Maven project structure. In addition, the release documentation will be updated to describe the necessary information for each module to be installed/imported. This will likely result in the usage of JitPack for distribution. While our current Maven repository structure remains operational, the number of new/separate Jars and files associated with modularization will rapidly make it messy and difficult to manage. JitPack already runs on its own for all public GitHub repos, so there is little to no effort on our end to switch to this form of distribution for the extensions library.
Edit: See https://jitpack.io/#hms-networks/sc-ewon-flexy-extensions-lib/dev~2.0.0-modular-SNAPSHOT for testing