on 2/18/01 5:39 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
> No question that this isn't Turbine's fault.
>
> Without gump, how long would this incompatibility gone unnoticed?
>
> There undoubtably are other projects out there using log4j. If each binds
> to a specific release and there isn't a period of deprecation, which
> version of the jar file do you put first in your classpath?
>
> The owner of the log4j project has been notified. At least twice - once by
> me and once by Jon.
>
> Still consider this a problem with Gump? ;-)
>
> - Sam Ruby
This is definitely not a problem with Gump. These types of things are
exactly what Gump is for. More education is in need since this feature of
development is new for a lot of us. :-)
Thanks Sam for heading this up.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
