Sam Ruby wrote:

compile:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-avalon-logkit/build
[mkdir] Created dir: /home/rubys/jakarta/jakarta-avalon-logkit/build/classes
[javac] Compiling 79 source files to /home/rubys/jakarta/jakarta-avalon-logkit/build/classes
[javac] /home/rubys/jakarta/jakarta-avalon-logkit/src/java/org/apache/log/output/lf5/LF5LogTarget.java:61: package org.apache.log4j.lf5.viewer does not exist
[javac] import org.apache.log4j.lf5.viewer.LogBrokerMonitor;
[javac] ^

This looks like a circular dependency?  (log4j and logkit)
circular? Why circular?

  <project name="jakarta-log4j">
    <package>org.apache.log4j</package>

    <ant target="jar">
      <property name="version" value="@@DATE@@"/>
    </ant>

    <depend project="jakarta-ant" inherit="runtime"/>
    <depend project="xml-xerces"/>
    <option project="jms"/>
    <option project="jmx"/>
    <option project="junit"/>
    <option project="javamail"/>

    <jar  name="log4j-@@DATE@@.jar"/>

    <nag to="[EMAIL PROTECTED]"
         from="Ceki Gülcü &lt;[EMAIL PROTECTED]&gt;"/>
  </project>

log4j doesn't depend on logkit.

Could this
particular viewer be conditionally compiled based on the availability of the LogBrokerMonitor class?
yep. That was in place, but it seems broken again now. Need to fix.

Nevertheless, looking at http://cvs.apache.org/builds/gump/latest/jakarta-log4j.html

log4j.jar:
[jar] Building jar: /home/rubys/jakarta/jakarta-log4j/log4j-20030205.jar

log4j-chainsaw.jar:
[jar] Building jar: /home/rubys/jakarta/jakarta-log4j/log4j-chainsaw-20030205.jar

log4j-lf5.jar:
[jar] Building jar: /home/rubys/jakarta/jakarta-log4j/log4j-lf5-20030205.jar

it seems like the log4j gump definition needs to be modified to also build 3 jars so logkit only needs to depend on the lf5 jar.

cheers,

- Leo


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to