anchor.diff:  [source,groovy]
   [subs="attributes"]
   ----
  +    publishPlugin {
  +        username = 'ExampleUsername'
  +        password = 'ExamplePassword'
  +    }
  +
       teamcity {
           // Use TeamCity {example-api-version} API
           version = '{example-api-version}'
  
positive.code: :uri-server-descriptor: {uri-teamcity-documentation}/Plugins+Packaging#PluginsPackaging-PluginDescriptor
  :uri-agent-descriptor: {uri-teamcity-documentation}/Plugins+Packaging#PluginsPackaging-PluginDescriptor.1
  :uri-gradle-plugin-portal: https://plugins.gradle.org/plugin/com.github.rodm.teamcity-server
  :plugin-version: 1.0
  :default-api-version: 9.0
  :example-api-version: 8.1
  
  The plugin provides support to {uri-teamcity-extending}[develop TeamCity plugins], creating agent and server side archives, downloading and
  installing a TeamCity server and tasks to deploy, start and stop the server and agent.
  
  image:https://travis-ci.org/rodm/gradle-teamcity-plugin.svg?branch=master["Build Status", link="https://travis-ci.org/rodm/gradle-teamcity-plugin"]
  
negative.code: ### TeamCity Server Plugin
  
  The plugin when applied with the Java Plugin, adds the JetBrains Maven repository and adds the TeamCity server-api and
  tests-support dependencies to the compile and testCompile configurations. If the Java Plugin is not applied the plugin
  provides only the tasks to package and publish the server side plugin archive if a plugin descriptor is defined.
  
  The server plugin can be combined with the agent plugin but not with the Java Plugin.
  
  