Skip to content
  • Oct 2, 2011

    prevayler-2.5

    [maven-release-plugin] copy for tag prevayler-2.5
    
  • Jun 7, 2006

    v2.3

    This commit was manufactured by cvs2svn to create tag
    'PREVAYLER_2_3'.
  • Jul 14, 2005

    v2.02.006

    Update jars, licenses, JDK1.5 compatibility (contirb classes) and gen…
    …erally synch with HEAD where it makes sense. Will tag as 2.02.006 shortly
  • Sep 29, 2004

    v2.02.005

    updated version to 2.02.005
    Jake
  • Sep 16, 2004

    v2.02.004

    removed "known bugs" section, per Klaus
    Jake
  • Aug 30, 2004

    v2.02.003

    fix typo in propery name for JDK 1.4 docs. Now the JDK API usage in j…
    …avadoc will show up as links.
    
    Jake
  • Jul 26, 2004

    v2.02.002

    remove "beta" postfix from version.
    Jake
  • May 6, 2004

    v2.02.001

    updated version number to 2.02.001beta and excluded **/foundation/Fil…
    …eIOTest.java in preparing for distribution.
    
    Jake
  • Apr 30, 2004

    v2.02.000

    This commit was manufactured by cvs2svn to create branch 'bugfix'.
    
  • Mar 14, 2004

    v2.01.000

    Specify versions on jar files to make clear which ones are being used…
    … as well as guarantee that the build controls which version of jars are being used. If the build points to a specific version and we don't have it stored in root/lib (for the skaringa and common-logging jars, that is) then the compile will fail. The cost will be that the distribution package for these jars will be downloaded each time, but the build will continue to fail until the build version is matched up to what is stored in CVS. This is a good thing, IMO. Updated sample.build.propeties with the build version and accounted for the new locations of skaringa and commons-logging jars to point to in root/lib.
    
    Jake
Something went wrong with that request. Please try again.