[
https://issues.apache.org/jira/browse/UIMA-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674351#action_12674351
]
Adam Lally commented on UIMA-857:
---------------------------------
Personally, I still strongly dislike version numbers in jar file names, and it
doesn't have anything to do with the setUimaClasspath script, which I don't
really use. It has more to do with Eclipse - if I have lots of projects
depending on uima jars, then every time I got a new version I'd have to go
through them all and update their classpaths. It's not specifically
I think we are not in the same situation as Tomcat, because Tomcat is a
container in which you embed things, whereas UIMA gets embedded in other
things. Therefore, by changing our jar file names we are requiring those
embedders to keep up with us. I would not want to have to use a special jar
loader in my application just to use UIMA.
> Change startup of framework to support versioned Jars and simplified classpath
> ------------------------------------------------------------------------------
>
> Key: UIMA-857
> URL: https://issues.apache.org/jira/browse/UIMA-857
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Priority: Minor
>
> Our approach to the framework classpath is to (a) strip version info from our
> Jar names, and (b) have a setUimaClassPath script that adds lots of these
> (unversioned) jars to the classpath.
> Other systems use a different approach - usually putting all the jars that
> should be in the classpath into a directory, and then having a small wrapper
> jar (with an unversioned name) that adds all the jars it finds in this dir to
> the classpath. (See for instance, ActiveMQ startup, or the way things like
> Tomcat work). Change UIMA to use this approach. (Not for 2.2.2, but for
> following release, perhaps).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
