[
https://issues.apache.org/jira/browse/UIMA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757867#action_12757867
]
Marshall Schor commented on UIMA-1273:
--------------------------------------
If I understand this correctly, the change will not break Pear packages built
with the pear packager - users still do not need to specify Class Path entries
for Jars in the lib directory, because the pear packager will create an
explicit classpath for those jars as part of the packaging process. Is this
correct? If so, I'm OK with this change after we fix the documentation to say
what's going on a bit more precisely.
> Pear runtime pulls in all jar files in pear lib directory, no matter if
> they're on the classpath or not
> -------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1273
> URL: https://issues.apache.org/jira/browse/UIMA-1273
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.2.2
> Reporter: Thilo Goetz
> Fix For: 2.3
>
>
> The pear runtime will not only use the classpath as defined in
> metadata/install.xml, it will also pick up any jar in the lib directory. It
> even recurses down into subdirectories. This is undocumented, and most
> unexpected.
> I chatted with Michael about this. He thinks it may be because the same code
> that creates the classpath in the pear packager is used in the runtime. The
> packager does collect all jar files it can find and puts them in the
> classpath, and the pear file. That's fine for the packager, but not the
> runtime. We should *either* have an explicit classpath, *or* use all jar
> files in the lib dir, but not both.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
