|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-15132) Cannot use a single file name as module for retrieval in CVS Plugin version 2.5
michael.m.cla...@gmail.com (JIRA) Sun, 14 Oct 2012 07:33:46 -0700
- [JIRA] (JENKINS-15132) Cannot use a sing... deepakmah...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... deepakmah...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... deepakmah...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... deepakmah...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... valenti...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... deepakmah...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15132) Cannot use a... michael.m.cla...@gmail.com (JIRA)
This issue will still exist for the following situations due to the workings of CVS (i.e. there's not an easy way to fix them in CVS plugin):
1. Checking out a single file into a workspace in non legacy mode - updates will checkout all sibling files and sub-modules (initial checkout will be ok)
2. Checking out a single file into a workspace with the local name set the same as the remote name - checks-out out the file into a folder named the same as the file name (e.g. remote name of /path/to/file.txt would cause file to be checked out into /path/to/file.txt/file.txt). Work around this by setting the local name to only include the module directory names (e.g checking out /path/to/file.txt should set local name as /path/to)
3. Checking out a single file with a remote name set - updates will checkout all sibling files and sub-modules.