[ http://jira.codehaus.org/browse/SCM-110?page=comments#action_53301 ]
mike perham commented on SCM-110: --------------------------------- Well, the release process is relatively rare. How often do you release a new version of a project? Once a week when under heavy development, maybe. Once a month or quarter once it is mature? And I would argue it is critical that the released files are exact. You don't want a missing file to cause a release to be malformed. The bigger issue is the more frequent and heavier uses of the checkout/update command like Continuum since builds usually involve the entire codebase several times a day. Obviously force sync will not work well in that case and we need to support both modes. I'm wondering if a -Dforce.sync=true might be a workable alternative. This is what another Perforce/Continuum user had to say. I don't know how his system got into this state but it sounds like a force sync issue. ############################################################ Here's the latest. When I run the build I can see in the log that p4 sync command is executed, as follows INFO | jvm 1 | 2005/12/12 10:52:34 | 2005-12-12 10:52:34,547 [Thread-1] DEBUG ScmManager - Executing p4 -H corpmetrodev:1666 -u t_rstone -ct_rstone-vm-portalx.qualcomm.com-maven sync ... And then it fails with INFO | jvm 1 | 2005/12/12 10:52:36 | **************************************************************************** INFO | jvm 1 | 2005/12/12 10:52:36 | Build Error: INFO | jvm 1 | 2005/12/12 10:52:36 | **************************************************************************** INFO | jvm 1 | 2005/12/12 10:52:36 | Exception: INFO | jvm 1 | 2005/12/12 10:52:36 | Cannot checkout sources. INFO | jvm 1 | 2005/12/12 10:52:36 | null If I copy/paste "p4 -H corpmetrodev:1666 -u t_rstone -ct_rstone-vm-portalx.qualcomm.com-maven sync" command in the shell runned by the same user that runs Continuum, it has no problem to sync files and create project file structure. However under Continuum build it will only create a sigle, empty folder under build root. > Perforce should force sync > -------------------------- > > Key: SCM-110 > URL: http://jira.codehaus.org/browse/SCM-110 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Reporter: mike perham > Attachments: force.txt > > > It's not pretty but it's the only way to get sync to work when files could be > deleted from the filesystem (e.g. mvn clean). -- 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
