You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Andreas Christoforides (JIRA)" <ji...@codehaus.org> on 2009/02/28 09:29:20 UTC
[jira] Created: (CONTINUUM-2103) Batch mode (--batch-mode) option
should be included by default
Batch mode (--batch-mode) option should be included by default
--------------------------------------------------------------
Key: CONTINUUM-2103
URL: http://jira.codehaus.org/browse/CONTINUUM-2103
Project: Continuum
Issue Type: Improvement
Components: Integration - Maven 2
Affects Versions: 1.3.1, 1.2.3
Reporter: Andreas Christoforides
Priority: Minor
Instead of having to include --batch-mode in every single Maven 2 build definition, include it by default. Builds in Continuum are never interactive anyway. If you omit it from your build definition, it causes the logs to increase in size when downloading dependencies.
--
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: (CONTINUUM-2103) Batch mode (--batch-mode) option
should be included by default
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-2103:
-----------------------------------
Fix Version/s: Future
> Batch mode (--batch-mode) option should be included by default
> --------------------------------------------------------------
>
> Key: CONTINUUM-2103
> URL: http://jira.codehaus.org/browse/CONTINUUM-2103
> Project: Continuum
> Issue Type: Improvement
> Components: Integration - Maven 2
> Affects Versions: 1.2.3, 1.3.1
> Reporter: Andreas Christoforides
> Priority: Minor
> Fix For: Future
>
>
> Instead of having to include --batch-mode in every single Maven 2 build definition, include it by default. Builds in Continuum are never interactive anyway. If you omit it from your build definition, it causes the logs to increase in size when downloading dependencies.
--
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: (CONTINUUM-2103) Batch mode (--batch-mode) option
should be included by default
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-2103:
-----------------------------------
Fix Version/s: Reviewed
I'm not sure about this one. I prefer to have it there in the build definition so the user has full control over the command that Continuum executes.
Maybe we could make it a checkbox instead of having to type it in the arguments field?
> Batch mode (--batch-mode) option should be included by default
> --------------------------------------------------------------
>
> Key: CONTINUUM-2103
> URL: http://jira.codehaus.org/browse/CONTINUUM-2103
> Project: Continuum
> Issue Type: Improvement
> Components: Integration - Maven 2
> Affects Versions: 1.2.3, 1.3.1
> Reporter: Andreas Christoforides
> Priority: Minor
> Fix For: Reviewed
>
>
> Instead of having to include --batch-mode in every single Maven 2 build definition, include it by default. Builds in Continuum are never interactive anyway. If you omit it from your build definition, it causes the logs to increase in size when downloading dependencies.
--
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