Page Comparison

...

If your MDS objects are in separate SCM folders, then everything will be easy to build and deploy, but if you have one single SCM folder, but would like to create more than one FlexDeploy projects, you need to utilize MDS Base Object Path and Checkout Folder to control what gets included in artifacts jar file. For example:

...

Git Example

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

...

Subversion Example

• Git Subversion Folder structure
  
  • /MDStrunk/apps/order/order.xsd
  • /MDStrunk/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 apps for MDS Name Space.
  • Leave MDS Base Object Path as empty and all Configure /trunk/apps 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.
  • At deploy time both files will deploy to apps folder.
  • This option should work for partial deployment project as well.
  • Configure namespace on Project Properties as apps.
• If you want only customer objects
  
  • Use "MDSMake sure you only checkout /trunk/apps/customer" for sparse checkout folder script. You can use anything for checkout folder script.Leave customer folder only as we are only interested in customer objects here.
  • Use apps/customer as checkout folder as we still want to maintain structure of objects.
  • Set apps as MDS Base Object Path as 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.Use apps/customer for MDS Name Spacexsd.
  • Configure namespace on Project Properties as apps.
• Configurations for sparse folder what should be checked out and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.