Hi Andrei,
by separate project, you mean a "real" project (with its own release
cycle, artifacts, svn repo, etc), or just a Maven module ?
I don't think it's a good idea to have it in a separate "real" project
as it's coupled to the others artifacts/modules/codebase.
But a itest Maven module it's a good think (it's what we have most of
projects, like Karaf, ServiceMix, etc).
Regards
JB
On 12/09/2012 07:37 PM, Andrei Shakirin wrote:
Hi,
I would suggest to extract integration and system tests into separate project.
From my perspective it makes management of tests and build process more
transparent and easy. Of course, JUnit tests will stay in corresponded
projects.
Does it make sense?
Cheers,
Andrei.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
