Symbol:
Function: These commands open the dialog “Include externals”.
Call:
-
Menu bar: “Project SVN”.
-
Context menu: “SVN”
Requirement: An object is selected in the object tree. The external objects are linked below that. If you have selected nothing or the project root directory, then the command “Include externals to project” is available. If you have selected an object, then the command “Include externals” is available.
The same external objects cannot be linked multiple times at different locations in the same project. This leads to problems in CODESYS because of conflicts with the internal identification of the object.
Dialog 'Include externals'
![]() |
URL of the external object that is linked. The object to be linked is versioned and can have sub-objects. External objects are located at another location in the SVN repository than the project. It can even be in another SVN repository. Example: Note: The objects that should be linked below the selected object must have a matching object type. For example, only a task can be linked below the “Task configuration” object. |
|
Opens the dialog “Select revision”. Here you can select a revision. The button is labeled with the currently selected revision:
Note: The dialog provides the same options as the “Revision” group. |
|
Opens the “SVN repository browser” dialog Here you can browse the SVN repository. |
Options for selecting a revision Note: the current valid selection is also displayed in the buttons next to the SVN repository URL. |
|
“HEAD” |
|
“Revision” |
Example: |
“Date” |
Example: |
“Use UTC Time”: |
|
“OK” |
Adds the external object and its sub-objects with the property Example: Note: If the linking fails (for example when adding a device below a task configuration), then the complete operation fails and reverts back. Note: Renaming or moving individual external objects is permitted inly within an external tree, whereby it is not permitted to move the top object. To move a complete tree, you have to remove it and link it to another location. |
“... You should seriously consider using explicit revision numbers in all of your externals definitions. Doing so means that you get to decide when to pull down a different snapshot of external information, and exactly which snapshot to pull. Besides avoiding the surprise of getting changes to third party repositories that you might not have any control over, using explicit revision numbers also means that as you backdate your working copy to a previous revision, your externals definitions will also revert to the way they looked in that previous revision, which in turn means that the external working copies will be updated to match the way they looked back when your repository was at that previous revision. For software projects, this could be the difference between a successful and a failed build of an older snapshot of your complex codebase. ...”
This is cited from:
⮫ http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html).