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. 

Environment/Instance Properties

Project Properties

Inputs

Outputs

Project File Attributes

...

• Subversion Folder structure
  
  • /trunk/namespaceapps/order/order.xsd
  • /trunk/namespaceapps/customer/customer.xsd
• If you want both objects
  • Configure /trunk/namespaceapps on 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.xsd and customer/customer.xsd.
  • Configure namespace on Project Properties.
• If you want only customer objects
  
  • Make sure you only checkout /trunk/namespaceapps/customer folder only as we are only interested in customer objects here.
  • Use namespaceapps/customer as checkout folder as we still want to maintain structure of objects.
  • Set namespace as  apps as MDS 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.
• 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.

...

• Git Folder structure
  
  • /MDS/namespaceapps/order/order.xsd
  • /MDS/namespaceapps/customer/customer.xsd
• If you want both of the objects
  • Use "MDS for sparse checkout folders and empty checkout folder.Set MDS/namespace  as /apps" for sparse checkout folder script. You can use anything for checkout folder script.
  • Use apps for 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.xsd and customer/customer.xsd.
  • At deploy time both files will deploy to apps folder.
  • This option should work for partial deployment project as well.
• If you want only customer objects
  
  • Use "MDS/namespaceapps/customer for " for sparse checkout folders and empty folder script. You can use anything for checkout folder script.
  • Set Leave MDS /namespace  as MDS Base Object Pathas empty.
  • 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.
  • Use apps/customer for 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.