You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/30 16:11:23 UTC

[jira] Updated: (MNG-2116) Add strict mode, to avoid any stubbing, dummying, etc. activities to account for missing data.

     [ http://jira.codehaus.org/browse/MNG-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MNG-2116:
-----------------------------------

    Fix Version/s:     (was: 3.0-alpha-8)
                   3.x (to be reviewed)

> 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 & 3
>          Issue Type: New Feature
>          Components: General
>    Affects Versions: 2.0.2
>            Reporter: John Casey
>            Priority: Minor
>             Fix For: 3.x (to be reviewed)
>
>
> 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