[
http://jira.codehaus.org/browse/MNG-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139536#action_139536
]
Francois Fernandes commented on MNG-2116:
-----------------------------------------
beside this I suggest that a strict mode would fail any build if dependency
version conflicts occur. The "transparent" version selection is nice but for
some situations it should be clear which version will be used.
> Add strict mode, to avoid any stubbing, dummying, etc. activities to account
> for missing data.
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-2116
> URL: http://jira.codehaus.org/browse/MNG-2116
> Project: Maven 2
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.2
> Reporter: John Casey
> Priority: Minor
> Fix For: 2.1
>
>
> Currently, Maven will create a stub POM when it cannot find one on the remote
> repository. However, there are cases where we need to have the ability to
> verify that all the components of an application or some other type of build
> are present. Therefore, we need a strict mode for Maven, which will suppress
> any stubbing activities like this.
--
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
