...
Perform Steps above to setup to setup a common rules repository.
Create a folder called ProjectRules in the DDB repository.
Add folders to this folder for Forecast, PostForecast, PreForecast, and SqlRules.
Add any project-specific rules to these folders beneath ProjectRules.
In the packager automation script, after the Steps above that copy the common rules into the DDB repository do the following:
Use shell commands to copy the rules from ProjectRules into Rules of the DDB repository.
Code Block cp -r ProjectRules/* Rules
The hammer packager command should be able to run without any modifications. The rules from the common rules repository will be in place in the Rules folder of the project with additional project-specific rules included as well.
...
Perform Steps above to setup to setup a common rules repository.
Create a folder called ProjectRules in the DDB repository.
Add folders to this folder for Forecast, PostForecast, PreForecast, and SqlRules.
For any rules you wish to modify, use the same rule name as what is present in the common rules repository.
Make the necessary code adjustments to the rule.
Place the project-specific rule in the appropriate folder beneath ProjectRules.
In the packager automation script, after the Steps above that copy the common rules into the DDB repository do the following:
Use shell commands to copy the rules from ProjectRules into Rules of the DDB repository.
Code Block cp -r ProjectRules/* Rules
The hammer packager command should be able to run without any modifications. The rules from the common rules repository will be in place in the Rules folder of the project with any project-specific overrides having replaced the common rule.
Tricks for modifying rules:
If you just wish to turn off a rule for a particular project, you can switch the ResponseType from FAIL or WARN to PASS.
Code Block insert(new Response(ResponseType.PASS,errorMessage,drools.getRule().getName()));