But doesn't continuum use the plexus and maven SCM stuff under the
hood? I haven't browsed the source or really watched the commits for
several months, but I thought it used some of the same infrastructure
for SCM handling. I could be wrong. Regardless, that really is more
of a comment for the continuum-dev list, not here.
As to your points below, I'm not sure that "pom projects scm calls are
non-recursive by default" is really valid. Almost every one of my pom
projects has a /src/site folder with content that I want to build in
the nightly. But also, a lot of Maven projects are mid-migration
from older build approaches, so being able to be more specific about
what's pulled in and what's not is critical until a proper "maven-
approved" structure is achieved.
Christian.
On 23-Jan-08, at 12:51 , Patrick Shea 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.
So just adding an option (checkbox) on the build definition to
prevent recursive checkout would be nice.
A good bet would be that maven projects of type "pom" should be non
recursive in regards to source code. You could override this later
with the above option.
The other way around (sync all then restrict) would leave your build
workspace polluted with unnecessary files.
Patrick
-----Original Message-----
From: Christian Edward Gruber <[EMAIL PROTECTED]>
Sent: Wednesday, January 23, 2008 9:37am
To: continuum-users@maven.apache.org
Subject: Re: Recursive maven projects
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
