Hi Perfectly fine using openjpa. (I would even prefer it as well :-) ) Now just think about do we use same database model as today (can be a pain to deal with the legacy jpox generated database) or do we use a new database model (and have a data migration step).
On 20 September 2016 at 15:19, Martin Stockhammer <m.stockham...@web.de> wrote: > Hi, > > I will look at them. I'm only familiar with hibernate currently. If the > work needed is the same, I think I would prefer openjpa. > > Greetings > > Martin > > Am 20. September 2016 07:09:41 MESZ, schrieb Olivier Lamy < > ol...@apache.org>: > >Hi > >Sure joop is nice for our case. > >We already have the database model, we just need to generate the beans. > >I think we can do it as well with openjpa. > >Martin what would you prefer? > > > > > >On 19 September 2016 at 10:27, Hadrian Zbarcea <hzbar...@gmail.com> > >wrote: > > > >> Hi Martin, Olivier, > >> > >> I had good experience with jooq [1][2] which is not jpa and is imho > >easier > >> to use. It's also ALv2, maybe something to consider? > >> > >> Hadrian > >> > >> [1] http://www.jooq.org/ > >> [2] https://github.com/jOOQ/jOOQ > >> > >> > >> > >> On 09/18/2016 08:13 PM, Olivier Lamy wrote: > >> > >>> Hi Martin, > >>> Where to start is always a good question :-) > >>> Regarding JPA it concerns only redback-core part as we do not use > >anymore > >>> database in archiva core. > >>> IMHO this one can be fun to implement (remember we cannot use > >library such > >>> hibernate because GPL but jpa has many other implementation even @ > >apache > >>> :-) ) > >>> Otherwise have a look at issues scheduled for 2.2.2 > >>> https://issues.apache.org/jira/browse/MRM/fixforversion/12335832/ > >>> > >>> HTH > >>> Olivier > >>> > >>> On 17 September 2016 at 22:56, Martin Stockhammer > ><m.stockham...@web.de> > >>> wrote: > >>> > >>> Hi, > >>>> > >>>> I looked at the JIRA tickets and think many of the are obsolete > >because > >>>> they > >>>> are very old or for different versions. > >>>> I'm willing to help but currently do not know where to start. I'm > >>>> currently > >>>> trying to understand the codebase, but I'm a bit lost. I do not > >really > >>>> know > >>>> which parts are more historic , which important. If some of you > >know some > >>>> specific issues that should be fixed and may be fixed without > >changing > >>>> the > >>>> complete codebase, please tell me or better give me the JIRA link. > >>>> Or if there are some major tasks that are needed to bring the > >project > >>>> forward, > >>>> tell me. > >>>> Olivier mentioned switching the persistence library to JPA is one > >thing > >>>> that > >>>> may be tried, because of some JDK incompatibilities with the > >current > >>>> implementation. I will look at this, but it would be helpful, if > >someone > >>>> can > >>>> give some hints what components may be involved in such a change. > >>>> > >>>> I would like to keep the product stable working and I'm more > >interested > >>>> in > >>>> fixing bugs and improving the usability. I think major changes that > >break > >>>> the > >>>> build and does not produce a running product for a long time will > >be > >>>> fatal > >>>> for > >>>> the project. > >>>> > >>>> Another question: The project page shows a lot of committers, are > >there > >>>> any of > >>>> them still active or is this list more like a gallery of ancestral > >>>> committers? > >>>> And who keeps the automatic build running? > >>>> > >>>> > >>>> Greetings > >>>> > >>>> Martin > >>>> > >>>> > >>>> > >>> > >>> > > > > > >-- > >Olivier Lamy > >http://twitter.com/olamy | http://linkedin.com/in/olamy > > -- > Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail > gesendet. -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
