I don't know. Maybe an issue in the Perforce provider. Emmanuel
On Tue, Apr 29, 2008 at 7:40 PM, Daniel King <[EMAIL PROTECTED]> wrote: > The scm:bootstrap seems to be checking everything out twice. Any ideas > why? > > Here are the steps: > > 1) Removing the checkoutDirectory > 2) Creating a temp client spec or workspace > 3) Checking out the code > 4) Deleting the checkout directory, > 5) Rechecking it out the code again > 6) Compiling > 7) Testing > 8) Deleting the client spec > > See below: > > [INFO] Removing C:\workspace2\unitedProject\build > [INFO] Checkout working directory: C:\workspace2\unitedProject\build > [INFO] Executing: p4 -d C:\workspace2\unitedProject\build -p > perforce:1555 -u devuser -P ********** client -i > [INFO] Executing: p4 -d C:\workspace2\unitedProject\build -p perforce: > 1555 -u devuser -P ********** client -d > devuser-F6NYG61-D-MavenSCM-C:\workspace2\unitedProject\build > [INFO] Removing C:\workspace2\unitedProject\build > [INFO] Checkout working directory: C:\workspace2\unitedProject\build > [INFO] Executing: p4 -d C:\workspace2\unitedProject\build -p perforce: > 1555 -u devuser -P ********** client -i > [INFO] Executing: p4 -d C:\workspace2\unitedProject\build -p perforce: > 1555 -u devuser -P ********** client -d > devuser-F443G61-D-MavenSCM-C:\workspace2\unitedProject\build > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > ---- > [INFO] Building Maven Default Project > [INFO] task-segment: [deploy] > > Daniel King > Vurv > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
