Build jdk8-b100 with custom cacerts file and java compiler

[matchew]

Thanks. How about build number. Setting variable BUILD_NUMBER does to have
any effect - b00 is taken by default.

Thanks in advance
--
Mateusz


2013/7/31 David Holmes <david.holmes at oracle.com>

> On 31/07/2013 6:46 PM, matchew wrote:
>
>> Hey All,
>>
>> I try to build above version. Since i want to provide custom cacert file
>> as
>> well as java compiler I set this env variables (that is how it worked for
>> 6
>> & 7):
>>
>> export ALT_BOOTDIR=[JAVA_COMPILER_**DIR]
>> export ALT_CACERTS_FILE=[CUSTOM_**CACERTS_FILE]
>>
>> Configure script passes and proper java compiler is taken (i have
>> specified
>> java7 / default on my box is java6), but got this warning anyway:
>>
>> WARNING: You have old-style ALT_ environment variables set.
>> These are not respected, and will be ignored. It is recommended
>> that you clean your environment. The following variables are set:
>> ALT_BOOTDIR=/usr/lib/jvm/java-**7-openjdk-amd64
>> ALT_CACERTS_FILE=/etc/ssl/**certs/java/cacerts
>>
>
> sh configure --help
>
> shows:
>
>  --with-cacerts-file     specify alternative cacerts file
>  --with-boot-jdk         path to Boot JDK (used to bootstrap build)
> [probed]
>
> Cheers,
> David
> ------
>
>
>
>
>> WARNING: You have the following ALT_ variables set:
>> ALT_CACERTS_FILE=/etc/ssl/**certs/java/cacerts
>> ALT_BOOTDIR=/usr/lib/jvm/java-**7-openjdk-amd64
>> ALT_ variables are deprecated and will be ignored. Please clean your
>> environment.
>>
>> If these variables are deprecated and ignored how is it possible that
>> java-7 was used for the compilation instead of default one? Anyway to
>> build
>> process continues and will check if cacert file was included. If not, what
>> is the alternative way to provide it?
>>
>> Best Regards
>> --
>> Mateusz
>>
>>