search

google-code-export / uimafit

Automatically exported from code.google.com/p/uimafit
2 stars 1 forks source link

upgrade dependencies? #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
So we're using a particularly old version of commons-io (1.4 vs. the current 
2.4) for uimafit. Any chance we could upgrade that before the next release? 
There are also several other dependencies that have more recent releases:

[INFO] The following dependencies in Dependency Management have newer versions:
[INFO]   commons-io:commons-io ..................................... 1.4 -> 2.4
[INFO]   commons-lang:commons-lang ................................. 2.4 -> 2.6
[INFO]   org.jdom:jdom ........................................... 1.1 -> 2.0.2
[INFO]   org.springframework:spring-context .... 3.1.0.RELEASE -> 3.1.2.RELEASE
[INFO]   org.springframework:spring-core ....... 3.1.0.RELEASE -> 3.1.2.RELEASE
[INFO]   org.springframework:spring-test ....... 3.1.0.RELEASE -> 3.1.2.RELEASE

Original issue reported on code.google.com by steven.b...@gmail.com on 27 Jul 2012 at 7:23

GoogleCodeExporter commented 9 years ago 
uimaFIT does not really need the features of newer versions of these libraries. 
I upgraded Spring because it was necessary since older versions of Spring did 
not support the features I needed.

Is there any particular reason that we should upgrade except for it being 
possible to upgrade?

Original comment by richard.eckart on 27 Jul 2012 at 7:40

GoogleCodeExporter commented 9 years ago 
I was getting exceptions in my code because ClearTK uses commons-io 2.1, but 
uimafit was earlier in my pom.xml and was overriding this to commons-io 1.4. So 
the ClearTK code was failing because it couldn't find the methods that were 
supposed to be there. (The fix was to move uimafit later in the pom.xml.)

For the upgrades suggested above by "mvn versions:display-dependency-updates":

* commons-io 2.4 is binary compatible with 1.4:
http://commons.apache.org/io/upgradeto2_4.html

* commons-lang 2.6 is binary compatible with 2.5, but I couldn't tell about 
2.4: 
http://commons.apache.org/lang/upgradeto2_6.html
http://commons.apache.org/lang/upgradeto2_5.html

* jdom 2.0.2 is "a recommended upgrade for anyone still using JDOM 1.1.3 or 
earlier, and using Java5 or later"
http://www.jdom.org/

* I don't know spring, but 3.1.0 to 3.1.2 looks like a bugfix release that 
should be compatible, so that should be pretty safe to pull in.

In general, I think we should always pull in the latest bug fixes. But yeah, we 
want to be careful not to pull in anything with incompatible changes.

Original comment by steven.b...@gmail.com on 27 Jul 2012 at 7:58

GoogleCodeExporter commented 9 years ago 
I locally did bump all the versions. Looks like JDom 2 is an incompatible 
change, but it's only a test dependency. So I'd vote to leave jdom at version 1 
and potentially remove it completely at some point.

Original comment by richard.eckart on 27 Jul 2012 at 8:01

GoogleCodeExporter commented 9 years ago 
Sounds good to me.

Original comment by steven.b...@gmail.com on 27 Jul 2012 at 8:05

GoogleCodeExporter commented 9 years ago 
Fixed in revision 913.

Original comment by richard.eckart on 28 Jul 2012 at 9:18