Hi, Just implemented and closed EMPIREDB-173 Switch to ASF Parent 13 POM for EMPIREDB-127 Switch to apache maven 3.0.x, there is no urgency so for my part we can keep it open. same for EMPIREDB-78 Create maven plugin integration test closed EMPIREDB-53 (See if we can have the maven website deployed) as there is no need for this website closed EMPIREDB-61 (Create a scala example project) as scala users will probably rather use Slick or Squeryl
I think we can keep the other issues open Cheers, F On 4 February 2013 15:23, Rainer Döbele <[email protected]> wrote: > Hi everyone, > > > > I have closed all issues that were resolved but not closed and that were more > than 1 year old. > > > > I have also resolved some open ones. > > > > Anyone any comments or ideas for the following remaining open issues? > > > > EMPIREDB-173 Switch to ASF Parent 12 POM > > > > EMPIREDB-170 DBDatabase.querySingleValue(cmd, conn) does not care about > DataType > > > > EMPIREDB-127 Switch to apache maven 3.0.x > > > > EMPIREDB-125 Investigate and solve problem with the location of velocity > templates on the code generator when integrated in own projects > > EMPIREDB-111 Use DBUnit with datasets for testing > > > > EMPIREDB-108 Correct and extend documentation for running the examples > > > > EMPIREDB-80 use of DdlUtils to synchronize database schema > > > > EMPIREDB-78 Create maven plugin integration test > > > > EMPIREDB-61 Create a scala example project > > > > EMPIREDB-53 See if we can have the maven website deployed > > > > IMO we should either assign those issues to someone or close them. > > > > Regards > > Rainer > > >
