Yes this is what I’m suggesting - except we already have a separate repository for accord and several other systems (like dtest api, sidecar etc), and for these it makes sense to have a separate repository for shared functionality.On 17 Mar 2025, at 07:20, Jon Haddad wrote:It should be possible t
That gets my vote as well Joan Haddad
On 17/3/25 8:19, Jon Haddad wrote:
It should be possible to modularize the code without breaking it into
separate repos. I don't know how to do it with ant, but with Gradle
[1] you use subprojects. I think Maven calls them multi module
projects [2]. The
It should be possible to modularize the code without breaking it into
separate repos. I don't know how to do it with ant, but with Gradle [1]
you use subprojects. I think Maven calls them multi module projects [2].
They're just folders in the same repo that are treated as dependencies.
For exampl
I can only speak for myself, but the overhead of managing the accord submodule has been fairly low. It does mean opening two PRs when a change touches both projects (which is often the case for accord), but I think for utility classes this would be infrequent anyway.I think any modules within Cassa
