Versions Compared

Old Version 14

changes.mady.by.user Ben Hoffman

Saved on

compared with

New Version 15

changes.mady.by.user Ben Hoffman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Generates an artifact jar of checked out objects for deployment. You should 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.

...

Environment/Instance Properties

Property Name

Property Code

Required

Description





  

Project Properties

Property Name

Property Code

Required

Description

MDS Base Object Path

FDMDS_BASE_OBJ_DIR

No

The relative directory path from where MDS objects will be included in generated artifact.

  

Inputs

Input Name

Input Code

Required

Description






Outputs

Output Name

Required

Description




  

Project File Attributes

Attribute Name

Attribute Code

Required

Description


Info

The following properties are Project File Attributes. They are only available on Partial Deploy projects.


Target PathTARGET

Yes

The path in MDS where the file should be placed. Default value is the SCM file path.

Property ReplacementPROPERTY_REPLACEMENTYesWeather or not to perform property replacement on individual files. Defaults to the value of FDMDS_PROPERTY_REPLACEMENT.

...

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:

  

Subversion Example

  • Subversion Folder structure
    • /trunk/namespace/order/order.xsd
    • /trunk/namespace/customer/customer.xsd
  • If you want both of the objects
    • Check out /trunk into empty checkout folder.
    • Set namespace for MDS Base Object Path 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.
  • If you want only customer objects
    • Make sure you only checkout /trunk/namespace/customer folder only as we are only interested in customer objects here.
    • Use namespace/customer as checkout folder as we still want to maintain structure of objects.
    • Set namespace 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 Example

  • Git Folder structure
    • /MDS/namespace/order/order.xsd
    • /MDS/namespace/customer/customer.xsd
  • If you want both of the objects
    • Use /MDS for sparse checkout folders and empty checkout folder.
    • Set /MDS/namespace  as MDS Base Object Path, 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.
  • If you want only customer objects
    • Use /MDS/namespace/customer for sparse checkout folders and empty checkout folder.
    • Set /MDS/namespace  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 sparse folder and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.

...