log4j-1.2.8 interface change

Discussion in 'Java' started by Divya Mali, Jun 29, 2004.

  1. Divya Mali

    Divya Mali Guest

    Hi,

    log4j-1.2.8 introduced an interface change from its previous version that
    forces code to be modified (obviously). We have a situation where we will be
    shipping a jar file that uses log4j-1.2.8 and our customers, who will be
    using classes in our jar, may still be using the previous version of log4j.
    Depending on the classpath, either our call to log4j-1.2.8 would fail or our
    customers call to old log4j would fail. I was wondering if there was a way
    to get around this problem. Would it possible to specify the classpath that
    our jar should be using at runtime using a java method (so that the
    classpath is not piucked from the environment variable CLASSPATH)?

    Thanks,

    Ganesh
     
    Divya Mali, Jun 29, 2004
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Alexandra Stehman

    eclipse, junit, log4j, & finding log4j.xml

    Alexandra Stehman, Jan 19, 2004, in forum: Java
    Replies:
    0
    Views:
    5,782
    Alexandra Stehman
    Jan 19, 2004
  2. Alex Hunsley
    Replies:
    2
    Views:
    12,945
    =?ISO-8859-15?Q?Fr=E9d=E9ric_G=E9din?=
    May 28, 2004
  3. Rodolfo
    Replies:
    0
    Views:
    958
    Rodolfo
    Jul 12, 2004
  4. joes
    Replies:
    1
    Views:
    2,176
  5. Gianni Galore
    Replies:
    0
    Views:
    1,276
    Gianni Galore
    Sep 8, 2010
Loading...

Share This Page