uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Lally (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-857) Change startup of framework to support versioned Jars and simplified classpath
Date Wed, 18 Feb 2009 14:19:04 GMT

    [ https://issues.apache.org/jira/browse/UIMA-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674628#action_12674628

Adam Lally commented on UIMA-857:

I'm not sure if there's a way to check in the Eclipse library definitions to SVN and share
them.  If there is then this would probably be an okay way to deal with this.  But so far
the only experience I've had with the Eclipse libraries is checking out somebody's .classpath
file that referred to library and not being able to compile anything because the library was
undefined, which is not nice.

The bottom line for me is:  The Java runtime doesn't have a native way to easily support jar
file names that change all the time.  Yes, various development environments and embedding
applications have invented ways to add a level of abstraction on top of jar file names, but
there's no standard way of doing so, and the existing solutions are sometimes not ideal. 

It just seems simpler to me to avoid this whole issue by leaving our jar file names the way
they are.  I know, some people feel strongly that they like to see what version they have
just by looking at the file name, but I don't happen to be one of those people.

I agree that the UIMA_JARPATH idea is separate from the file names and have no objection to
implementing that.

> 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.

View raw message