[
https://issues.apache.org/jira/browse/UIMA-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674442#action_12674442
]
Marshall Schor commented on UIMA-857:
-------------------------------------
Maybe we're confusing 2 things here - (a) ways of specifying jars to include in
the classpath, and (b) whether or not to strip version numbers from the jars.
It seems these are independent - one can have a UIMA_JARPATH kind of thing with
unversioned jars or not.
Regarding versioning the jars, if the issue is Eclipse, there's a feature in
Eclipse to create user "libraries" which are like the UIMA_JARPATH idea - they
are collections of jars with a name. If you wanted to, you could have a user
library for UIMA and have your projects use this library in their classpath;
then if you wanted to update the jars to a new level, you could just modify the
user library definition once, and all the projects that used the library would
get the new definition. Would this address the concern about Eclipse users?
I'm thinking that the thing that might set up a classpath based on UIMA_JARPATH
kind of spec would be optional, and wouldn't be needed in Eclipse if the user
library mechanism is used.
There are other mechanisms that people use, as well, such as "maven" - which
sets up the class path for eclipse projects when the user executes the maven
eclipse plugin. These would continue to work, as well.
> 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.
