[
https://jira.codehaus.org/browse/MNG-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306921#comment-306921
]
Paul Benedict commented on MNG-5085:
------------------------------------
I stumbled upon an article today that tangentially regards this issue. It is
mostly FUD but it also echos some of the recent sentiments here regarding the
difficulty of modules/nesting. Just linking to it to help the discussion:
http://buzdin.blogspot.com/2012/08/maven-modules-considered-harmful.html
> Add a CLI option to ignore missing modules
> ------------------------------------------
>
> Key: MNG-5085
> URL: https://jira.codehaus.org/browse/MNG-5085
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Reactor and workspace
> Reporter: Stephan Pauxberger
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
