Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of rosenberg.leon@googlemail.com
 designates 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hWxxsZCISzwusgBibaL+SFrPeGyGOyg5fDC/H7sK2r/YXbfwZwO0PtQKGYTnnFOCKdLaUkL1MEjjtAFbJvRwrpSBV06wZxXY1X4ITjx04VjdoSNNBE7aaBUWvLf1jjwgujmnCsALxfWijrKudhvKaYIT6gisQeS814Z605HoDgw=
Message-ID: <327858f40701051659g3a528319w89a7905d400e1750@mail.gmail.com>
Date: Sat, 6 Jan 2007 01:59:35 +0100
From: "Leon Rosenberg" <rosenberg.leon@googlemail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: signjar Ant task no longer works after Tomcat 5.5 upgrade
In-Reply-To: <459EE528.2080600@tom-mack.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <459EE528.2080600@tom-mack.com>

I remember several issues about jasper holding references to the
libraries in the past, maybe you should check bugzilla for appropriate
issues and eventually known workarounds:

http://issues.apache.org

regards
Leon

On 1/6/07, Tom Mack <apache-tomcat@tom-mack.com> wrote:
> I use org.apache.jasper.JspC to precompile my JSP files. I also use the
> signjar task to sign my JARs at the end of the build process (Some of
> them are served via Java Web Start). This all worked fine until I
> upgraded to Tomcat 5.5.20 (from 4.1.31).
>
> If the signing task depends on the build step, the build part will run
> just fine (JSPs will be precompiled and everything else works) but the
> signjar task will fail with:
>
>   [signjar] Signing JAR: C:\dev\eclipse\xxxx\lib\SqlServer.jar
>   [signjar] jarsigner: attempt to rename
> C:\dev\eclipse\xxxx\lib\SqlServer.jar to
> C:\dev\eclipse\xxxx\lib\SqlServer.jar.orig failed
>
> (SqlServer.jar happens to be the first alphabetically of about a hundred
> JARs.)
>
> If I make the signing task not depend on the build and run each
> independently (type "ant build", wait, and then type "ant sign")
> everything works just fine.
>
> After looking at all the build files, I determined that the only thing
> of substance that has changed is the version of the
> org.apache.jasper.JspC that is being used in the Ant taskdef.
>
> A few other notes, all of the JARs that are being signed are copied to
> that C:\dev\eclipse\xxxx\lib directory at the beginning of the build
> script. But, all of the JARs in that lib directory are placed on the
> classpath for the JspC task. My guess is that the new JspC is somehow
> holding on to its classpath entries differently than the old one did
> (although looking at the JspC code, I couldn't really convince myself
> that this was the case considering they both build up the classloader
> similarly).
>
> Has anyone seen anything like this or have any ideas?
>
> --Tom
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org