Generates an artifact jar (MDSObjects.jar) from exported code. You must checkout or export code from SCM prior to running this operation. Checkout or Export can be easily done if you configure project with Source details.
...
This operation also supports partial build. Partial build creates a build artifact containing file(s) and folder(s) selected on the Project Files tab of a project. When using partial build, the plugin will generate a zip file named {{FD_PROJECT_NAME}}.zip . Note that the structure of this file will match the folder structure from SCM, even if the TARGET attribute is set to a different path. This is so the user can easily change the target and redeploy to MDS to update the file path inside of MDS without having to rebuild the entire project.
Target Properties
...
...
Property Code
...
Required
...
Description
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
MDS Base Object Path |
| No | The relative directory path from where MDS objects will be included in artifact. If you want all files from configured Project Sources including checkout folder, then you can leave this property empty. See Special Considerations below for more details. |
Inputs
...
Input Name
...
Input Code
...
Required
...
Description
...
Output Name
Required
Description
Project File Attributes
| Info |
|---|
The following properties are Project File Attributes. They are only available on Partial Package-Based Deployment projects. |
Attribute Name | Attribute Code | Required | Description |
|---|---|---|---|
Target Path | TARGET | Yes | The path in MDS where the file should be placed. Default value is the SCM file path. |
Property Replacement | PROPERTY_REPLACEMENT | Yes | Whether or not to perform property replacement on individual files. Defaults to the value of FDMDS_PROPERTY_REPLACEMENT. |
...
Git Example
Git Folder structure
/MDS/apps/order/order.xsd/MDS/apps/customer/customer.xsd
If you want both of the objects
Use "
MDS/apps" for sparse checkout folder script. You can use anything for checkout folder script.Use
appsfor MDS Name Space.Leave MDS Base Object Path as empty and all objects will be included in artifact jar file, and it will have proper structure i.e.
order/order.xsdandcustomer/customer.xsd.At deploy time both files will deploy to
appsfolder.This option should work for partial deployment project as well.
If you want only customer objects
Use "
MDS/apps/customer" for sparse checkout folder script. You can use anything for checkout folder script.Leave MDS Base Object Path as empty.
So we have only checked out objects necessary for our project.
Use
apps/customerfor MDS Name Space.
Configurations for sparse folder and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.
...
Subversion Folder structure
/trunk/apps/order/order.xsd/trunk/apps/customer/customer.xsd
If you want both objects
Configure
/trunk/appson Project Source.Option 1
Set Checkout folder and MDS Base Object Path set to Project Name.
Option 2
Do not set anything for Checkout folder and MDS Base Object Path.
For both options, both objects will be included in artifact jar file, and it will have proper structure i.e.
order/order.xsdandcustomer/customer.xsd.Configure namespace on Project Properties as apps.
If you want only customer objects
Make sure you only checkout
/trunk/apps/customerfolder only as we are only interested in customer objects here.Use
apps/customeras checkout folder as we still want to maintain structure of objects.Set
appsasMDS Base Object Path.So, we have only checked out objects necessary for our project, so only customer folder related objects will be included in artifact jar file, but it will still have proper structure, i.e.
customer/customer.xsd.Configure namespace on Project Properties as apps.
Configurations for what should be checked out and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.