Ability to compile and test without having to save to $cclsource

[chvarunkumar1994]

For this plugin to compile or run unit tests in non-development domains (where most dba users are not allowed to save to $cclsource), users should still be able to compile files and test them without having to save them to $cclsource. It would be more meaningful if the save operation to $cclsource is performed only during a maven install.

Consider an application like DiscernVisualDeveloper.exe, that allows users to compile/build files without saving it to $cclsource.

[chvarunkumar1994]

How about we save the files to $CCLUSERDIR during a compile?

[feckertson]

1. Pull requests are welcomed.
   2, Why perform development operations (running unit tests) in a non-development domain?
2. I imagine more is desired than has been stated. Suppose a project contains X.inc and Y.prg which includes X.inc via %i cclsource:X.inc. If this request were satisfied, then the file X.inc would not get uploaded to cclsource so the wrong file would be included when compiling Y.prg.

There could be a couple of ways to go about this request: (1) use configuration to override the environment settings that get read from the back end or (2) use configuration to alter the landing locations for uploaded files.

(2) is desirable because landing locations are currently decided only by file extension and all files with an unhandled extension end up in cer_install which is not the right place for a csv or xml that exists only to provide data for a unit test.

Sometime back I had the idea to handle (2) by supporting subfolders of the resource folders and let the names of those subfolders (cer_temp, ccluserdir, etc.) dictate where their contained resources land. This idea does not address what is being asked for, however, because it only operates on the resources directories and it always puts specific files in specific places. This request involves the ccl directories and wants a file's landing location to flex based on the current operation.

ccluint-framework does support having the unit tests in any directory, but ccl-maven-plugin is still calling the framework via its original API (cclut_execute_test_case) which unlike cclut_execute_test_case_file requires the tests to reside in cclsource.

[feckertson]

Testing shouldn't be done in protected domains, but there is merit to this request from the perspective that client custom code should land in $CUST_SCRIPT rather than $CCLSOURCE.

[feckertson]

PR #38 (ccl-maven-plugin 3.3) provides the ability to compile. The ability to test will require additional work.