From continuum-users-return-3781-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org Tue May 15 13:32:23 2007
Return-Path: <continuum-users-return-3781-apmail-maven-continuum-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-continuum-users-archive@www.apache.org
Received: (qmail 16920 invoked from network); 15 May 2007 13:32:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 May 2007 13:32:22 -0000
Received: (qmail 72457 invoked by uid 500); 15 May 2007 13:32:21 -0000
Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org
Received: (qmail 72423 invoked by uid 500); 15 May 2007 13:32:21 -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 72367 invoked by uid 99); 15 May 2007 13:32:21 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2007 06:32:21 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [213.80.11.206] (HELO posten.jadestone.se) (213.80.11.206)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2007 06:32:12 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
	by posten.jadestone.se (Postfix) with ESMTP id 31A7649FEB
	for <continuum-users@maven.apache.org>; Tue, 15 May 2007 15:31:51 +0200 (CEST)
Received: from posten.jadestone.se ([127.0.0.1])
	by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 23907-42 for <continuum-users@maven.apache.org>;
	Tue, 15 May 2007 15:31:40 +0200 (CEST)
Received: from STENDUM (stendum.jadestone.local [192.168.2.11])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by posten.jadestone.se (Postfix) with ESMTP id ABBC349FD2
	for <continuum-users@maven.apache.org>; Tue, 15 May 2007 15:31:40 +0200 (CEST)
From: =?iso-8859-1?Q?Petter_M=E5hl=E9n?= <petter.mahlen@jadestone.se>
To: <continuum-users@maven.apache.org>
Subject: How to handle inter-project dependencies
Date: Tue, 15 May 2007 15:31:38 +0200
Message-ID: <01c301c796f5$5df304f0$0b02a8c0@jadestone.local>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceW9V3Ix1lfARPnTa6o/yK0p8N1BA==
X-Virus-Scanned: by amavisd-new at jadestone.se
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

We have a setup that works well during development but doesn't agree with
Continuum's philosophy of how to handle things - or so it seems to me. I
think there is a point in doing it another way than we are, but I am not
sure how. Hopefully, somebody here can enlighten me. :)

We have three projects:

1. 'common', which basically contains an XML schema definition file for code
generation with XJC (other things as well, but that's probably not relevant
for the issue at hand).

2. 'client', which is built using Ant (for historical reasons, would have
preferred Maven but no time to fix that yet). One step of the build looks
like so:

	<target name="generate-xsd-source">
		<mkdir dir="${xjc.gen.dir}" />
		<exec executable="${xjc.exe}">
			<arg value="-p" />
			<arg value="se.jadestone.hc.client.database"/>
			<arg value="-d" />
			<arg value="${xjc.gen.dir}"/>
			<arg
value="${common.dir}/src/main/schemas/database.xsd"/>
		</exec>
	</target>

In our local environments, '${common.dir}' points to a directory where the
source code of the 'common' project resides (../common by default).

3. 'server', which is built using Maven, and which contains the following
dependency:

  ...
  <build>
     ...
     <plugins>
	   	<plugin>
			<groupId>com.sun.tools.xjc.maven2</groupId>
			<artifactId>maven-jaxb-plugin</artifactId>
			<executions>
				<execution>
					<goals>
						<goal>generate</goal>
					</goals>
				</execution>
			</executions>
			<configuration>
	
<generatePackage>se.jadestone.hc.client.database</generatePackage>
	
<schemaDirectory>../common/src/main/schemas</schemaDirectory>
				<strict>true</strict>
				<verbose>true</verbose>       
			</configuration>
		</plugin>
     </plugin>
  </build>

Since we cannot know (I think) which directory name Continuum will choose
when checking out and building the 'common' project, both of these builds
fail. As far as I have been able to figure out, both the XJC tool and the
maven-jaxb-plugin require that we specify an explicit path to the file to
generate code from, so it doesn't seem to be an option to use the jar file
that we actually build from other things in the 'common' project. I would
like to get away from using explicit paths the way we are, but I am not sure
how.

Does anybody have a solution to this problem? We're using 1.0.3, by the way.

Thanks in advance,

Petter