You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be practical to organize these files by release so users are less likely have multiple jarfiles for the same classes but different versions in the same space. At least some kind of structure (branches?) or .md help that'd make it easier for users to pick the complete and consistent set of latest jarfiles.
Maybe I'll fork and PR something later, but if there are any existing ideas around this (other than this being an interim solution pending maven availability), I'm happy to learn.
The text was updated successfully, but these errors were encountered:
Any PRs are welcome of course.
The main idea of the repository is to have something temporary before we
publish it in maven.
Looks like temporary solutions could live longer as expected sometimes.
On Mon, Nov 30, 2020 at 11:20 AM Benjamin De Boe ***@***.***> wrote:
I think it would be practical to organize these files by release so users
are less likely have multiple jarfiles for the same classes but different
versions in the same space. At least some kind of structure (branches?) or
.md help that'd make it easier for users to pick the complete and
consistent set of latest jarfiles.
Maybe I'll fork and PR something later, but if there are any existing
ideas around this (other than this being an interim solution pending maven
availability), I'm happy to learn.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVHEPYNLZUKGMPXO5CNOT3SSNIVVANCNFSM4UHHHTVQ>
.
I think it would be practical to organize these files by release so users are less likely have multiple jarfiles for the same classes but different versions in the same space. At least some kind of structure (branches?) or .md help that'd make it easier for users to pick the complete and consistent set of latest jarfiles.
Maybe I'll fork and PR something later, but if there are any existing ideas around this (other than this being an interim solution pending maven availability), I'm happy to learn.
The text was updated successfully, but these errors were encountered: