Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <dev@cocoon.apache.org>
Subject: RE: cvs commit: cocoon-2.1/src/blocks/html/lib .cvsignore
 jtidy-04aug2000r7-dev.jar
Date: Tue, 26 Aug 2003 14:10:52 +0200
Message-ID: <LKENJPKDAIKAPKHEOCMMAEHKENAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <3F4B4C13.3040604@verizon.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Vadim Gritsenko wrote:
> 
> >>I noticed that jtidy has been moved out of html block and into 
> >>lib/optional. What will happen if I to remove jtidy from the 
> >>lib/optional? Will this break the build?
> >>    
> >>
> >Yepp, you can see it in the gump.xml dependency description.
> >
> 
> But that means that we are busting build even more instead of fixing it?
> 
Vadim, this is a point a stressed several times in the last months, but
noone was really interested. Yes, we have a problem with libs, e.g. we
have the same lib (velocity) at different places!

We are not "busting the build". Currently, if two blocks require the same
lib, it has to be in lib/optional. When the blocks directory structure 
was built, someone moved the libs into the blocks directories making it
impossible to use the same jar in several projects. Now, each time
a second block needs the jar we have to move it :(
As I pointed out several times, this can be solved with an updated build
system where we have all jars in lib/optional. These jars are not copied
automatically to WEB-INF/lib. They are only copied if a included block
depends on them.

Carsten