See: http://jenkins.ovirt.org/view/01%20Unstable%20Jobs%20(ALL)/job/ovirt-engine-extension-logger-log4j_master_create-rpms-fc21-x86_64_merged/7/artifact/exported-artifacts/logs.tgz build.log: Buildfile: /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/build.xml conf: [copy] Copying 1 file to /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/output main: [mkdir] Created dir: /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/target/main [mkdir] Created dir: /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/output/modules/org/ovirt/engine-extensions/logger/log4j/main [copy] Copying 2 files to /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/target/main [javac] Compiling 2 source files to /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/target/main [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.7 [javac] /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/src/main/java/org/ovirt/engineextensions/logger/log4j/Log4jLogger.java:25: error: cannot find symbol [javac] import org.apache.log4j.Hierarchy; [javac] ^ [javac] symbol: class Hierarchy [javac] location: package org.apache.log4j [javac] /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/src/main/java/org/ovirt/engineextensions/logger/log4j/Log4jLogger.java:28: error: cannot find symbol [javac] import org.apache.log4j.spi.RootLogger; [javac] ^ [javac] symbol: class RootLogger [javac] location: package org.apache.log4j.spi [javac] /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/src/main/java/org/ovirt/engineextensions/logger/log4j/Log4jLogger.java:43: error: cannot find symbol [javac] private org.apache.log4j.Logger logger = new RootLogger(org.apache.log4j.Level.ALL); [javac] ^ [javac] symbol: class RootLogger [javac] location: class Log4jLogger [javac] /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/src/main/java/org/ovirt/engineextensions/logger/log4j/Log4jLogger.java:109: error: cannot find symbol [javac] LoggerRepository hierarchy = new Hierarchy(logger); [javac] ^ [javac] symbol: class Hierarchy [javac] location: class Log4jLogger [javac] /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/src/main/java/org/ovirt/engineextensions/logger/log4j/Log4jLogger.java:119: error: constructor LoggingEvent in class LoggingEvent cannot be applied to given types; [javac] logger.callAppenders(new LoggingEvent(record.getSourceClassName(), [javac] ^ [javac] required: no arguments [javac] found: String,Logger,Level,String,Throwable [javac] reason: actual and formal argument lists differ in length [javac] 5 errors [javac] 1 warning BUILD FAILED /builddir/build/BUILD/ovirt-engine-extension-logger-log4j-1.0.1/build.xml:77: Compile failed; see the compiler error output for details. Total time: 5 seconds Makefile:26: recipe for target 'ant' failed
fedora-21 provides log4j version 2 without package rename, this is amazing! they renamed the legacy to log4j12, but did not provide proper support for build-classpath to work. not sure why the new log4j package is not log4j2 and keep interface. anyway, the log4j2 and log4j12 are not api compatible, there is log4j-api-1.2 that contains subset of the api, I am unsure if this subset is sufficient. but as java as no preprocessor same source cannot support two apis. as we need to support all environments, I suggest to wait for fedora to address bug#1182346 and not invest resources.
rpm successfully build on fc22 on current master
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.