Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 59226] StandardJarScanner ignores jars in manifest Class-path
 header
Date: Tue, 03 May 2016 08:44:00 +0000
Message-ID: <bug-59226-78-iYnOFNtKYT@https.bz.apache.org/bugzilla/>
In-Reply-To: <bug-59226-78@https.bz.apache.org/bugzilla/>
References: <bug-59226-78@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0
archived-at: Tue, 03 May 2016 08:44:04 -0000

https://bz.apache.org/bugzilla/show_bug.cgi?id=59226

--- Comment #8 from Mark Thomas <markt@apache.org> ---
Update.

I've spent a fair amount of time looking at the proposed patch to see if there
is a way to avoid processing a JAR once to look at the class path and again to
scan it. I think it is possible but it is going to need some refactoring.

Regarding the proposed patch, it doesn't handle all of the cases that the Jar
Scanner does (packed WARs, exploded JARs, etc.) which is why I'd prefer to do
this in a single scan.

Reviewing the code has also uncovered some minor bugs that need to be fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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