Hmm. I'm liking how this is all shaping up, but I'm wondering about
the "in the top level pom" bit. Already some things we do assuming a
reactor build are confusing because each project is built separately,
and when you start getting into continuum which essentially replaces
the reactor with its own per-sub-project build infrastructure to allow
only parts of the build that are relevant/changed to be executed, and
any assumptions of parent location are off. I think causing this to
go project at a time, and have workspace_repo per subproject would
probably be more supportive of the overall rather independent nature
of maven sub projects.
Christian.
On 18-Sep-07, at 8:22 AM, Kenney Westerhof wrote:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
