Hello there,
I'm trying to split a monobloc demo application I'm writing into smaller, more usable building blocs.
The current application - assume its name is Prototype - consists of :
- a Service layer
- definitions of DAO interfaces
- 3 different implementations of the DAO interfaces impl.jdbc, impl.ibatis, impl.speedo
- a set of unit tests (in src/test) for the service layer
- a set of unit tests (in src/test, really speaking dbUnit tests) for the DAO layer
- for the moment, a conf file in src/conf allows the DAO tests to be passed on one of the 3 concrete implementations : jdbc, ibatis or speedo.
What I want to do is have separate maven projects for service, DAO specs (interfaces), DAO impls :
prototype prototype-dao prototype-dao-jdbc prototype-dao-ibatis prototype-dao-speedo
At the same time, I don't want to duplicate the unit tests for the DAO layer.
I would have been happy if I could have kept the DAO unit tests with the DAO specs (interfaces) maven project.
But as I don't want the tests to be jarred with the DAO, and as I think if I put the tests in the src/test directory, I can't make other project benefit from it,
the only way I have to mutualize the tests is to create a dao-tests maven project :
prototype-dao-tests
What I don't like here is that I have to expose the tests at a high level, just to solve some factorisation problem....
Is this the "best practice" to do it, or do I miss the point somewhere ?
Do you know a better way to solve this *common* (I guess) problem with project management ?
Thanks in advance for your suggestions,
Regards,
-- Laurent Petit
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
