tm-sdk:svc-scaffold-legacy
Full name:
com.avoka.tm:tm-sdk-maven-plugin:22.4.0:svc-scaffold-legacy
Description:
MOJO class providing "svc-scaffold-legacy" goal
The svc-scaffold-legacy provides a scaffolding task to create a new Legacy Groovy service.
Please note developers should not be creating new Legacy Groovy services as they have a weaker security model.
The svc-scaffold-legacy provides a scaffolding task to create a new Legacy Groovy service.
Please note developers should not be creating new Legacy Groovy services as they have a weaker security model.
Attributes:
- Requires a Maven project to be executed.
- Since version:
22.4.0
.
Required Parameters
Name | Type | Since | Description |
---|---|---|---|
<dir> |
File |
22.4.0 |
The target project directory to create and deploy files to User property is: dir . |
<legacyPackageName> |
String |
22.4.0 |
The package name for the generated Groovy service definition User property is: legacy.package.name . |
<legacyServiceName> |
String |
22.4.0 |
The service name User property is: legacy.service.name . |
<legacyServiceTemplate> |
String |
22.4.0 |
The service template. Must be a supported service definition
template. Supported legacy service definition template: Groovy Delivery Process, Groovy Dynamic Data, Groovy Email Service, Groovy Form Prefill, Groovy Form Saved Processor, Groovy Form Security Filter, Groovy Form Version Selector, Groovy Service, Groovy Job Action, Groovy Job Action Wait, Groovy Job Delivery Wait, Groovy Job Expiry Action, Groovy Job Task Wait, Groovy Render Receipt, Groovy Receipt Number, Groovy Scheduled Service, Groovy Submission Preprocessor, Groovy Submission Completed Processor, Groovy Submission Data Validator, Groovy Task Expiry, Groovy Tracking Number User property is: legacy.service.template . |
Optional Parameters
Name | Type | Since | Description |
---|---|---|---|
<legacyClientCode> |
String |
22.4.0 |
The service Organization client code User property is: legacy.client.code . |
Parameter Details
<dir>
The target project directory to create and deploy files to
- Type:
java.io.File
- Since:
22.4.0
- Required:
Yes
- User Property:
dir
<legacyClientCode>
The service Organization client code
- Type:
java.lang.String
- Since:
22.4.0
- Required:
No
- User Property:
legacy.client.code
<legacyPackageName>
The package name for the generated Groovy service definition
- Type:
java.lang.String
- Since:
22.4.0
- Required:
Yes
- User Property:
legacy.package.name
<legacyServiceName>
The service name
- Type:
java.lang.String
- Since:
22.4.0
- Required:
Yes
- User Property:
legacy.service.name
<legacyServiceTemplate>
The service template. Must be a supported service definition
template.
Supported legacy service definition template:
Groovy Delivery Process, Groovy Dynamic Data, Groovy Email Service, Groovy Form Prefill, Groovy Form Saved Processor, Groovy Form Security Filter, Groovy Form Version Selector, Groovy Service, Groovy Job Action, Groovy Job Action Wait, Groovy Job Delivery Wait, Groovy Job Expiry Action, Groovy Job Task Wait, Groovy Render Receipt, Groovy Receipt Number, Groovy Scheduled Service, Groovy Submission Preprocessor, Groovy Submission Completed Processor, Groovy Submission Data Validator, Groovy Task Expiry, Groovy Tracking Number
Supported legacy service definition template:
Groovy Delivery Process, Groovy Dynamic Data, Groovy Email Service, Groovy Form Prefill, Groovy Form Saved Processor, Groovy Form Security Filter, Groovy Form Version Selector, Groovy Service, Groovy Job Action, Groovy Job Action Wait, Groovy Job Delivery Wait, Groovy Job Expiry Action, Groovy Job Task Wait, Groovy Render Receipt, Groovy Receipt Number, Groovy Scheduled Service, Groovy Submission Preprocessor, Groovy Submission Completed Processor, Groovy Submission Data Validator, Groovy Task Expiry, Groovy Tracking Number
- Type:
java.lang.String
- Since:
22.4.0
- Required:
Yes
- User Property:
legacy.service.template