Re: OJB Dependency breakdown

Hi Mike, Carlos sent our pom descriptor for ojb. See more comments 
between lines....

Mike Perham escribió:
> Here's my first pass at determining how OJB 1.0.4 uses the various
> dependencies.  Basically I just moved each package out of lib and ran
> compile/test to see what failed and how.  Comments welcome.  The
> second line for each is my suggested scope/optional dependency setting
> in the OJB Maven 2 POM, e.g:
>
> <dependency>
>  <groupId>antlr</groupId>
>  <artifactId>antlr</artifactId>
>  <version>2.7.5</version>
>  <scope>compile</scope>
>  <optional>true</optional>
> </dependency>
>
> Hope this helps others.
>
> mike
>
> ===================================
>
> antlr-2.7.5.jar
>    Used to parse JDOQL
>    Compile/Optional
compile time only dependency. Not needed for runtime.
>
> commons-beanutils-1.7.0.jar
>    Uses DynaBean and PropertyUtils
>    Compile/Required, consider forking code to remove this dep?
I think it is required.
>
> commons-betwixt-0.8-dev.jar
>    Unknown usage
>    Remove? Runtime/Optional, no compilation or test failures without it
yes.
>
> commons-digester-1.7.jar
>    Used by ant DdlUtils support
>    Compile/Optional
>
> commons-pool-1.2.jar
>    Used with DBCP connection pooling
>    Compile/Optional, J2EE container should perform pooling at runtime
Optional, it depends on OJB configuration.
>
> commons-transaction-1.1.jar
>    Used by OJB's broker.locking package
>    Compile/Required
>
> jakarta-regexp-1.3.jar
>    Used by reversedb mapping tool
>    Compile/Optional
>
> jcs.jar
>    One of a number of caching impls
>    Compile/Optional
>
> prevayler.jar
>    Object database, unknown usage
>    Runtime/Optional?
It is optional. Needed if you choose prevayler as you DB.

>
> village-2.0.jar
>    Used with Torque to generate DDL, no compile/test failures without it
>    Runtime/Optional?
Optional, not needed at runtime. ut's used only by torque.

Best Regards,

Antonio Gallardo