[Proxool-cvs] proxool CHANGES.txt,1.29,1.30 build.xml,1.66,1.67

[<bil...@us...>]

Update of /cvsroot/proxool/proxool
In directory sc8-pr-cvs1:/tmp/cvs-serv25518

Modified Files:
	CHANGES.txt build.xml 
Log Message:
new revision

Index: CHANGES.txt
===================================================================
RCS file: /cvsroot/proxool/proxool/CHANGES.txt,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** CHANGES.txt	27 Oct 2003 13:13:58 -0000	1.29
--- CHANGES.txt	5 Nov 2003 00:19:48 -0000	1.30
***************
*** 6,10 ****
  $Author$
  
! 0.8.1 - October 27, 2003
  
  - NullPointerException that occured during SQL logging for certain methods
--- 6,24 ----
  $Author$
  
! 0.8.2 - 4 November 2003
! 
! - Fixed bug where delegate properties weren't being passed onto the delegate driver. If you weren't
!   passing any properties other than username and password to the delegate driver then this didn't
!   cause a problem anyway. (Note that Proxool properties were being recognised correctly.) Added a
!   new unit test specifically for this problem.
! 
! - Throw a friendlier exception if you try and add a statistics listener to a pool with
!   no statistics
! 
! - Statistics now creates write locks less often. This was causing a problem during heavy loads
!   even though the process of collecting statistics itself was very fast. If you had statistics
!   turned off (the default) then this wasn't a problem anyway.
! 
! 0.8.1 - 27 October 2003
  
  - NullPointerException that occured during SQL logging for certain methods
***************
*** 16,20 ****
    during removal of shutdownHook that occurs during JVM shut down.
  
! 0.8.0 - October 26, 2003
  
  - We now use Cglib's proxy library. Together with dropping the use of Timer
--- 30,34 ----
    during removal of shutdownHook that occurs during JVM shut down.
  
! 0.8.0 - 26 October 2003
  
  - We now use Cglib's proxy library. Together with dropping the use of Timer
***************
*** 83,87 ****
  - Batched statements are now correctly reported with the trace feature.
  
! 0.7.2 - April 28, 2003
  
  - Moved DataSourceTest into Sandbox so that the Ant test target
--- 97,101 ----
  - Batched statements are now correctly reported with the trace feature.
  
! 0.7.2 - 28 April 2003
  
  - Moved DataSourceTest into Sandbox so that the Ant test target
***************
*** 93,97 ****
    when there was no change, and didn't call it when there was.
  
! 0.7.1 - April 19, 2003
  
  - Added a lot of concurrency code - mainly using concurrent package
--- 107,111 ----
    when there was no change, and didn't call it when there was.
  
! 0.7.1 - 19 April 2003
  
  - Added a lot of concurrency code - mainly using concurrent package
***************
*** 134,138 ****
    definition had changed.
  
! 0.7 - February 21, 2003
  
  - We have dropped the dependency on commons-logging.jar
--- 148,152 ----
    definition had changed.
  
! 0.7 - 21 February 2003
  
  - We have dropped the dependency on commons-logging.jar
***************
*** 181,185 ****
    house-keeper-test-sql) rather than waiting for the next scheduled sweep.
  
! 0.6 (January 23, 2003)
  
  - ProxoolFacade API has changed slightly. Some of the methods no
--- 195,199 ----
    house-keeper-test-sql) rather than waiting for the next scheduled sweep.
  
! 0.6 - 23 January 2003
  
  - ProxoolFacade API has changed slightly. Some of the methods no
***************
*** 226,230 ****
    See ProxoolFacade#updateConnectionPool.
  
! 0.5 (December 3, 2002)
  
  - Fix finalisation of old instances. If you deploy to some environments in
--- 240,244 ----
    See ProxoolFacade#updateConnectionPool.
  
! 0.5 - 3 December 2002)
  
  - Fix finalisation of old instances. If you deploy to some environments in
***************
*** 281,285 ****
    that encounter certain types of exception.
  
! 0.4 - September 19, 2002
  
  - Rethink of how we organise our source code so that we can easily build
--- 295,299 ----
    that encounter certain types of exception.
  
! 0.4 - 19 September 2002
  
  - Rethink of how we organise our source code so that we can easily build

Index: build.xml
===================================================================
RCS file: /cvsroot/proxool/proxool/build.xml,v
retrieving revision 1.66
retrieving revision 1.67
diff -C2 -d -r1.66 -r1.67
*** build.xml	27 Oct 2003 13:13:58 -0000	1.66
--- build.xml	5 Nov 2003 00:19:48 -0000	1.67
***************
*** 27,31 ****
  
      <!-- Currect release, e.g. 0.6 -->
!     <property name="release" value="0.8.1"/>
  
      <!-- Currect release, e.g. 0.6 -->
--- 27,31 ----
  
      <!-- Currect release, e.g. 0.6 -->
!     <property name="release" value="0.8.2"/>
  
      <!-- Currect release, e.g. 0.6 -->
***************
*** 277,280 ****
--- 277,281 ----
              <jvmarg line="${jvmargs}"/>
          </java>
+         <echo message="Note! These unit tests have probably produced some worrying exceptions. As long as the tests passed then you can ignore these exceptions. They are part of the tests."/> 
      </target>