Hi Wendy, thanks for your answer. You're right. I should keep a organisational pom separately. On the other hand, I'll still need a reactor that puts the different subsystems togheter, since the subsystems are closely connected, but are released separately. As a consequence, I'll need 2 poms. One build pom in the hiearchy above the subsystems and a second, the organsisational pom, in separate location. The subsystems would inherit from the organisational pom.
I think that should work. Kuno -----Ursprüngliche Nachricht----- Von: Wendy Smoak [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 23. Oktober 2008 16:56 An: [email protected] Betreff: Re: Limiting svn checkout depth for deploying organisational pom On Thu, Oct 23, 2008 at 1:32 AM, Baeriswyl Kuno - Extern (IT-BA-MV) > What is the best way to deploy this organisational POM? Doing it > manually is a bit cumbersome and need to be deployed in the local > repository for continuum. However, if I configure a project, it would > also checkout all subsystems (say the whole directory hiearchy). Is > there a way to limit the checkout depth? Usually this type of pom is released separately, and so kept separately in Subversion. For example, the Maven and ASF organization-level pom "projects" which contain only the pom.xml file (and possibly a site skin): http://svn.apache.org/repos/asf/maven/pom/trunk/ I'm not aware that you can limit the checkout depth with Continuum, though it will default to a --non-recursive build so it will only build the parent. Unfortunately checking out with -N wouldn't always be correct as an organization-level pom can have some source code with it -- sometimes there is a shared site skin. -- Wendy
