-
Improvement
-
Resolution: Fixed
-
Critical
-
None
-
Platform: All, OS: All
When we perform a non-recursive subversion checkout/update of our source code
(see issue 1311), hudson tries to resolve the sub-modules that do not exist
since their "pom.xml" file have not been checked out. To resolve this problem it
would be nice if Hudson support the maven option "N", "-non-recursive" in
order to not recurs into sub-projects.
Created an attachment (id=916)
This SVN patch file (hudson-1.323-non-recursive-modules-resolution.patch) has been made based on the Hudson version "1.323". It allows for each job to configure if the maven modules resolution has to be done recursively or not. If the user specify, in the "Goals and options" field of the "Build" section of the job configuration web page, the option "
N" or "-non-recursive" then maven will not recurs into the sub-projects, i.e. will not resolve the modules recursively.