Re: NB Platform - running unit tests on multiple machines

2019-05-03 Thread Damian Carey
OK. I *think* I have a solution.

Ant could not pick up the environment variable without some help.

Issue described in
https://stackoverflow.com/questions/17571595/env-java-home-not-found-ant

HTH & YMMV

Answer ...

Step 1. Set Operating System Environment variable 
=
MY_PROJ_PATH = C:/my/path/to/project
(for me, the folder that contains the "build" folder)


Step 2. Tell ANT where environment variables are
-
For each module ... in Important Files > Build Script
add the line ...

before the existing ...



Step 3. Update the test.unit.run.cp.extra
-

javac.source=1.7
test.unit.run.cp.extra=\
${env.QL_PROJ_PATH}/build/cluster/modules/com-acme-impl-nmb1.jar:\
${env.QL_PROJ_PATH}/build/cluster/modules/com-acme-nmb2.jar:



On Sat, 4 May 2019 at 13:04, Tushar Joshi  wrote:

> Many years ago (10+?) I used a relative path, but that is not good enough
>> because the relative path is different depending on if you are running unit
>> tests for an individual module, or for the whole module suite.
>>
>> Any suggestions would be most appreciated.
>>
>
> I would check if I can use environmental variables in the file and try
> using something like $PROJECT_HOME before all my paths, so it can be
> changed without changing the file.  I have not tried it but may be worth a
> try.
>
> with regards
> Tushar
>


Re: NB Platform - running unit tests on multiple machines

2019-05-03 Thread Tushar Joshi
>
> Many years ago (10+?) I used a relative path, but that is not good enough
> because the relative path is different depending on if you are running unit
> tests for an individual module, or for the whole module suite.
>
> Any suggestions would be most appreciated.
>

I would check if I can use environmental variables in the file and try
using something like $PROJECT_HOME before all my paths, so it can be
changed without changing the file.  I have not tried it but may be worth a
try.

with regards
Tushar