You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/02/10 16:22:19 UTC
[jira] Created: (MNG-4025) Prominently document opt-out setting for
parallel artifact resolution for users
Prominently document opt-out setting for parallel artifact resolution for users
-------------------------------------------------------------------------------
Key: MNG-4025
URL: http://jira.codehaus.org/browse/MNG-4025
Project: Maven 2
Issue Type: Sub-task
Reporter: John Casey
Priority: Blocker
If there are any bugs in parallel resolution, they're likely to cause major problems for users. This is because artifact resolution is at the very foundation of Maven's functionality. Since we're putting together tests late in the game on this, and since its a new feature that will only have limited soak time before release, we need to provide an opt-out option for users, to limit its ability to compromise the quality of the release as a whole.
Once this setting is in place, we should document it prominently for users, to close the loop and make sure we have a contingency plan in place if the worst happens.
--
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
[jira] Updated: (MNG-4025) Prominently document opt-out setting for
parallel artifact resolution for users
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-4025:
------------------------------
Fix Version/s: 2.1.0
> Prominently document opt-out setting for parallel artifact resolution for users
> -------------------------------------------------------------------------------
>
> Key: MNG-4025
> URL: http://jira.codehaus.org/browse/MNG-4025
> Project: Maven 2
> Issue Type: Sub-task
> Reporter: John Casey
> Priority: Blocker
> Fix For: 2.1.0
>
>
> If there are any bugs in parallel resolution, they're likely to cause major problems for users. This is because artifact resolution is at the very foundation of Maven's functionality. Since we're putting together tests late in the game on this, and since its a new feature that will only have limited soak time before release, we need to provide an opt-out option for users, to limit its ability to compromise the quality of the release as a whole.
> Once this setting is in place, we should document it prominently for users, to close the loop and make sure we have a contingency plan in place if the worst happens.
--
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
[jira] Closed: (MNG-4025) Prominently document opt-out setting for
parallel artifact resolution for users
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-4025.
-----------------------------
Resolution: Fixed
> Prominently document opt-out setting for parallel artifact resolution for users
> -------------------------------------------------------------------------------
>
> Key: MNG-4025
> URL: http://jira.codehaus.org/browse/MNG-4025
> Project: Maven 2
> Issue Type: Sub-task
> Reporter: John Casey
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.1.0
>
>
> If there are any bugs in parallel resolution, they're likely to cause major problems for users. This is because artifact resolution is at the very foundation of Maven's functionality. Since we're putting together tests late in the game on this, and since its a new feature that will only have limited soak time before release, we need to provide an opt-out option for users, to limit its ability to compromise the quality of the release as a whole.
> Once this setting is in place, we should document it prominently for users, to close the loop and make sure we have a contingency plan in place if the worst happens.
--
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