[
https://issues.apache.org/jira/browse/UIMA-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-5624:
---------------------------------
Description:
The uimaj-examples project has a classpath file used to create the .classpath
for the examples Eclipse project in the binary distribution. This classpath
file has out-of-date version numbers for 3 jars needed to run the v3 migration
tool. Update the version numbers so they match the distribution, or better
yet, fix this so they're always automatically kept in sync.
The classpath file is also missing the slf4j api jar, and the slf4j connection
to the java unit logger jar. Without these, no logging is possible - and
running something like the Document Analyzer tool gives warnings about this.
was:The uimaj-examples project has a classpath file used to create the
.classpath for the examples Eclipse project in the binary distribution. This
classpath file has out-of-date version numbers for 3 jars needed to run the v3
migration tool. Update the version numbers so they match the distribution, or
better yet, fix this so they're always automatically kept in sync.
> uv3 update the version numbers of included JARs in the uimaj-examples
> classpath
> -------------------------------------------------------------------------------
>
> Key: UIMA-5624
> URL: https://issues.apache.org/jira/browse/UIMA-5624
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
>
> The uimaj-examples project has a classpath file used to create the .classpath
> for the examples Eclipse project in the binary distribution. This classpath
> file has out-of-date version numbers for 3 jars needed to run the v3
> migration tool. Update the version numbers so they match the distribution,
> or better yet, fix this so they're always automatically kept in sync.
> The classpath file is also missing the slf4j api jar, and the slf4j
> connection to the java unit logger jar. Without these, no logging is
> possible - and running something like the Document Analyzer tool gives
> warnings about this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
