Hans Dockter wrote:
Hi Adam,
On Jul 30, 2008, at 5:17 AM, Adam Murdoch wrote:
the other is the relationship between a configuration and a task
which *produces* it.
I don't see a use case relationship. Any examples?
One example is a project which uses the artifacts of another project in
a multi-project build. Currently we use
DependencyManager.artifactProductionTaskName to model this, which
ProjectDependency uses to add a task dependency from the consuming
project to the producing task of the project. This is fine when all
public configurations of a project are produced by a single task and are
cheap to build. A problem I ran into porting a multi-project ant build
to gradle is that some configurations were very expensive to build and
were not needed by most of the other projects. However, in order to use
any of them in another project, I was forced to build all of them
whether required or not.
I also think some consistency between modelling the consumers of a
configuration and the producers of a configuration would help
understandability.
I'd love to do continuous peer reviews particularly on domain driven
design aspects. Unfortunately Codehaus does not offer Atlassians
Crucible.
I've not really seen anything other than the 'check it in and let the
other develpers comment on it' approach for open source projects. I
guess it works reasonably well. It's predicated on sufficient developer
bandwidth to review stuff, and probably some upfront discussion on the
mailing list (the why, the what, and the roughly how).
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
