Hi,
2. Workspaces should be something you have to set consciously, not
automatically created. This allows an integration-testing run (for
example) to run in isolation by using a different workspace id, and
clean up after itself when finished.
Agreed.
I think they should always be created, and after the entire build finished,
merged to the main tree. Look at it as build transactions. When something
fails in mid-build, you can end up with a few artifacts referring to wrong
versions. For instance for a 2 artifact snapshot build, when the first artifact
is installed and the 2nd fails, where the 2nd has a dependency on the first.
If there were already snapshots present, then you have one that's newer
(with possible code changes that only work for the newer 2nd artifact).
Other projects depending on the 2nd artifact will get the old code and
the newer first artifact which will break builds.
When deploying comes into play, this will affect more than just local users.
For CI systems or multi-user builds having these workspaces will reduce
interference with other builds, as was said before.
Btw, we don't necessarily require the workspace repo to be present
in the ~/.m2/ directory. It could just aswell be target/workspace-repo/
in the top level pom.
-- Kenney
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
