Re: How to force keystoreFile and truststoreFile to be absolute paths

Chris, On 6/24/2016 9:07 AM, Christopher Schultz wrote: > Mark, > > On 6/21/16 3:46 PM, Mark Eggers wrote: >> On 6/21/2016 11:03 AM, Miller, Gerald wrote: >>> I'm seeing errors from attempts to append uncorrected paths >>> (e.g., C:\out\) and corrected ones (e.g., ~/out/) onto some >>> arbitrary

Re: How to force keystoreFile and truststoreFile to be absolute paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 6/21/16 3:46 PM, Mark Eggers wrote: > On 6/21/2016 11:03 AM, Miller, Gerald wrote: >> I'm seeing errors from attempts to append uncorrected paths >> (e.g., C:\out\) and corrected ones (e.g., ~/out/) onto some >> arbitrary path. >> >>

Re: How to force keystoreFile and truststoreFile to be absolute paths

Gerald, On 6/21/2016 11:03 AM, Miller, Gerald wrote: > I'm seeing errors from attempts to append uncorrected paths (e.g., > C:\out\) and corrected ones (e.g., ~/out/) onto some arbitrary path. > Assuming a relative path in a case like this makes about as much > sense as using relative branching

RE: How to force keystoreFile and truststoreFile to be absolute paths

Now that I think about it, this is probably a classpath issue. Nice to have when it works, but a royal pain the rest of the time. From: Miller, Gerald Sent: Tuesday, June 21, 2016 2:04 PM To: 'users@tomcat.apache.org' Subject: How to force keystoreFile and

How to force keystoreFile and truststoreFile to be absolute paths

I'm seeing errors from attempts to append uncorrected paths (e.g., C:\out\) and corrected ones (e.g., ~/out/) onto some arbitrary path. Assuming a relative path in a case like this makes about as much sense as using relative branching in non-relocatable code. I've wasted hours trying to get