[ 
https://issues.apache.org/jira/browse/OOZIE-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606800#comment-14606800
 ] 

Robert Kanter commented on OOZIE-2286:
--------------------------------------

Jenkins is still having trouble posting to JIRA.  Here's the results:
{noformat}
Testing JIRA OOZIE-2285

Cleaning local git workspace

----------------------------

+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    +1 the patch does not introduce any line longer than 132
    +1 the patch does adds/modifies 1 testcase(s)
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
    +1 HEAD compiles
    +1 patch compiles
    +1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
    +1 the patch does not modify JPA files
-1 TESTS
    Tests run: 1672
    Tests failed: 5
    Tests errors: 0

    The patch failed the following testcases:

      
testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)
      
testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService)
      
testStreamingWithMultipleOozieServers_coordActionList(org.apache.oozie.service.TestZKXLogStreamingService)
      
testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)
      
testMemoryUsageAndSpeed(org.apache.oozie.service.TestPartitionDependencyManagerService)

+1 DISTRO
    +1 distro tarball builds with the patch 

----------------------------
-1 Overall result, please check the reported -1(s)


The full output of the test-patch run is available at

   https://builds.apache.org/job/oozie-trunk-precommit-build/2423/
{noformat}

> Update Log4j and Log4j-extras to latest 1.2.x release
> -----------------------------------------------------
>
>                 Key: OOZIE-2286
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2286
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>             Fix For: trunk
>
>         Attachments: OOZIE-2286.001.patch
>
>
> Oozie currently uses log4j 1.2.16 and log4j-extras 1.1.  These were released 
> way back in 2010.  We should update to the newest releases 1.2.17 (though 
> they're also pretty old at 2012 and 2013 respectively), which fix some bugs.
> The changelogs are pretty minimal:
> log4j: https://logging.apache.org/log4j/1.2/changes-report.html#a1.2.17
> log4j-extras: 
> http://logging.apache.org/log4j/extras/changes-report.html#a1.2.17
> Looks like log4j-extras changed their versioning scheme to match log4j's 
> because 1.2.17 is the next release after 1.1.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to