Elias Torres wrote:
Dave wrote:
Drat. I hit the send button too soon.
How about this: since we are basically done with Roller 4.0 features
and we probably won't be adding any more, let's make the switch to the
roller_4.0_newbackend branch now.
svn mv trunk branches/roller_4.0_oldbackend
svn mv branches/roller_4.0_newbackend trunk
We'll make JPA the default back-end but we'll keep Hibernate in place
so that you can use it if you need to do any deployments or builds.
I'll set up my build servers to test both the Hibernate and JPA
implementations. And you can work exclusively in Hibernate if you wish
and I'll take the JPA side, as we are doing now but in one branch
instead of two.
That will make it easy for folks (like Elias) to test JPA, easy for me
to deploy JPA and will eliminate the dreadful merge work that is
making the new installer and DI work a pain in the you know what. We
could even make some early access builds available so others can help
with testing -- we need a lot more testing this time because of
Struts2 and JPA.
The irritating double implementation business will only exist for a
relatively short time: until we have enough confidence in JPA to
delete Hibernate from SVN.
Could that work?
- Dave
I'm ok with the double impl for a bit. I'll try to find some time to
test the new implementation.
I am okay with that as well, but before you make that change I'd like to
finish testing some i18n fixes i have in my workspace and commit them.
Also, in the newbackend branch you added that 'core' component and put
some code in there which I still not sure about. You have a bunch of
persistence specific code there and I think we should talk about whether
or not that is really the right place for that code. This doesn't have
to be done beforehand, but we should do it right after it's done.
We should also talk about moving the weblogger code into it's own place
under apps/weblogger like we did with the planet stuff. We had been
wanting to put this off for a bit while 3.1 was being finalized, but now
that 3.1 is out we can probably move forward with this.
-- Allen
... and yes don't wait for IBM to get through lawyers to give the iBatis
backend for comparison. I'll say it again, if the performance is
good/better than Hibernate we'd rather not raise any obstacles for
Roller's progress.
-Elias
