Stephen,
If we can verify that the new jars (with Phoenix, not just Merlin) are
working as well as the old (unknown vintage) ones, is there any reason not
to do a cvs remove of the unused jars? AFAIK, we are committed to moving
forward in HEAD. I put the released logkit v1.2 jar into phoenix-bin/lib
when the vote came through, so that's updated, and I believe that it just
makes sense to clean up the files in HEAD.
--- Noel
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 21, 2003 12:36
To: James Developers List
Subject: Re: Avalon Jars
Danny Angus wrote:
>Guys,
>
>I just did a clean checkout of the HEAD and dicover that theres a big load
of avalon jars in three seperate places,
>
>/lib
>/lib/candidates
>/phoenix-bin/lib
>
>Now HEAD builds and runs, but its impossible to develop because there are
conflicting classes in these avalon jars, and no clear indication of which
should be on the classpath and which are redundant.
>
>Stephen, if you read this could you help please...
>
Sure - I'm going to update the project.class.path to use the explicit
declarations from the default.properties file. This will ensure that
there is one and only one reference point for the identification of the
jars in use.
Cheers, Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
