Enabling or disabling Gosu compilation

If you know that your Gosu code will generate many compilation errors, then you may want to disable compilation while you fix them. For example, if a PolicyCenter upgrade involves API changes, then you can disable compilation while you make the required changes to your code.

There are several ways to compile Gosu source code files, such as by building the project. When compilation is disabled, explicitly compiling Gosu source files within Studio does not produce .class files. Instead, only the .gs files are copied to the output directory. In addition, when compilation is disabled, Studio always reports an explicit compilation as completing successfully, even when the code contains errors. To detect errors in your code when compilation is disabled, explicitly verify that resource.

When you deploy your application, the .gs files are copied to the server, and the server compiles them as needed. Therefore, when Gosu compilation is disabled, you may see server compilation errors that were not reported when compiling in Studio.

Gosu compilation in Guidewire Studio is enabled by default.

  1. In Guidewire Studio, click File > Settings.
  2. In the Settings dialog, in the navigation list, expand Build, Execution, Deployment, then expand Compiler, and then click Gosu Compiler.
  3. Do the following:
    • To disable Gosu compilation for tests, set Exclude Tests.
    • To disable Gosu compilation for other files, set Disable Local Gosu Compilation. Then set the option to disable it for All Gosu code, or Only Gosu code in PCF files.

See also