Subject: Readme for scripts/dev-setup/jdbc-dep directory
Date:    2010-05-25
--------------------------------------------------------

The jasperserver build has been refactored to ensure that there is only 
a single instance of any Spring Framework configuration file. Additionally,
there were cleanups to how configuration files are utilized such as
js.jdbc.properties, hibernate.cfg.xml, etc. 

There is an issue with the maven build tool where a pom file installed
to a local repository cannot have property values such as ${jdbc.driver.type}.

There was an automatic workaround for this issue built into the buildomatic
auto-config Ant scripts. 

However, if you are *not* using buildomatic you need to handle the work 
around step manually.

In this directory is a maven pom.xml file. You can edit this pom to point
to the jdbc driver that you need. If you are using the MySQL DB then 
you do not need to change it. Next, you can install this pom file into
your local repository.

Here are the steps:

1) Edit pom.xml 
  
   mysql (leave unchanged):

     <groupId>mysql</groupId>
     <artifactId>mysql-connector-java</artifactId>
     <version>5.1.10</version>
 
   postgresql:

     <groupId>postgresql</groupId>
     <artifactId>postgresql</artifactId>
     <version>8.1-407.jdbc3</version>

   other databases

    See buildomatic/conf_source/db/<db-type> for additional values

2) Execute in a shell

   cd <js-src>/scripts/dev-setup/jdbc-dep    (ie current-dir)

   mvn install

3) Outcome

   pom file will be installed to:

     ~/.m2/repository/com/jaspersoft/jasperserver/jdbc-dep/1.0/jdbc-dep-1.0.pom 

   unit-tests and db build steps will find the required jdbc driver using values
   you added to the pom file. 



Notes on already existing jdbc drivers:

  Look in the following directories for already existing jdbc drivers:
   
    <js-ce-src>/buildomatic/conf_source/db/<db-type>/jdbc/
     
    <js-pro-src>/buildomatic-additional/conf_source/db/<db-type>/jdbc/
     
     



===
