On 21.6.23 20:32, Volker Lamp wrote:
Is there any chance I can motivate you to contribute your test case as a unit test to the Tapestry code base? Have a look at the test apps in tapestry-jpa as a starting point.
If I find some free time in the following months to look it up and learn how to create an entire test case. For the time-being it will be faster for me to create a docker container spec to reproduce the bug.
As an alternative, I tried to modify the tapestry sources and the existing tests. I have never tried to build tapestry from source in the past, so bare with my ignorance. I cloned the sources from git, and decided for the command line route and just did ./gradlew build.
It seems successful. All the .jars are at the expected locations. I modified the gradle build file and hibernate.cfg.xml in the test folders inside tapestry-hibernate so that it should connect to another database and it uses another driver, just to see if this will stir things up, but nothing happened. The problem is that I don't see any connections to the database when I run the build, which seems strange to me. How do I force the tests to rerun and which is the specific test that i should run that uses the connection information in tapestry-hibernate/src/test/resources/hibernate.cfg.xml?
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
