Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: PEAR Classpath issues
From: =?iso-8859-1?Q?Erik_F=E4=DFler?= <erik.faessler@uni-jena.de>
In-Reply-To: <5012342B.4060104@gmx.de>
Date: Fri, 27 Jul 2012 10:51:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DC04909-E16A-44E7-814B-B9F0F8A3104A@uni-jena.de>
References: <24545B78-89E3-49D4-9ADB-A5ADB76C1BD3@uni-jena.de>
 <5012342B.4060104@gmx.de>
To: user@uima.apache.org

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."
>=20
> 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.

>>=20
>> 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?
>=20
> I think the answer to that is "yes", but I'm not sure I really
> understand your question.
>=20

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.

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