db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning P. Schmiedehausen" <...@intermeta.de>
Subject Re: svn commit: r278825 - in /db/torque/test: ./ trunk/ trunk/maven-test-plugin/
Date Tue, 06 Sep 2005 08:59:52 GMT
Thomas Fischer <fischer@seitenbau.net> writes:

>I tried several things and this was the best I could come up with till now.
>The problem with the old runtimetest were the following:
>- one had to build the generator and the templates separately if one
>changed something there. Really annoying if you run the test 10 times.
>- it was testing the ant version of the generator and not the maven-plugin.
>- it had problems with the junit task definition.
>- it was not a runtimetest, but instead it was testing the whole of torque,
>and therefore should not be in the runtime part of the project.

>The new test has none of these problems, and the new problem with the
>installed plugin can be solved. So in my own personal private opinion, it
>is much better than the old test. Full stop.

>However, it is also not the ideal solution from my point of view. What I
>would have liked best would be a test project which could be run like any
>other torque project. The problems were the following:
>- The main problem is that I did not find a possibility to read a profile
>file during (not before!!!) maven execution and passing the parameters to
>the torque maven plugin. Maybe I did not look hard enough, will look again
>this evening if one can do tricks with maven:set.
>- in the runtimetest, one can switch the idmethod from the profile. This
>was done using ant filters while copying the file. To retain this feature,
>one has to copy the schema files. If one does not want to retain this
>feature, one could use some tables with the idbroker and some normal ones.
>Then one could leave out the copying stuff and the project would look more
>like a normal Torque project. A strong point for retaining the idmethod
>switching feature is that some database adapters (firebird, at least) do
>not support the idmethod="native", so the part of the test using idmethod
>native would not run at all. Maybe one wants to have two runs in every
>test, one with idmethod=native and one with idmethod=idbroker, but no idea
>how to do this in an elegant way.

It's ok. If you see real benefits and it does not put a burden on a
maven installation, go ahead. As I said, I'm not really a fan of the
solution (-0) but I don't object it.

Getting some docs on how to use this would be good, though.


Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

		      4 - 8 - 15 - 16 - 23 - 42

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message