[jira] Commented: (MNG-5085) Add a CLI option to ignore missing modules

["Stephan Pauxberger (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265609#action_265609 ] 

Stephan Pauxberger commented on MNG-5085:
-----------------------------------------

Our project consists of about 30 modules. To be able to individually combine "active" and "not active" modules, we would need a profile for each of the modules, which would be quite extreme.

Alternately, you could specify the projects to build using "-pl", however even the projects that you do not want to be built need to be present, making the use of sparse checkouts impossible.

My proposal is a way similar to parent projects (i.e. if the parent project is present, that one is used, else the parent is retrieved from repo).

This would allow the following workflow:

- I have a task to work upon, concerning modules A12, A13 and A23.
- I do a sparse checkout of the master project
- I widen the checkout to include A12, A13 and A23 (these steps take about 1/10th of the time it would take to do a complete checkout!)
- I work upon my task, whenever I need a build I just build the whole scaffold project using "mvn -imm install", which builds only parent an my three modules
- I realize my task also concerns A7, so I widen my working copy to include that as well
- nothing changes in respect to compilation etc.., what is there gets built, what is missing is retrieved from repo.

Major benefit of this workflow:

Since my working copy is way smaller EVERY subversion operation is faster by magnitudes.


> Add a CLI option to ignore missing modules
> ------------------------------------------
>
>                 Key: MNG-5085
>                 URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira