release:perform just uses the scm:checkout command. There's no
scm:export command.
-Original Message-
From: Mark Hewett [mailto:[EMAIL PROTECTED]
Sent: Monday, July 17, 2006 2:10 PM
To: Maven Users
Subject: [m2] release:perform checkout vs. export (with Subversion)
When doing a release:perform the tagged version is checked out into
target/checkout. This causes some issues with Subclipse - you end up
with a Subversion working copy nested within a Subversion working
copy, and even though the target directory is marked as ignored this
causes new resources created under target/checkout during the build
(in my case, cobertura.ser) to show up during a "Team/Synchronize with
Repository" operation in Eclipse, and also causes the operation to
take much longer.
I'm told (on the Subclipse list) that if Maven 2 did an export instead
of a checkout that this would not be an issue, performance would be
improved (since the exported resources are not versioned at all the
status would not be checked) and disk space would be saved (since you
don't have a full working copy with export - just the actual
resources).
This applies to Subversion. I'm not sure if it also applies to CVS,
although with export at least you would save creating the .CVS
directories.
So, any reason that release:perform can't use export instead of
checkout? Should this be asked on the dev list instead (I'm not
subscribed, and I don't see a way to search the archives to see if
this has come up already).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
