I would recommend decoupling the utility classes used by both subproject1 and subproject2 into a separate subproject (subprojectutil?). Then, you'd have the dependency chain of subproject1 DEPENDS ON subprojectutil + subproject2, subproject2 DEPENDS ON subprojectutil.


Matt


John Casey wrote:

IMO, that's not really going to help anything. It seems that the subprojects here constitute a cyclic dependency issue. In this case,
it's not possible to compile one subproject without compiling the other
at the same time. Why are these separated in the first place? If there
isn't a good reason, then I'd put them in the same project and compile
them together...


my 2 cents.

-john

On Thu, 2004-01-15 at 15:51, Sonnek, Ryan wrote:


I would recommend breaking your ejb interfaces into a separate project
(something like an ejb-client project).  I've got an example up on the maven
wiki if you want an example.  Feel free to comment if this setup works for
you or if you see any possible improvements.
http://wiki.codehaus.org/maven/CreatingEjbApplications

Ryan



-----Original Message-----
From: Jyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 2:15 PM
To: [EMAIL PROTECTED]
Subject: Build of severals subprojects


Example : I have two 2 subprojects mavenproject/subproject1 mavenproject/subproject2

subproject1 is a framework
subproject2 is an EJB

subproject2 uses classes from subproject1 (the EJB uses utility classes)
subproject1 uses classes from subproject2 (using interfaces when call EJB)

The build of subproject1 failed => ok because classes of subproject2 are
needed.
The build of subproject2 failed => ok because classes of subproject1 are
needed.

What's the maven logic to resolve this problem ? what's the best way ?
Must I compile all classes in a third project and put it in repository to
make subproject1 & subproject2 with a dependancy ?


Thanks



--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to