openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Prud'hommeaux <mprud...@apache.org>
Subject [DISCUSS] required vs. optional dependencies
Date Wed, 18 Apr 2007 18:31:13 GMT

Currently with OpenJPA, we ship with the following jars in the lib/  
directory:

   * commons-lang-2.1.jar
   * commons-collections-3.2.jar
   * geronimo-jta_1.0.1B_spec-1.0.1.jar
   * geronimo-jpa_3.0_spec-1.0.jar
   * geronimo-j2ee-connector_1.5_spec-1.0.1.jar
   * serp-1.11.0.jar
   - commons-logging-1.0.4.jar (used only in CommonsLogFactory when  
logging is configured to use commons)
   - commons-pool-1.3.jar (used only in TCPRemoteCommitProvider for  
distributed data caching)
   - geronimo-jms_1.1_spec-1.0.1.jar (used only in  
JMSRemoteCommitProvider for distributed data caching)
   - derby-10.2.2.0.jar (provided only as a convenience for getting  
started with the examples quickly)

The jars marked with stars (*) are the only ones that are actually  
required for OpenJPA to function in the common cases (the examples  
included in the distribution all run if you have just the starred  
libraries + derby).

My question: should we differentiate between the required libraries  
and the optional ones (perhaps by putting them in an /optional/  
directory or something)? Does anyone have experience with how this is  
done with other Apache projects?



Mime
View raw message