Full name:
com.betfair.cougar:cougar-codegen-plugin:3.3-SNAPSHOT:process
Description:
A gotcha exists when accessing IDDs as resources. Since the IDDs are not required at run-time, it would make sense to include the relevant IDD project (jar) as a plugin dependency (ie. in project/plugins/plugin/dependencies as opposed to a project dependency of project/dependencies). You can do this unless your service is built as part of a larger project tree, in which multiple services are built. Maven resolves dependencies for the plugin once, so you can't have projectA relying on projectA-idd and project B relying on projectB-idd respectively - you end up with both projects relying on (say) projectA-idd. To work around this, you have to include the IDD as part of the project dependencies.
TODO If there's an easy way to fix this, we should do so (maven-savvy volunteers welcome)
Attributes:
Name | Type | Since | Description |
---|---|---|---|
services | Service[] | - | name of service. |
Name | Type | Since | Description |
---|---|---|---|
baseDir | String | - | the base directory of the project Default value is: ${basedir}. |
client | boolean | - | If set to true, generate a client version of generated code. |
iddAsResource | boolean | - | Read IDDs and files from the file system (as opposed to as
resources). Use as transition for existing services, and also as a
way to make writing/testing new services a bit simpler. |
legacyExceptionParamValidation | boolean | - | Legacy mode exception validation. Allows for an exception parameter
to be called message. Note this is a nuisance as it obfuscates
conventional exception class behaviour, so this method of operation
should be phased out |
offline | boolean | - | Either mvn -o or in settings.xml User property is: settings.offline. |
server | boolean | - | If set to true, generate a server version of generated code. |
legacyExceptionParamValidation: