Java – Maven incremental build

We currently have a large Maven 2 project, which is a collection of many separate projects with complex dependencies, except for some common parent POMs Finally, we always treat the application as a single, so I'd rather convert it into one or more large projects

Does anyone have experience in optimizing continuous integration of large projects Is there any benefit to Maven or Hudson's incremental build capability? I only made a small change in one module. I'd rather not wait 2 hours

On the other hand, it is certain that you must always rebuild and retest at least all direct and indirect dependencies This is what we are currently doing with Hudson to automatically trigger all dependent work

Is it effective to split the same project into multiple builds? I usually don't like that all other generated things (such as reports, documents, etc.) files on the server may expire

Thank you for any ideas

Solution

I strongly recommend that you don't divide the construction work into different parts In my experience, this can quickly break away from upstream and downstream dependencies Incremental architecture is very suitable for your needs If these dependencies are set directly, only their dependencies can be changed

I will split the build jobs, but if they are completely independent applications with no or very few dependencies (if true, then they should not be in the same reactor, so incremental versions are impossible)