Carsten Ziegeler wrote:
> Hi,
>
> looking at our lib directory we have 32 jar files in it!
> This really shows the power of Cocoon to integrate/combine the different
> projects and solutions, but on the other hand it makes the distribution
> rather big and slightly confusing.
>
> Some jars are essential to the core of Cocoon, some are most often required
> and some are rarely used optional ones.
>
> Can we reflect this with a better (directory) structure?
+1
> I suggested some weeks ago that we create an opt directory parallel to the
> src/java directory to identify optional components, for example:
>
> src + java
> + opt + fop + conf + fop.sitemap (The configuration of the fop sitemap
> components)
> + lib + fop.jar
> + src + org ...
> + sample + ...
> + batik ...
> + deli ...
> + jtidy ....
>
> Then the lib directory would only contain the necessary jar files for the
> core of cocoon.
Well, we could set the lib directory like this:
/lib/core
(all the core jars)
/lib/ext
(all the extension jars)
>
> I will start right now and finish the remaining part of the new directory
> structure and create the tools directory. THis will move at least the
> two ant files out of the lib directory.
And Junit--are there any other tool only jars?
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
