[
https://issues.apache.org/jira/browse/UIMA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832743#comment-13832743
]
Jerry Cwiklik commented on UIMA-3452:
-------------------------------------
In addition to poms, Ducc's python scripts also need to change to make this
work. Currently, the ducc_util.py builds a CP using explicit jar names. I think
this is because all Ducc jars are directly in the lib folder. If we add
versions to jars, this would become a maintenance issue.
I propose that we move Ducc jars to a separate folder to be able to take
advantage of java's wildcard support. Now, there are two choices, we can move
jars to lib/uima or create a new folder say lib/ducc-uima. Actually, there is a
third choice - leave Ducc jars where they are (under lib) and construct the CP
with /lib/*. I believe java does not use recursion (not sure if this will
change in the future), so only Ducc's jars will be picked up.
> DUCCs jars should include a version number
> ------------------------------------------
>
> Key: UIMA-3452
> URL: https://issues.apache.org/jira/browse/UIMA-3452
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Affects Versions: 1.0-Ducc
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> Seems like DUCC follows the wrong example set by UIMA which is not to include
> version number in a jar name. Most Apache projects follow a convention which
> includes the version number. Modify poms to append a version number. Change
> CLI pom to name jars with versions.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
