jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1569) Jackrabbit semi-validated with new libraries
Date Wed, 29 Apr 2009 08:52:31 GMT

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

Jukka Zitting resolved JCR-1569.
--------------------------------

    Resolution: Won't Fix
      Assignee: Jukka Zitting

Thanks for the information!

However, we normally only upgrade our dependencies when there's a clear reason to do so. So
each potential upgrade should be filed as a separate improvement issue with a rationale of
why upgrading the dependency would make Jackrabbit better.

> Jackrabbit semi-validated with new libraries
> --------------------------------------------
>
>                 Key: JCR-1569
>                 URL: https://issues.apache.org/jira/browse/JCR-1569
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.2
>         Environment: JDK 1.6; Tomcat 6; Windows 2003
>            Reporter: Julio Castillo
>            Assignee: Jukka Zitting
>
> Because we use a good number of open source libraries, I had to test Jackrabbit (to the
degree that I use it) with newer versions of other libraries that are embedded in the jackrabbit
war file.
> I successfully deployed and ran with the following upgrades (please upgrade your distribution
when possible).
> - slf4j 1.5.0
> - commons-codec 1.3
> - commons-collections 3.2
> - commons-httpclient 3.1
> - junit 4.4
> - log4j 1.2.15
> - xerces 2.9.1
> - pdfbox 0.7.3 that should include new dependency on fontbox 0.1 (See bug# 1567)
> - POI 3.0.2
> Couldn't upgrade the tm-extractors (see bug# 1568)

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