[
https://jira.codehaus.org/browse/MNG-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306068#comment-306068
]
Ivan commented on MNG-5085:
---------------------------
Well in my case this is more in order to provide "sparse" workspaces to
developers.
I mean, we have some core modules and many plugin modules.
Some developers are not interested in having the core modules (and in some
cases we don't want them to have it, for security reasons).
But they still need to build the whole application regardless they don't have
the sources for the core project or for non related plugins.
During the build, missing modules needed (dependency) will be downloaded from
the repository.
And missing modules that are not present and not needed won't be packaged.
(An even better solution might be to tell maven that modules which can't be
built should be searched in the local/remote repository)
In other words, to have the same behavior for dependency resolutions than for
modules resolutions.
> 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
