Actually, this isn't a bad idea - looking at modules and including all
things that aren't in the module spec. At least in theory. Where it
breaks down is that modules can be of the form:
<modules>
<module>../sibling-child-project</module>
</modules>
Though you could just construct the relevant canonical path and
determine if the canonical path is still under the current project,
and if so - exclude it.
As to how, if your scm doesn't support an exclusion, then you'd have
to find all children, do an SCM -N on the parent, then iterate through
all non-excluded children and do an update on those. The problem
isn't (likely) one of unfeasibility, it's one of making it relatively
clean. If it's too messy, then it can be a bear for the user to
configure.
Christian.
On 23-Jan-08, at 13:37 , Patrick Shea wrote:
Well, it's pretty similar, it means don't run the command (maven:
compile,deploy, etc and subversion: co,up etc) recursively.
If there was a way to exclude from the scm command all sub projects
declared in the <modules> section that would do the trick. anything
else left would be considered legitimate.
Patrick
-----Original Message-----
From: Wendy Smoak <[EMAIL PROTECTED]>
Sent: Wednesday, January 23, 2008 10:27am
To: continuum-users@maven.apache.org, [EMAIL PROTECTED]
Subject: Re: Recursive maven projects
On Jan 23, 2008 10:51 AM, Patrick Shea <[EMAIL PROTECTED]> wrote:
I'm not sure I follow you, In my case I don't use the maven scm
plugin to synchronize the source code, continuum dos this for me
(which is the default behavior).
The maven build is fine, the non-recursive parameter is used by
default, it's just that the scm command is not doing the same.
Non-recursive means something different to Maven and Subversion. If
you check out with -N, you only get "the directory" not "the project"
(which as Christian already mentioned may include src/site.)
Still, I'm not opposed to adding a way to supply parameters for the
scm command, to give people the option.
--
Wendy
