CVS Update: Barracuda

CVSROOT:	/u/cvs
Module name:	Barracuda
Repository:	Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/contrib/dbroggisch/webapp/
Changes by:	JacobK@frogger.	02/10/23 21:09:55

Modified files:
	Projects/EnhydraOrg/toolsTech/Barracuda/src/: build-contrib.xml 
	                                              build.xml 
	                                              sample.build.properties 
	Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/contrib/dbroggisch/webapp/: 
	                                                                                              build.xml 
Added files:
	Projects/EnhydraOrg/toolsTech/Barracuda/src/: 
	                                              sample.version.properties 
	Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/contrib/dbroggisch/webapp/: 
	                                                                                              version.properties 

Log message:
	Added a new concept of a version.properties file.  This file is defines both the version of the libraries that barracuda requires/creates and where they exist.  This provides for more transparent dependency checking.  The build.xml just knows the libraries by generic names such as the property name "gnu-regexp.jar".  That property name is mapped to the real jar via the "location.gnu-regexp" and "version.gnu-regexp" properties set in the version.properties file.  So, the build.xml files know what general library they need, but don't need to be constantly edited for the specific version.  That is done in the sample.version.propeties file.  If we change versions, we must change this file.  This enforces the specific versions that Barracuda supports.  If we decide that Barracuda does indeed support the new version of a jar file, then that decision needs to be recorded in the sample.version.properties file.  All build files inside the Barracuda project are now synced upon this c!
 
oncept.
	
	I also did a little cleanup of the build files....removing some lesser used properties and targets.  In addition, I created an environment variable that can be read inside both property files and the build.xml file.  The only place where it is used right now is in the build.properties file which extracts the value of the CATALINA_HOME and JAVA_HOME environment variables.  These are commonly set and make it so it is less likely that one would have to edit the build.properties file for their own system.  Everything shoudl work just fine as long as the user has defined CATALINA_HOME and JAVA_HOME in their environment.  Things are just more automatic now.
	
	I tested all this by first running the "superclean" targets on both the main build and Diez' contrib package and then ran this:
	
	ant contrib test -Dsubproject=dbroggisch -Dsubtarget=install
	
	Everything succeeded so all should be well with the build files.  I don't think I introduced any regressions.
	
	Jake

===================================================================
File: no file build-contrib.xml		Status: Unknown

   Working revision:	No entry for build-contrib.xml
   Repository revision:	No revision control file

===================================================================
File: no file build.xml		Status: Needs Checkout

   Working revision:	1.25	Thu Oct 24 04:09:55 2002
   Repository revision:	1.25	/u/cvs/Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/contrib/dbroggisch/webapp/build.xml,v

   Existing Tags:
	Barracuda_1_1_1          	(revision: 1.14)

===================================================================
File: no file sample.build.properties		Status: Unknown

   Working revision:	No entry for sample.build.properties
   Repository revision:	No revision control file

===================================================================
File: no file build.xml		Status: Needs Checkout

   Working revision:	1.25	Thu Oct 24 04:09:55 2002
   Repository revision:	1.25	/u/cvs/Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/contrib/dbroggisch/webapp/build.xml,v

   Existing Tags:
	Barracuda_1_1_1          	(revision: 1.14)

===================================================================
File: no file sample.version.properties		Status: Unknown

   Working revision:	No entry for sample.version.properties
   Repository revision:	No revision control file

===================================================================
File: version.properties	Status: Up-to-date

   Working revision:	1.1	Thu Oct 24 04:09:55 2002
   Repository revision:	1.1	/u/cvs/Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/contrib/dbroggisch/webapp/version.properties,v

   Existing Tags:
	No Tags Exist