Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Using SVN for a rather big project, we tend to use SVN sparse checkouts, i.e. we do not checkout the whole project. Example:
Full Project (as in Repository):
Parent
pom.xml (contains A and B as modules)
--> A
pom.xml
--> B
pom.xml
Now, do a checkout (svn co xxx --depth children; svn update --set-depth inifity A)
Working Copy:
Parent
pom.xml (contains A and B as modules)
--> A
pom.xml
--> B (no pom!!, since we only did a sparse checkout)
Now, this setup is not buildable, since maven complains (rightfully) about a missing pom for B.
What I propose is an option to change this behaviour with a command-line option (-imm, --ignore-missing-modules) that would simply ignore missing modules during pom resolution.
Attachments
Issue Links
- relates to
-
MNG-5230 Command line option to exclude modules from reactor
- Closed