[jira] Resolved: (CXF-3020) Many of the JARS used by apache CXF have newer versions available that aren't being used.

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-3020.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.2.10)
                   2.2.11
         Assignee: Daniel Kulp



I've updated as much as we can.

We cannot update to Jetty 7 on 2.2.x as it's incompatible with Jetty 6.  We have updated to to Jetty 7 on trunk/2.3.

Jaxen 1.1.2 is not available in central.    Others have been updated.

> Many of the JARS used by apache CXF have newer versions available that aren't being used.
> -----------------------------------------------------------------------------------------
>
>                 Key: CXF-3020
>                 URL: https://issues.apache.org/jira/browse/CXF-3020
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Robert Liguori
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.2.11
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> In apache-cxf-2.2..10/lib, 65 JARs are listed.
> Many of these contained APIs have been updated...
> I looked at a few of them...
>   abdera v 1.0 is used, but is now at v 1.1
>   commons-codec v 1.3 is used, but is now at v 1.4
>   commons-lang v 2.4 is used, but is now at v 2.5
>   jaxen v 1.1.1 is used, but is now at v 1.1.2,
>   jetty 6.1.21 is used, but is now at v 7.
> It would be nice if all of the used JAR files (by Apache CXF) are audited against their latest versions, analyzed to see if an upgrade is feasible, and then upgraded (if need be) and tested.
> Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.