RE: [jgrapht-developers] JGraphT backport

[Barak N. <bar...@us...>]

> - I created file etc/build.properties.template with the documented =
(but
> commented-out) property definitions in CVS.  In a distribution, this
> becomes etc/build.properties.  The reason I gave it a different name =
in
> CVS is to avoid developers accidentally editing it and committing
> site-specific changes.  Instead, developers should copy the template =
to
> etc/build.properties and edit that.  Distribution users can just edit
> etc/build.properties directly.

That's a good idea -- it allows developers to add their customized
etc/build.properties to their .cvsignore.

> In addition, I also made a change to the jar naming convention.  The =
jar
> name used to be based on the release version, but I have found this to
> be a pain in dependent projects, because it means with every upgrade I
> have to edit the dependent build file to reference the new version.
> Instead, the jar names are now:
>=20
> jgrapht-jdk1.4.jar (retrowoven version)
> jgrapht-jdk1.5.jar (standard compile)

Such a naming convention indeed eases upgrading.  However, there should =
be a
way to easily identify the version of each jar (if separated from the
distribution).  Perhaps each jar should include a 'version.txt' file at =
its
top-level; the 'version.txt' could be generated automatically and =
include
the respective JGraphT version info.

Barak=20