You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2005/10/31 08:14:33 UTC
[jira] Created: (CONTINUUM-403) cvs update with empty r argument generate error
cvs update with empty r argument generate error
-----------------------------------------------
Key: CONTINUUM-403
URL: http://jira.codehaus.org/browse/CONTINUUM-403
Project: Continuum
Type: Bug
Components: continuum-core
Versions: 1.0
Reporter: Olivier Lamy
Priority: Blocker
The cvs update command with an emty -r argument.
This generate an error.
This append when editing a project and simply updating the version of the continuum project.
The only workaround is to delete and recording again the project.
2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -
f -q update -d -r
2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Working director
y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
2005-10-31 08:00:10,363 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Error while
updating the code for project: 'tcclient', id: '14' to '/local/maven/continuum/continuum-1.0/apps/co
ntinuum/working-directory/14' with branch/tag .
2005-10-31 08:00:10,364 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Command outp
ut: update: option requires an argument -- r
Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
[-I ign] [-W spec] [files...]
-A Reset any sticky tags/date/kopts.
-P Prune empty directories.
-C Overwrite locally modified files with clean repository copies.
-d Build directories, like checkout does.
-f Force a head revision match if tag/date not found.
-l Local directory only, no recursion.
-R Process directories recursively.
-p Send updates to standard output (avoids stickiness).
-k kopt Use RCS kopt -k option on checkout. (is sticky)
-r rev Update using specified revision/tag (is sticky).
-D date Set date to update from (is sticky).
-j rev Merge in changes made between current revision and rev.
-I ign More files to ignore (! to reset).
-W spec Wrappers specification line.
--
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: (CONTINUUM-403) cvs update with empty r argument generate error
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-403?page=all ]
Trygve Laugstol closed CONTINUUM-403:
-------------------------------------
Resolution: Duplicate
> cvs update with empty r argument generate error
> -----------------------------------------------
>
> Key: CONTINUUM-403
> URL: http://jira.codehaus.org/browse/CONTINUUM-403
> Project: Continuum
> Type: Bug
> Components: continuum-core
> Versions: 1.0
> Reporter: Olivier Lamy
> Assignee: Emmanuel Venisse
> Priority: Blocker
> Fix For: 1.1
>
>
> The cvs update command with an emty -r argument.
> This generate an error.
> This append when editing a project and simply updating the version of the continuum project.
> The only workaround is to delete and recording again the project.
> 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -
> f -q update -d -r
> 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Working director
> y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
> 2005-10-31 08:00:10,363 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Error while
> updating the code for project: 'tcclient', id: '14' to '/local/maven/continuum/continuum-1.0/apps/co
> ntinuum/working-directory/14' with branch/tag .
> 2005-10-31 08:00:10,364 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Command outp
> ut: update: option requires an argument -- r
> Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
> [-I ign] [-W spec] [files...]
> -A Reset any sticky tags/date/kopts.
> -P Prune empty directories.
> -C Overwrite locally modified files with clean repository copies.
> -d Build directories, like checkout does.
> -f Force a head revision match if tag/date not found.
> -l Local directory only, no recursion.
> -R Process directories recursively.
> -p Send updates to standard output (avoids stickiness).
> -k kopt Use RCS kopt -k option on checkout. (is sticky)
> -r rev Update using specified revision/tag (is sticky).
> -D date Set date to update from (is sticky).
> -j rev Merge in changes made between current revision and rev.
> -I ign More files to ignore (! to reset).
> -W spec Wrappers specification line.
--
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] Reopened: (CONTINUUM-403) cvs update with empty r argument generate error
Posted by "Trygve Laugstol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-403?page=all ]
Trygve Laugstol reopened CONTINUUM-403:
---------------------------------------
Opening to fix resolution.
> cvs update with empty r argument generate error
> -----------------------------------------------
>
> Key: CONTINUUM-403
> URL: http://jira.codehaus.org/browse/CONTINUUM-403
> Project: Continuum
> Type: Bug
> Components: continuum-core
> Versions: 1.0
> Reporter: Olivier Lamy
> Assignee: Emmanuel Venisse
> Priority: Blocker
> Fix For: 1.1
>
>
> The cvs update command with an emty -r argument.
> This generate an error.
> This append when editing a project and simply updating the version of the continuum project.
> The only workaround is to delete and recording again the project.
> 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -
> f -q update -d -r
> 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Working director
> y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
> 2005-10-31 08:00:10,363 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Error while
> updating the code for project: 'tcclient', id: '14' to '/local/maven/continuum/continuum-1.0/apps/co
> ntinuum/working-directory/14' with branch/tag .
> 2005-10-31 08:00:10,364 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Command outp
> ut: update: option requires an argument -- r
> Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
> [-I ign] [-W spec] [files...]
> -A Reset any sticky tags/date/kopts.
> -P Prune empty directories.
> -C Overwrite locally modified files with clean repository copies.
> -d Build directories, like checkout does.
> -f Force a head revision match if tag/date not found.
> -l Local directory only, no recursion.
> -R Process directories recursively.
> -p Send updates to standard output (avoids stickiness).
> -k kopt Use RCS kopt -k option on checkout. (is sticky)
> -r rev Update using specified revision/tag (is sticky).
> -D date Set date to update from (is sticky).
> -j rev Merge in changes made between current revision and rev.
> -I ign More files to ignore (! to reset).
> -W spec Wrappers specification line.
--
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: (CONTINUUM-403) cvs update with empty r argument generate error
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-403?page=all ]
Emmanuel Venisse closed CONTINUUM-403:
--------------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.1
Already fixed
> cvs update with empty r argument generate error
> -----------------------------------------------
>
> Key: CONTINUUM-403
> URL: http://jira.codehaus.org/browse/CONTINUUM-403
> Project: Continuum
> Type: Bug
> Components: continuum-core
> Versions: 1.0
> Reporter: Olivier Lamy
> Assignee: Emmanuel Venisse
> Priority: Blocker
> Fix For: 1.1
>
>
> The cvs update command with an emty -r argument.
> This generate an error.
> This append when editing a project and simply updating the version of the continuum project.
> The only workaround is to delete and recording again the project.
> 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs -
> f -q update -d -r
> 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Working director
> y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
> 2005-10-31 08:00:10,363 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Error while
> updating the code for project: 'tcclient', id: '14' to '/local/maven/continuum/continuum-1.0/apps/co
> ntinuum/working-directory/14' with branch/tag .
> 2005-10-31 08:00:10,364 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Command outp
> ut: update: option requires an argument -- r
> Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
> [-I ign] [-W spec] [files...]
> -A Reset any sticky tags/date/kopts.
> -P Prune empty directories.
> -C Overwrite locally modified files with clean repository copies.
> -d Build directories, like checkout does.
> -f Force a head revision match if tag/date not found.
> -l Local directory only, no recursion.
> -R Process directories recursively.
> -p Send updates to standard output (avoids stickiness).
> -k kopt Use RCS kopt -k option on checkout. (is sticky)
> -r rev Update using specified revision/tag (is sticky).
> -D date Set date to update from (is sticky).
> -j rev Merge in changes made between current revision and rev.
> -I ign More files to ignore (! to reset).
> -W spec Wrappers specification line.
--
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