You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@empire-db.apache.org by Rainer Döbele <do...@esteam.de> on 2022/02/14 17:23:18 UTC
Empire-db version 3.0.0 state of development / Migration of modules
Hi all,
as announced I have started working on Empire-db version 3.0.0 in order modernize it for the 2020s.
I am happy to announce that I have reviewed and optimized almost every part and it looks awesome in my opinion.
At the start I would have not imagined that there was so much potential.
Empire-db 3.0 rocks!
To get more information look at the Jira tickets EMPIREDB-362 to EMPIREDB-372.
Or even better, get the "version3" branch from git (https://gitbox.apache.org/repos/asf/empire-db.git ) and run the examples.
A lot of classes and function have been renamed, removed or altered.
Migrating code from projects using the version 2.x branch is possible but requires some work and attention.
(I might do a migration guide later)
I am planning on merging the version3 branch with the head in the coming days.
Any objections anyone?
Now about the modules:
The following modules have been update to version 3:
Apache Empire-db Core ..............................
Apache Empire-db Java Server Faces 2.x extensions ..
Apache Empire-db Code Generator ....................
Apache Empire-db Maven Plugin ......................
Apache Empire-db Maven Codegen Example .............
Apache Empire-db Basic Example .....................
Apache Empire-db Advanced Example ..................
Apache Empire-db JSF2 Example ......................
Apache Empire-db Vue.js Example ....................
However, I have NOT converted any of the following modules:
Apache Empire-db CXF Example .......................
Apache Empire-db Spring JDBC Template ..............
Apache Empire-db Spring Example ....................
Apache Empire-db Struts2 Extension .................
Apache Empire-db Struts2 Example ...................
Apache Empire-db Struts2/CXF Example ...............
Originally the Stuts2 Extensions had been provided by me, but I am not planning on continuing Struts2 support myself.
As I have no experience with Spring, I am unable to do the migration myself. Same with CXF.
So what should we do with this leftover modules?
Anyone willing to convert them to version 3?
Re: Empire-db version 3.0.0 state of development / Migration of modules
Posted by Jan Glaubitz <ja...@glaubitz.org>.
Hello Rainer,
sounds and looks interesting!
I’d like to try it out with my existing projects. Can you provide a small migration guide / getting started guide?
I’m using PostgreSQL and have some postgres-specific functions implemented. I hope I can get them work again ;)
- jan
> Am 14.02.2022 um 18:23 schrieb Rainer Döbele <do...@esteam.de>:
>
> Hi all,
>
> as announced I have started working on Empire-db version 3.0.0 in order modernize it for the 2020s.
> I am happy to announce that I have reviewed and optimized almost every part and it looks awesome in my opinion.
> At the start I would have not imagined that there was so much potential.
>
> Empire-db 3.0 rocks!
>
> To get more information look at the Jira tickets EMPIREDB-362 to EMPIREDB-372.
> Or even better, get the "version3" branch from git (https://gitbox.apache.org/repos/asf/empire-db.git ) and run the examples.
>
> A lot of classes and function have been renamed, removed or altered.
> Migrating code from projects using the version 2.x branch is possible but requires some work and attention.
> (I might do a migration guide later)
>
> I am planning on merging the version3 branch with the head in the coming days.
> Any objections anyone?
>
> Now about the modules:
> The following modules have been update to version 3:
>
> Apache Empire-db Core ..............................
> Apache Empire-db Java Server Faces 2.x extensions ..
> Apache Empire-db Code Generator ....................
> Apache Empire-db Maven Plugin ......................
> Apache Empire-db Maven Codegen Example .............
> Apache Empire-db Basic Example .....................
> Apache Empire-db Advanced Example ..................
> Apache Empire-db JSF2 Example ......................
> Apache Empire-db Vue.js Example ....................
>
> However, I have NOT converted any of the following modules:
>
> Apache Empire-db CXF Example .......................
> Apache Empire-db Spring JDBC Template ..............
> Apache Empire-db Spring Example ....................
> Apache Empire-db Struts2 Extension .................
> Apache Empire-db Struts2 Example ...................
> Apache Empire-db Struts2/CXF Example ...............
>
> Originally the Stuts2 Extensions had been provided by me, but I am not planning on continuing Struts2 support myself.
> As I have no experience with Spring, I am unable to do the migration myself. Same with CXF.
>
> So what should we do with this leftover modules?
> Anyone willing to convert them to version 3?
>
Re: Empire-db version 3.0.0 state of development / Migration of modules
Posted by Jan Glaubitz <ja...@glaubitz.org>.
Hello Rainer,
sounds and looks interesting!
I’d like to try it out with my existing projects. Can you provide a small migration guide / getting started guide?
I’m using PostgreSQL and have some postgres-specific functions implemented. I hope I can get them work again ;)
- jan
> Am 14.02.2022 um 18:23 schrieb Rainer Döbele <do...@esteam.de>:
>
> Hi all,
>
> as announced I have started working on Empire-db version 3.0.0 in order modernize it for the 2020s.
> I am happy to announce that I have reviewed and optimized almost every part and it looks awesome in my opinion.
> At the start I would have not imagined that there was so much potential.
>
> Empire-db 3.0 rocks!
>
> To get more information look at the Jira tickets EMPIREDB-362 to EMPIREDB-372.
> Or even better, get the "version3" branch from git (https://gitbox.apache.org/repos/asf/empire-db.git ) and run the examples.
>
> A lot of classes and function have been renamed, removed or altered.
> Migrating code from projects using the version 2.x branch is possible but requires some work and attention.
> (I might do a migration guide later)
>
> I am planning on merging the version3 branch with the head in the coming days.
> Any objections anyone?
>
> Now about the modules:
> The following modules have been update to version 3:
>
> Apache Empire-db Core ..............................
> Apache Empire-db Java Server Faces 2.x extensions ..
> Apache Empire-db Code Generator ....................
> Apache Empire-db Maven Plugin ......................
> Apache Empire-db Maven Codegen Example .............
> Apache Empire-db Basic Example .....................
> Apache Empire-db Advanced Example ..................
> Apache Empire-db JSF2 Example ......................
> Apache Empire-db Vue.js Example ....................
>
> However, I have NOT converted any of the following modules:
>
> Apache Empire-db CXF Example .......................
> Apache Empire-db Spring JDBC Template ..............
> Apache Empire-db Spring Example ....................
> Apache Empire-db Struts2 Extension .................
> Apache Empire-db Struts2 Example ...................
> Apache Empire-db Struts2/CXF Example ...............
>
> Originally the Stuts2 Extensions had been provided by me, but I am not planning on continuing Struts2 support myself.
> As I have no experience with Spring, I am unable to do the migration myself. Same with CXF.
>
> So what should we do with this leftover modules?
> Anyone willing to convert them to version 3?
>