Builds JDeveloper project(s) using a deployment profile. This operation can be used to build JAR, WAR files, etc.
You should checkout or export code for entire JDeveloper application from SCM prior to running this operation. Checkout or Export can be easily done if you configure project with Source details. It is good practice to create FlexDeploy project with name that matches JDeveloper application name.
You can also use this operation to build ADF Library JAR files that are useful to share code across various project teams for modular development. Create deployment profile on your project as necessary, commit changes to SCM and run projectBuild plugin operation to execute deployment profile.
...
| Input Name | Input Code | Required | Description | |
|---|---|---|---|---|
| Application(JDev) Source Folder | FDJDEV_INP_APP_SOURCE_FOLDER | No | The folder where source is checked out. Leave it blank if you did not use any sub-folder to checkout/export source. If you have only one JDeveloper Application in export or check out then leave this blank, and plugin will find .jws file automatically. If you are using SubVersion and Source is defined on Project configuration, you can use FDBLD_SVN_SOURCE1_CHECKOUT_FOLDER variable. | |
| JDeveloper Project Name | FDJDEV_INP_PROJECT_NAME | Yes | The folder where source is checked outNo | Project name for which deployment profile will be executed. Leave it blank if you did not use any sub-folder to checkout/export source. If you are using SubVersion and Source is defined on Project configuration, you can use FDBLD_SVN_SOURCE1_CHECKOUT_FOLDER variablewant to all run all project deployment profiles, in which case Project Deployment Profile property is ignored. |
| Project Deployment Profile | FDJDEV_INP_PROJECT_DEPLOY_PROFILE | No | The name of the deployment profile to run, only applies if specific project is provided on JDeveloper Project Name input. You can leave this blank if you want to run all deployment profiles for project. | |
| Application Artifacts Folder | FDJDEV_INP_APP_ARTIFACT_FOLDER | No | Folder name relative to the application where the EAR file artifact files (.war, .jar) will be generated. Default is the deploy folder, if you do not supply any value here. This is default when you create new Application deployment profile as well. | |
| Save Artifacts with Extension(s) | FDJDEV_INP_SAVE_ARTIFACTS_EXTENSIONS | No | Specify comma separated extensions to be copied to artifacts after build. For example: war, jar. (Optional). Select one or more from drop down. | |
| Override File Pattern(s) | FDJDEV_INP_OVERRIDE_FILE_PATTERN | No | Specify {FileName}={OverrideFileName} pattern. Matching files will be replaced by override files and Property replacement logic will be executed as well. For example: , web.xml=fd-web.xml, where web.xml file will be replaced with content from fd-web.xml file and Property Replacement logic will perform property replacement as well. See Property Replacement Support |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
The plugin input FDJDEV_INP_SAVE_ARTIFACTS_EXTENSIONS is used to determine what types of artifacts to copy to the artifacts repository. The files are copied from the folder specified by FDJDEV_INP_APP_ARTIFACT_FOLDER which has a default value of "deploy".
...
You must create an instance for JDeveloper and associate the endpoints where you have JDeveloper installed. You can create more than one instance if you are supporting multiple JDeveloper versions in your environment. For example, JDeveloper 11.1.1.8, JDeveloper 12.1.3 etc. Projects can select a specific JDeveloper instance on the Project Configuration Screen as per what version of JDeveloper each project is using for development.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
...