> > Hum what worked was RunJettyRun from within Eclipse.
Gradle test or gradle runJetty did not work. But they do now after adding entity classes explicitley to persistence.xml 2011/11/12 Chris Mylonas <ch...@opencsta.org> > In glassfish? > > > On 12/11/2011, at 4:26 AM, Gunnar Eketrapp wrote: > > > I'll answer this me myself. > > > > The problem was solved by adding the entity classes to persistence.xml > > > > I don't know why it works wiht Maven without having them there. > > > > > > 2011/11/11 Gunnar Eketrapp <gunnar.eketr...@gmail.com> > > > >> Inspired by HLS condolences to us that are still using Maven I tried > >> Gradle out yesterday. > >> > >> And gosh that seem's like a big leap forward. Awesome product and I was > >> almost there in less then an hour! > >> > >> One small step in the other direction was that the scanning of my entity > >> beans totally disappeared. > >> > >> I have filed a question in the Gradle forum ... > >> > >> > >> > http://forums.gradle.org/gradle/topics/context_component_scan_stopped_working_after_move_to_gradle > >> > >> Has anyone in this forum encountered something alike !? > >> > >> Thanks in advance and excuse me for asking Gradle related quest in this > >> forum. > >> > >> /Gunnar > >> > > > > > > > > -- > > [Hem: 08-715 59 57, Mobil: 070-991 86 42] > > Allévägen 2A, 132 42 Saltsjö-Boo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- [Hem: 08-715 59 57, Mobil: 070-991 86 42] Allévägen 2A, 132 42 Saltsjö-Boo
