Date: Fri, 29 Mar 2024 00:57:24 +0000 (UTC) Message-ID: <1311108214.5.1711673844844@009434f3664c> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4_1095981961.1711673844842" ------=_Part_4_1095981961.1711673844842 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The following folder structure is recommended for Source Control= (SVN, GIT, TFVC, CVS etc). You can follow a different structure than this,= but you will need the * Source Directory properties at th= e FlexDeploy project level to make sure the files are processed correctly. = For example, if you put Java code in a different folder, just update the&nb= sp;EBS Java Root Source Directory property on your project= to the folder name where you are storing Java files.
See below some examples of Source Control folder structure and FlexDeplo= y project organization. These are just some of the recommendations, as ther= e are numerous combinations possible.
Note that each FlexDeploy project typically deploys customizations to on= e EBS TOP. You could have files in FlexDeploy Project that deploy to multip= le EBS TOP but that would require updating various properties manually.
Source Control Structure | FlexDeploy Project Setup |
---|---|
This is most common Source Control Folder structure. There is a folder f= or custom top and sub-folders for types of files.
|
|
In this Source Control setup we have created one folder for each extensi= on which will contain files developed for that specific extension. It is im= portant to note that the folder structure under each extension has folders = like cp_sql, sql, import, workflows, publisher etc. to identify specific fi= les. The workflows folder can hold both wft and wfx files. Each extension folder will be used to create new FlexDeploy project.
|
Application - XXAP
|