https://issues.apache.org/bugzilla/show_bug.cgi?id=56397
--- Comment #16 from Pierre Viret <pierre.vi...@gmail.com> --- I've just figured out where you have performed the changes (tomcat/sandbox/trunk-maven-layout/) so I will be able to check this out on Friday. Regarding the tests: I have not tried to integrate the tests in the maven components yet. A good practice in maven is to split the integration tests in separate components which are built & tested late in the build cycle, when all base components are already built and can be referenced. Only the real unit tests, which run quickly (if they last more than a couple of seconds then we risk that the developers skip them...) should be integrated in the corresponding component and so the developer get at once a feedback if something is broken at this level. If some test classes are widely used then a solution is to create a "common-test" component containing all these utility classes which is then added as dependency (with scope <test>) in the other components. One other (quick & dirty) solution would be to create one single test component and put all the tests there, but I think this should only be used in a "first throw" and that we should integrate the real unit-tests in the corresponding components as soon as possible. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
