Matthew Seaman wrote:
On Thu, Sep 15, 2005 at 04:27:03PM +1200, Mark Kirkwood wrote:
Great - easy is always nice :-)
Indeed. However, my perspective is a bit different. I've already got
a mechanism for ensuring that log4j and junit get installed before
attempting to build the mysql-connector-java code -- that's just
standard dependency management that any software packaging system
worth it's salt will give you. In that sort of setup, you really do
prefer to use the separate log4j or junit packages -- avoiding
duplication being the key idea.
I've got no problem with the log4j or junit jars being supplied with
the mysql-connector-java sources, just so long as it's possible /not/
to use those particular ones while building.
Second that, an Ant target like 'cleanlibs' or similar would do the trick.
Indeed, I am quite happy for log4j and junit *not* to be shipped by
default, as folks wanting to build from source are probably going to be
reasonably savvy, and therefore comfortable fetching components from the
web.
However, they do need good install help - in particular listing the
dependencies - which as of right now is not there, and also a reasonably
simple way to add the Dependant jars into the compile classpath (the
3.2.x mechanism with the lib directory is good!).
Cheers
Mark
12 messages in com.mysql.lists.javaRe: Building connector 3.1.10 from sr...
.diff