cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-3020) Many of the JARS used by apache CXF have newer versions available that aren't being used.
Date Thu, 07 Oct 2010 06:48:31 GMT

    [ https://issues.apache.org/jira/browse/CXF-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918797#action_12918797
] 

Andreas Veithen commented on CXF-3020:
--------------------------------------

The Axiom version should indeed not be changed since upgrading to a newer version causes issues
in Abdera; see ABDERA-267.

What about the ASM dependency? Is CXF compatible with ASM 3.2?

> 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.


Mime
View raw message