Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of Chuck.Caldarale@unisys.com
 designates 216.82.243.50 as permitted sender)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Date: Thu, 21 Feb 2013 10:39:40 -0600
Subject: RE: JarScanning
Thread-Topic: JarScanning
Thread-Index: Ac4QUWmYhH84ew0NRnq6cRH3V7UaTgAAFKCA
Message-ID: 
 <99C8B2929B39C24493377AC7A121E21FC49EF19D83@USEA-EXCH8.na.uis.unisys.com>
References: <51264CA8.9040503@apache.org>
In-Reply-To: <51264CA8.9040503@apache.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: Mark Thomas [mailto:markt@apache.org]=20
> Subject: JarScanning

> jarsToScan
> This is a little more complicated.
> First of all, how does it work? The suggestion is:
> - If jarsToScan matches, scan it
> - else if jarsToSkip matches, skip it
> - else scan it

>From the above, it looks like the only purpose of jarsToScan is to avoid ch=
ecking the jarsToSkip list.  Unless such checking is expensive, this seems =
like an unnecessary complication.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL and is thus for use only by the intended recipient. If you received =
this in error, please contact the sender and delete the e-mail and its atta=
chments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org