3.0 rename as such is done, but it also has a lot of expectations on "deep" fixes. There is a Jira that tries to capture those; https://issues.apache.org/jira/browse/ZEST-109
Some of those are relatively trivial, such as ZEST-123 (change Base64Encoder) and ZEST-124 (replace Jodatime with Java 8 Time API), but others are quite massive, such as ZEST-97 which is about total revamp of how UnitOfWork is handled. As usual, with other jobs that put food on table, this will take some time... // Niclas On Oct 9, 2015 03:55, "Paul Merlin" <[email protected]> wrote: > nino martinez wael a écrit : > > I Know it was in purpose. But I do think it would do good to spend 10 > > minutes in a, "large" zest app, that would really show some of the raw > > power of composite programming.. Just really to put emphasis on > > using/reusing fragments.. Because doing a simple project doesn't show, it > > only show the overhead. Now some people of course can abstract from that, > > others might not. > > Sure, makes sense. And yes, we did not dig deep into composition/reuse. > > > The speaker console app could be okay. If it had more classes to show of > > the many facets of reuse.. > > The tutorials do a pretty good job on this. > Maybe we should have pointed to Zest documentation along the presentation? > > > Btw on a personal plan I intent to look into zest again.. Any idea on > when > > naming on packages will be moved to apache naming, e.g. Zest vs qi4j? > > 2.x will keep using org.qi4j.* > 3.0 will use org.apache.zest.*. > The rename has already been done in the develop branch. > > We don't have a 3.0 release time frame, we only know it should happen in > 2016. > > Cheers > > /Paul > >
