Thank you very much. This patch is invaluable, really. It
solves the problem with the annoying dependencies and it's
fully backwards compatible. And it's so easy!
I'll apply this patch for the next release. Additionally,
I'll provide separate jar files for the different
technologies (EJB, JMS etc) with adapter versions that do
not extend BaseTestCase with one of the next versions. I've
already implemented the code generator for the different
adapters and I think this is a good thing, aside from the
fact that your idea makes the main mockrunner.jar (which
I'll still provide, of course) useable without adding
everything to classpath.
Kind regards,
Alwin Ibba
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm currently thinking about this issue. I'm not sure if it
still makes sense to provide separate jars. On the other
hand, the generator for the adapters is finished (this
generator is useful anyway, because I don't have to
synchronize the adapters with modules manually). With this
generator it's no problem to create adapters that do not
extend BaseTestCase, in fact it's no additional work. For
users only interested in JDBC, it's desirable to have a
"lightweight" jar just with JDBC stuff. But it's not really
necessary with your BaseTestCase-patch, in fact it's "nice
to have" now :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
patch for BaseTestCase.java
Logged In: YES
user_id=804648
Thank you very much. This patch is invaluable, really. It
solves the problem with the annoying dependencies and it's
fully backwards compatible. And it's so easy!
I'll apply this patch for the next release. Additionally,
I'll provide separate jar files for the different
technologies (EJB, JMS etc) with adapter versions that do
not extend BaseTestCase with one of the next versions. I've
already implemented the code generator for the different
adapters and I think this is a good thing, aside from the
fact that your idea makes the main mockrunner.jar (which
I'll still provide, of course) useable without adding
everything to classpath.
Kind regards,
Alwin Ibba
Logged In: YES
user_id=79346
You are welcome.
This patch may remove the need to have the separate jars
prepared for various technologies.
Logged In: YES
user_id=804648
I'm currently thinking about this issue. I'm not sure if it
still makes sense to provide separate jars. On the other
hand, the generator for the adapters is finished (this
generator is useful anyway, because I don't have to
synchronize the adapters with modules manually). With this
generator it's no problem to create adapters that do not
extend BaseTestCase, in fact it's no additional work. For
users only interested in JDBC, it's desirable to have a
"lightweight" jar just with JDBC stuff. But it's not really
necessary with your BaseTestCase-patch, in fact it's "nice
to have" now :-)