uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Closed: (UIMA-1054) Correct some version dependency levels in uima-as build / poms
Date Mon, 09 Jun 2008 20:22:44 GMT

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

Marshall Schor closed UIMA-1054.

    Resolution: Fixed

Testing uncovered that log4j at 1.2.8 failed - so made the build have log4j at 1.2.12 level.
 Lesson learned - if some component requires a level (e.g.) 1.2.12 and others use (e.g.) 1.2.8,
 it may be best to include the later version because it has new function or fixes needed,
and may run the older APIs just fine.

The other "downgrade" of levels recently done for jetty and httpclient were done to match
the activemq 4.1.1 levels from earlier attempts to use activemq5.0.0.  So these should be
OK, and appear to be ok from the testing.

> Correct some version dependency levels in uima-as build / poms
> --------------------------------------------------------------
>                 Key: UIMA-1054
>                 URL: https://issues.apache.org/jira/browse/UIMA-1054
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.2.2AS
> Scanning the dependency tree produced with mvn dependency:tree revealed some incorrect
version dependency levels.   While these probably do not affect anything (unless the APIs
changed with release levels in a way that would affect our code), it would be good to be consistent
between the levels in the POM used for compiling and the levels included in the bin distribution.

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

View raw message