Return-Path: 
 <continuum-users-return-3878-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-continuum-users-archive@www.apache.org
Received: (qmail 11980 invoked from network); 6 Jun 2007 20:31:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Jun 2007 20:31:48 -0000
Received: (qmail 37759 invoked by uid 500); 6 Jun 2007 20:31:49 -0000
Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org
Received: (qmail 37744 invoked by uid 500); 6 Jun 2007 20:31:48 -0000
Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:continuum-users-help@maven.apache.org>
List-Unsubscribe: <mailto:continuum-users-unsubscribe@maven.apache.org>
List-Post: <mailto:continuum-users@maven.apache.org>
List-Id: <continuum-users.maven.apache.org>
Reply-To: continuum-users@maven.apache.org
Delivered-To: mailing list continuum-users@maven.apache.org
Received: (qmail 37729 invoked by uid 99); 6 Jun 2007 20:31:48 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2007 13:31:48 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jun 2007 13:31:42 -0700
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1Hw2A5-0003ep-OR
	for continuum-users@maven.apache.org; Wed, 06 Jun 2007 13:31:21 -0700
Message-ID: <10996664.post@talk.nabble.com>
Date: Wed, 6 Jun 2007 13:31:21 -0700 (PDT)
From: bkbonner <brian.bonner@paraware.com>
To: continuum-users@maven.apache.org
Subject: Re: Subversion Maven Continuum (trunk/tags/branches) and flat
 layout
In-Reply-To: <10996159.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: brian.bonner@paraware.com
References: <10996159.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


I've tried creating svn:externals  as a separate project (i.e.

eclipseworkspace/continuum-build

and I define on this svn:externals:

foo   http://www.test.com/foo/trunk
bar   http://www.test.com/bar/trunk


I can checkout this project using eclipse but continuum complains that it
can't find a pom.xml -- and it's correct, it's not visible from the
directory.  I guess I can add a pom.xml to see what happens.

Any ideas are appreciated.

Brian


bkbonner wrote:
> 
> I have a question about the best practice for dealing with a flat layout
> project in conjunction with a common directory structure for subversion
> namely:
> 
> foo/trunk/...
> foo/tags/...
> foo/branches/...
> 
> If I have multiple modules that are part of foo, I'll end up with:
> 
> foo/trunk/...
> foo/tags/...
> foo/branches/...
> 
> and the modules:
> 
> bar/trunk/...
> bar/tags/...
> bar/branches/...
> 
> I check each of the trunk modules into eclipse as:
> 
> eclipseworkspace/foo-config/  (see below)
> eclipseworkspace/foo/...
> eclipseworkspace/bar/...
> 
> 
> I also create a master eclipse project (foo-config) that I check into
> subversion to share things on the project including:
>   *  an eclipse team project set - to make checkout easier
>   *  subversion config information for this project
>   *  project format template
>   *  project code templates
>   *  maven settings files
>   *  etc.
> 
> The problem I have is with modules.  In each of the poms, I have modules
> and parents referring to the directories without including the trunk.
> 
> eclipseworkspace/foo/pom.xml
>              <module>../bar</module>
> eclipseworkspace/bar/...
>              <parent>../foo</parent>
> 
> But when I try to access the projects from continuum, the module
> definitions are wrong because trunk is in the way.  I show this below:
> 
> eclipseworkspace/foo/trunk/pom.xml
>              <module>../bar</module>
> (this will break because it can't find ../bar -- it only finds foo.)  
> <================
> eclipseworkspace/bar/...
>              <parent>../foo</parent>
> 
> I'd like to know how other people handle these build issues and what the
> best practices are for a flat layout (that eclipse needs).
> 
> Thanks.
> 
> 

-- 
View this message in context: http://www.nabble.com/Subversion-Maven-Continuum-%28trunk-tags-branches%29-and-flat-layout-tf3880094.html#a10996664
Sent from the Continuum - Users mailing list archive at Nabble.com.