On Fri, Feb 13, 2015 at 01:21:13PM -0500, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On 2/13/15 1:02 PM, Mark H. Wood wrote:
> > On Fri, Feb 13, 2015 at 11:46:37AM -0500, Christopher Schultz
> > wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gustavo,
On 2/14/15 10:42 AM, gustavo.avitab...@unina.it wrote:
> Quoting Christopher Schultz :
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Mark,
>>
>> On 2/13/15 1:02 PM, Mark H. Wood wrote:
>>> On Fri, Feb 13, 2015 at 11:46:37AM
Quoting Christopher Schultz :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/13/15 1:02 PM, Mark H. Wood wrote:
On Fri, Feb 13, 2015 at 11:46:37AM -0500, Christopher Schultz
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Alexander,
On 2/12/15 2:26 PM, Alexander Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/13/15 1:02 PM, Mark H. Wood wrote:
> On Fri, Feb 13, 2015 at 11:46:37AM -0500, Christopher Schultz
> wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Alexander,
>>
>> On 2/12/15 2:26 PM, Alexander Johnson wrote:
>>> It lo
On Fri, Feb 13, 2015 at 11:46:37AM -0500, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Alexander,
>
> On 2/12/15 2:26 PM, Alexander Johnson wrote:
> > It looks like that's true. It turns out this wasn't a permissions
> > issue at all. For some reason copyin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alexander,
On 2/12/15 2:26 PM, Alexander Johnson wrote:
> It looks like that's true. It turns out this wasn't a permissions
> issue at all. For some reason copying the JAR files out of the
> directory and back into it caused them to be picked up (
Thanks Chris,
It looks like that's true. It turns out this wasn't a permissions issue
at all. For some reason copying the JAR files out of the directory and
back into it caused them to be picked up (I read this in a suggestion
somewhere). Reading the 'man' entry for cp I see that it doesn't pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alexander,
On 2/10/15 8:48 PM, Alexander Johnson wrote:
> Thanks for the suggestions. I don't have access to the server
> where this is happening, but I did get a script to run there:
>
> echo Displaying JAR files with current permissions... ls -l
Alexander Johnson wrote:
Sorry, those aren't the actual project or directory names since I was
asked to obscure the information when seeking help. I've double-checked
and the actual directory names are consistent.
Yes, the target directory is created by the same build. We're using Maven
so thi
Sorry, those aren't the actual project or directory names since I was
asked to obscure the information when seeking help. I've double-checked
and the actual directory names are consistent.
Yes, the target directory is created by the same build. We're using Maven
so this all happens sequentially.
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, but I did get a script to run there:
>
> echo Displaying JAR files with current permissions...
> ls -la ./target/MyProject/WEB-INF/lib/
>
>
Thanks for the suggestions. I don't have access to the server where this
is happening, but I did get a script to run there:
echo Displaying JAR files with current permissions...
ls -la ./target/MyProject/WEB-INF/lib/
echo Adding read, write, and execute permission
On 06/02/2015 08:16, Alexander Johnson wrote:
> 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?\\
Usually file permissions on the file or one of the directories it is in.
Other possibilities include using
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
14 matches
Mail list logo
