Avoid test-jar usage
Currently build of driver-mapping module is dependant on two things - driver-core and driver-core test jar which provides some helper classes.
These helper classes should be extrated to separate test module which could be used in tests of both: driver-core and driver-mapping.
This ticket has been closed due to more than 2 years of inactivity, as part of an automatic housekeeping procedure.
If you think that this was inappropriate, feel free to re-open the ticket. If possible, please provide any context that could explain why the issue described in this ticket is still relevant.
Thanks for your understanding.
I know it is possible to live with it, however now for example I am unable to modify mapper module cause I can not manage to driver-core tests to pass. Necessarily to make extra steps to contribute just makes contributing to project harder.
Exactly, there are some circular dependencies between test classes and core classes.
What purpose would a separate test module achieve? I know the test-jar is slightly annoying sometimes (e.g. need to run a mvn install when bumping the version), but I think we can live with it.
At this moment CCMBridge has too many things in it to pull it out. Another way is to extract driver API with interfaces and let test utility be dependant only on that, but this may force some design changes.
I like this idea. Another benefit of this is that we could publish this module and make CCMBridge available within this module for external use. Although this is not a current desire for CCMBridge, I can see others wanting to use it.