Hi David,
Thank you for your feedback. I upgraded to 2.3.0 because the entire code
seems to be dependent upon 2.3.0.
A quick look for the uimafit dependencies:
[INFO]
------------------------------------------------------------------------
[INFO] Apache UIMA uimaFIT 2.3.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ uimafit ---
[INFO] org.apache.uima:uimafit:pom:2.3.0
[INFO] +- org.apache.uima:uimafit-core:jar:2.3.0:compile
[INFO] | +- commons-lang:commons-lang:jar:2.6:compile
[INFO] | +- commons-io:commons-io:jar:2.2:compile
[INFO] | +- commons-logging:commons-logging-api:jar:1.1:compile
[INFO] | +- *org.apache.uima:uimaj-core:jar:2.9.0:compile*
uimafit seems also to be dependent upon uimaj 2.9.0 (which matches our
current setup). Upgrading uimafit to 2.3.1 would force uimaj to 2.10.0.
Upgrading uimafit to 2.4.0 would force uimaj to 2.10.2
Checking an upgrading to latest uima:
$ git diff
diff --git a/pom.xml b/pom.xml
index bc98d5b7..ef922e6a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -83,8 +83,8 @@
<maven.compiler.target>1.8</maven.compiler.target>
<maven-surefire-plugin.version>2.12.1</maven-surefire-plugin.version>
<exec-maven-plugin.version>1.2.1</exec-maven-plugin.version>
- <uimaj.version>2.9.0</uimaj.version>
- <uimafit.version>2.3.0</uimafit.version>
+ <uimaj.version>2.10.2</uimaj.version>
+ <uimafit.version>2.4.0</uimafit.version>
<spring.version>4.3.12.RELEASE</spring.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
Although all tests seem to *pass* (an upgrade looks as safe), default
profile has some integration-tests set to be skipped. I wasn't comfortable
to make the change until fixing all integration tests.
Alex
On Mon, Nov 27, 2017 at 7:45 PM, David Kincaid <[email protected]>
wrote:
> Thanks for upgrading uimafit. I was thinking of giving it a try myself when
> I had a chance. I see that you upgrades to 2.30, but the most recent
> version is 2.4.0. Was there a problem with 2.4.0?
>
> - Dave
>
> On Mon, Nov 27, 2017 at 6:08 PM, Alexandru Zbarcea <[email protected]>
> wrote:
>
> > Hi Sean,
> >
> > I have noticed your commits for CTAKES-485 [2]. Kudos for the commit
> > messages. I started to like the Jenkins integration [3], where in the
> > changes section you can click on the change and takes you to the Jira
> > issue. Will also ease the release process to identify the features.
> >
> > I have also fixed the uimafit dependencies to use ${uimafit.version}
> across
> > the entire project [1]. Upgrading from 2.2.0 to 2.3.0 seemed to hove not
> > affect over the project. All tests pass. I didn't see any issue, but
> please
> > also keep an eye. Without more test coverage, is hard to make sure there
> > was no harm done.
> >
> > Hope it helps,
> > Alex
> >
> > [1] - https://issues.apache.org/jira/browse/CTAKES-457
> > [2] - https://issues.apache.org/jira/browse/CTAKES-485
> > [3] -
> > https://builds.apache.org/view/C/view/Apache%20cTAKES/
> > job/ctakes-trunk-compiletest/1151/changes
> >
>
