Merge pull request #72 from anarnold97/MTA-4264-Tags-are-not-accessible-in-SVN-repositories

To be merged for 7.1 - MTA-4264: Tags are inaccessible in SVN repositories

Author: anarnold97

docs/topics/mta-web-adding-applications.adoc

@@ -22,41 +22,45 @@ Before creating an application, set up business services, check tags and tag cat
 . In the *Migration* view, click *Application Inventory*.
 . Click *Create new*.
 . Under *Basic information*, enter the following fields:
-* *Name*: A unique name for the new application.  
+* *Name*: A unique name for the new application.
 * *Description*: A short description of the application (optional).
 * *Business service*: A purpose of the application (optional).
 * *Manual tags*: Software tags that characterize the application (optional, one or more).
-* *Owner*: A registered software owner from the drop-down list (optional). 
+* *Owner*: A registered software owner from the drop-down list (optional).
 * *Contributors*: Contributors from the drop-down list (optional, one or more).
 * *Comments*: Relevant comments on the application (optional).
 
 . Click *Source Code* and enter the following fields:
-// ![](/Tackle2/AddingApps/NewAppSource.png)
 * *Repository type*: *Git* or *Subversion*.
 * *Source repository*: A URL of the repository where the software code is saved.
+** For Subversion: this must be either the URL to the root of the repository or a fully qualified URL which (optionally) includes the branch and nested directory. When fully qualified, the *Branch* and *Root path* must be blank.
 * *Branch*: An application code branch in the repository (optional).
+** For Git: this may be any reference; `commit-hash`, `branch` or `tag`.
+** For Subversion: this may be a fully qualified path to a branch or tag, for example, `branches/stable` or `tags/stable`. This must be blank when the Source repository URL includes the branch.
 * *Root path*: A root path inside the repository for the target application (optional).
+** For Subversion: this must be blank when the Source Repository URL includes the root path.
 
-+ 
-NOTE: If you enter any value in either the Branch or Root path fields, the Source repository field becomes mandatory. 
+
++
+NOTE: If you enter any value in either the Branch or Root path fields, the Source repository field becomes mandatory.
 
 . Optional: Click *Binary* and enter the following fields:
 // ![](/Tackle2/AddingApps/NewAppBinary.png)
 * *Group*: The Maven group for the application artifact.
-* *Artifact*: The Maven artifact for the application. 
+* *Artifact*: The Maven artifact for the application.
 * *Version*: A software version of the application.
 * *Packaging*: The packaging for the application artifact, for example, `JAR`, `WAR`, or `EAR`.
 
-+ 
-NOTE: If you enter any value in any of the Binary section fields, all fields automatically become mandatory. 
++
+NOTE: If you enter any value in any of the Binary section fields, all fields automatically become mandatory.
 
 . Click *Create*. The new application appears in the list of defined applications.
 
 .Automated Tasks
 
 After adding a new application to the *Application Inventory*, you can set your cursor to hover over the application name to see the automated tasks spawned by adding the application. The language discovery task identifies the programming languages in the application. The technology discovery task identifies specific technologies in the application. The tasks automatically add appropriate tags to the application, reducing the effort involved in manually assigning tags to the application. After these tasks are complete, the number of tags added to the application will appear under the *Tags* column. To view the tags:
 
-. Click on the application's row entry. A side pane opens. 
+. Click on the application's row entry. A side pane opens.
 . Click the *Tags* tab. The tags attached to the application are displayed.
 
 You can add additional tags manually as needed. When MTA analyzes the application, it can add additional tags to the application automatically.