ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimitris Mouchritsas" <dmo...@gmail.com>
Subject Resolving cyclical dependencies
Date Fri, 21 Dec 2007 09:11:37 GMT
Hi everyone. I'm into a project that started recently. The "powers that be"
wanted the dev team to re-use another project which supposedly is similar to
ours. The problem is that this project is also based on a "base" project of
the company. I forgot to mention I'm talking about a J2EE 1.3 project, using
EJBs 2.0, XDoclet, Hibernate and Struts 1.2
I tried to fix the build file only to discover that the "base" project has
cyclical dependencies. Classes that are in the util package talk to DAOs,
DAO's referring to common classes, web classes talking to DAO's. In short I
can't compile one without the other. It's a nightmare. My manager is
reluctant about doing some heavy refactoring to correct all this. Since we
have a build file that works (even though it compiles classes and then
deletes them to resolve the dependencies) he says, no let's try it by
improving upon this; and we'll see.
What do you suggest? Is there a way to create a proper build file for this
project, having seperation of concerns (e.g. commom-compile, ejb-compile,
web-compile etc)

-- 
Dimitris Mouchritsas
Computer Services

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message