Part of the problem, of course, is that this is delegated to the maven
SCM stuff, so this may force a lot of feature-requests back into that
project. Not a bad thing, but it's very very easy to over-specify if
this isn't thought through carefully.
christian
On 23-Jan-08, at 12:34 , Patrick Shea wrote:
Yes that would be good. In a sense what we what is a way to control
the scm command string per project or add a checkbox on the build
definition for non recursive.
Patrick
-----Original Message-----
From: Christian Edward Gruber <[EMAIL PROTECTED]>
Sent: Wednesday, January 23, 2008 9:19am
To: continuum-users@maven.apache.org
Subject: Re: Recursive maven projects
Actually, you don't want this, because a parent project may have /src/
site/*, so you actually want slightly more granularity on this than
just "recursive pull or not"
Christian.
On 23-Jan-08, at 12:05 , Patrick Shea wrote:
Ok I will. This may not be an issue on small projects but it becomes
one when you have a large code base.
Patrick
-----Original Message-----
From: Wendy Smoak <[EMAIL PROTECTED]>
Sent: Wednesday, January 23, 2008 8:54am
To: continuum-users@maven.apache.org
Subject: Re: Recursive maven projects
On Jan 23, 2008 9:39 AM, Patrick Shea <[EMAIL PROTECTED]> wrote:
Yes that's for maven, but continuum will still call "svn up" on the
entire branch.
What I'm trying to avoid is to have multiple "checked out" projects
with the same code.
I need to pass "-N" to subversion on projects of type pom.
As Emmanuel mentioned there's no way to do this currently. Can you
open a JIRA for this enhancement if it's not already there?
--
Wendy
