Ok, once you have set up the new repo, I will trawl GitHub for any
guice-persist libraries that seem relevant, and just let the repo owners
know about this initiative
On 12 September 2017 at 09:50, Stephan Classen wrote:
> Agree the more collaborators and users we attract the
Agree the more collaborators and users we attract the better. Lack of
users and collaborators was the reason why apache onami was discontinued
and went to attic.
On 12.09.2017 10:47, David Sowerby wrote:
I agree about the single focus - I wasn't suggesting diluting the
purpose of the library
I agree about the single focus - I wasn't suggesting diluting the purpose
of the library - I was thinking more that those who have developed
libraries based on guice-persist who may be wondering about being dependent
on it, and possibly also willing to collaborate
On 12 September 2017 at 09:43,
Maybe in a second phase. I would first concentrate on pulling the
different efforts for onami-persist together. But personally I prefer to
focus on one responsibility with such libraries. And I see the main
responsibility of onami-persist in providing JPA and JTA integration for
guice.
On
Seems like a good plan to me. Persistence isn't my strong suit, but I am
certainly happy to help, and contribute where I can.
Do you think it is worth contacting people who have Guice integrations
with guice-persist, as that seems to be defunct? I'm thinking of projects
like this one
So a quick search on github finds 3 forks of onami-persist.
https://github.com/tocktix/onami-persist
https://github.com/FingolfinTEK/onami-persist
https://github.com/davidsowerby/krail-jpa
Is there interest in joining forces? If so I would suggest I start a new
github organization for