the tomcat7-maven-plugin. It seems a
little sketchy that I don't really know the root cause of the problem, but
I'm happy that it's now fixed.
-Alex
On 2/11/15, 8:13 AM, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
chance for it to be asynchronous. Good thinking
though!
-Alex
On 2/10/15, 6:10 PM, "Konstantin Kolinko" wrote:
>2015-02-11 4:48 GMT+03:00 Alexander Johnson :
>> Thanks for the suggestions. I don't have access to the server where
>>this
>> is happening,
/workspace/MY_JENKINS_JOB/tomcat7/webapps/../../target/MY_PROJE
CT/WEB-INF/lib/activation-1.1.jar (No such file or directory)
at java.util.zip.ZipFile.open(Native Method)
I'm still at a loss...
-Alex
On 2/6/15, 1:45 AM, "Mark Thomas" wrote:
>On 06/02/2015 08:16, Alexande
ate e-mail about it.
On 2/4/15, 8:13 PM, "Alexander Johnson" wrote:
>Original question here:
>http://stackoverflow.com/questions/28181602/whats-the-difference-between-w
>ebappclassloader-and-standardjarscanner
>
>I'm able to run my team's webapp on my local
I'd like to know what could cause Tomcat or the native Java ZipFile.open
method to claim that a file does not exist when it actually does? This
has been a blocking issue for some of my work for the past month. It's
happening when attempting to run the tomcat7-maven-plugin. It works fine
on most
Original question here:
http://stackoverflow.com/questions/28181602/whats-the-difference-between-webappclassloader-and-standardjarscanner
I'm able to run my team's webapp on my local machine using the
tomcat7-maven-plugin. Unfortunately when I attempt to do the same on the build
server it bre
