Adam Lally wrote:
My general opinion is - warn developers on possible conflicts, but
let them
go their own way.
1) I believe, PEAR Packager may post a warning that adding UIMA JARs to
a PEAR package may lead to conflicts, but it should not prevent
developers
from doing this, because we canno
On 1/16/07, Adam Lally <[EMAIL PROTECTED]> wrote:
On 1/16/07, Lev Kozakov <[EMAIL PROTECTED]> wrote:
> The PEAR validation code uses UIMA ResourceManager mechanism to add
several
> JARs to the classpath, but it does not override the default class
loader.
> Therefore, the 'extension' classes, whi
On 1/16/07, Lev Kozakov <[EMAIL PROTECTED]> wrote:
The PEAR validation code uses UIMA ResourceManager mechanism to add several
JARs to the classpath, but it does not override the default class loader.
Therefore, the 'extension' classes, which are specified in the component
classpath, are searched
On 1/15/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
A user posted a forum question on
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=444&thread=145870&cat=28
.
That link has a trail of discussion that led to a resolution - the
failing case involved the
PEAR including in its
A user posted a forum question on
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=444&thread=145870&cat=28
.
That link has a trail of discussion that led to a resolution - the
failing case involved the
PEAR including in its lib/ subdirectory some UIMA framework Jars, such
as
