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

Ivan commented on MNG-5085:
---------------------------

Paul, 
Of course it is related to our process and I understand this is a feature 
request not a bug.

Regarding the "building the whole thing" I don't think using hudson/jenkins 
would solve my problem:
My idea was that a developer should be able to generate a version for 
testing/demo with its modified sources.
I can't see how hudson could be able to pickup sources in its workspace and the 
missing module sources in the SCM.
And, further more, that means a developer can't build the software if he has 
not access to hudson. (which is likely to happen often in our case)

Anyway, I will simply stick to the "use profile" solution for now.
Thanks for your feedback


                
> 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

        

Reply via email to