On 23/08/2007, at 3:59 PM, Stephen Connolly wrote:
One of the advantages of what you were describing is the ability
to not install anything unless the entire build passes - that has
some virtues as well, but I consider it a separate feature to
fixing the local repository concurrency problems.
I am torn over which way to run on this question.
I think it's something that would be separately configurable. I don't
think it would be the default. The individual artifacts, once built,
should be useful whether the rest build or not - but it really
depends on your project.
The only issue is how to push from one layer to the next... don't
want to end up with another phase between install and deploy (local-
deploy???) that has the same locking problems!
I wasn't suggesting any pushing here: install goes into separate
local installation repository only, deploy pushes to the remote
repository from there, dependency resolution looks first in the
installation repository, then in the cache (if that's the way it's
defined), and then of course in the remote repository to bring into
the cache. There's no need to migrate things between them.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
