Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1544ADD8F for ; Fri, 27 Jul 2012 10:03:26 +0000 (UTC) Received: (qmail 35671 invoked by uid 500); 27 Jul 2012 10:03:25 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 35608 invoked by uid 500); 27 Jul 2012 10:03:25 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 35437 invoked by uid 99); 27 Jul 2012 10:03:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jul 2012 10:03:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of twgoetz@gmx.de designates 213.165.64.23 as permitted sender) Received: from [213.165.64.23] (HELO mailout-de.gmx.net) (213.165.64.23) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 27 Jul 2012 10:03:17 +0000 Received: (qmail invoked by alias); 27 Jul 2012 10:02:55 -0000 Received: from p5482A41C.dip.t-dialin.net (EHLO [192.168.0.2]) [84.130.164.28] by mail.gmx.net (mp017) with SMTP; 27 Jul 2012 12:02:55 +0200 X-Authenticated: #25330878 X-Provags-ID: V01U2FsdGVkX194La4WujZ4uaKWnQXyHCLu8zCR2t7oiNCC4BA0Ju tnk/E4zBy6lVAp Message-ID: <5012674C.5040304@gmx.de> Date: Fri, 27 Jul 2012 12:02:52 +0200 From: Thilo Goetz User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: user@uima.apache.org Subject: Re: PEAR Classpath issues References: <24545B78-89E3-49D4-9ADB-A5ADB76C1BD3@uni-jena.de> <5012342B.4060104@gmx.de> <3DC04909-E16A-44E7-814B-B9F0F8A3104A@uni-jena.de> In-Reply-To: <3DC04909-E16A-44E7-814B-B9F0F8A3104A@uni-jena.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Erik, On 27/07/12 10:51, Erik F��ler wrote: > Hi Thilo! > > Thanks for your answer! Some comments and further questions below: > > Am 27.07.2012 um 08:24 schrieb Thilo Goetz: > >>> I did intentionally not include my libraries in the classpath here, because the documentation says, >>> "The buildComponentClasspath method of the PackageBrowser class builds a classpath string from what it finds in the CLASSPATH specification here, plus adds a classpath entry for all Jars in the lib directory. Because of this, there is no need to specify Class Path entries for Jars in the lib directory." >> >> If the documentation still says that, I think it's outdated. I'm pretty >> sure we changed this defaulty behavior at some point. > > *cough* It doesn't. I am very sorry - I must have confused documentation versions while being in the full action of research for information. The new version just says, Eclipse classpath entries would be included. > >>> >>> And one fall-back-question: In case I would just add all my libraries manually into the install.xml, would I still get the PEAR isolation? >> >> I think the answer to that is "yes", but I'm not sure I really >> understand your question. >> > > My ultimate goal is to run two components in one pipeline where the two components use incompatible versions of the same library. The ability to do so was called "PEAR isolation" in older versions of the UIMA documentation. yes, that should work just fine. > > I will try this out now, after I just got the classpath entries managed using the Maven PEAR packaging plugin. > > Thx a lot for your help, > > Erik >