<?xml version="1.0" encoding="UTF-8"?><pluginInfo>
  <!--
  
  **author name IS required**
  
  The Author Section is used to give credit to the author of the plugin.
  Name is the only required element/attribute, but feel free to also include your email, 
  website  or bio to allow users of your plugin to praise your work, ask questions 
  or share their use case to help grow your plugin's functionality. 
  -->
  
  <author name="UrbanCode">
    <organization>UrbanCode</organization>
    <email>info@urbancode.com</email>
    <website>http://urbancode.com</website>
    <bio/>
  </author>
  
  <!--
  
  **intergration type IS Required**
  
  The integration type section identifies where the plugin fits into the process
  excepted types are SCM, Build, Artifact, Automation, Deploy 
  
  For example:
  
  The plugin pulls Artifacts from an artifact repository during deployment
  the Type would be "Artifact"
  or 
  The plugin deploys to a middleware server 
  the Type would be "Deploy"
  -->
  
  <integration type="SCM"/>
  
  
  <!-- 
  **source is NOT required**
  
  The source section identifies the location of the plugin source code
  For example 
  https://github.com/...
  -->
  <!--
  <source url=""/>
  -->
  <!-- 
  **license type is NOT required**
  
  If your plugin uses any licensed software please acknowledge it by 
  listing the license type below  
  -->
  <!--
  <licenses>
    <license type=""/>
  </licenses>
  -->
  <!-- 
  **tool-description IS required**
  
  The tool-description section is used to summarize the software 
  the plugin was created to integrate with. 
  
  For example: 
  Apache Ant is a software tool to automate software processes during the build or 
  deployment of an application. Ant uses an propitiatory XML file to define build 
  and/or deployment steps(referred to as targets by ant) . The Ant executable is 
  called to execute the targets in the build.xml.
  -->
  
  <tool-description>IBM's ClearCase software provides tools for supporting software configuration management (SCM) of source code and other software development assets.</tool-description>
  
  <!-- 
  **related-info is NOT required**
  
  The releated-info section is used to define links which may be useful to users of the plugin 
  but don't fall into the release-notes or tool-description section. 
  
  For example: releated-info can be links to pdf documentation, help videos related to plugin setup or the product's
  website.
  
  excepted values for type include: PDF, WEBSITE, VIDEO  
  -->
  
  <related-info>
    <link description="More information available at IBM's website" title="IBM's ClearCase UCM" type="WEBSITE" url="http://www.ibm.com/developerworks/rational/library/836.html"/>
  </related-info>
  <!-- 
  **meta-html in NOT required**
  
  The meta-html section is used define the meta description and the meta keywords of the plugin page.The meta 
  description tag allows you to influence the description of your page in the web crawlers that support the 
  tag The meta keywords tag allows   you to provide additional text for crawler-based search engines to index 
  along with your body copy. 
  
  If multiple keywords are used they must be comma(,) delimited   
  -->  
  
  <meta-html>
    <meta content="" name="description"/>
    <meta content="" name="keywords"/>  
  </meta-html>
    
  <!-- Do not change the release-version, the build process injects it. -->
  <release-version>13.673057</release-version>
  
  <release-notes>
    <!--
      **release-note IS required**
      
      The plugin-version name must match the plugin version found in the plugin.xml file 
      
      The release-note should document the changes, improvements, or bug fixes introduced 
      with the new plugin version 
        
      The release-note may contain text or reference a file in the plugin zip package
      
      For example your release note could be:
      Support for was added for version 10.0 for software X
      or 
      releaseNotes/release1.html (where release1.html contains html formatted version information)
      -->
      
    <release-note plugin-version="1">
Installing this plugin will give you access to the steps listed below. These steps will be available for use when designing a Job. 
    </release-note>
      
    <release-note plugin-version="2">
Update to a newer version of a library for HTTP communication.
    </release-note>
      
    <release-note plugin-version="3">
Fixed the label step to call the correct script. Fixed a bug where the label step would try to create a baseline even when there were no changes.
    </release-note>
      
    <release-note plugin-version="4">
Updated each step to use the viewPath as a working directory when the view creation strategy is set to Use Existing.
Other creation strategies will use the view name as an offset within the current working directory.
    </release-note>
      
    <release-note plugin-version="5">
Fixed a bug with boolean values being stored as strings
    </release-note>
      
    <release-note plugin-version="6">
Removed the vobName property. The value is determined based on the Paths property on the source configuration
    </release-note>
      
    <release-note plugin-version="7">
Updated the plugin to create the offset directory based on the view name or view path. This fixes an issue with the populate step not being able to determine if the view exists
    </release-note>
      
    <release-note plugin-version="8">
Added the -stream option to the mkview command
    </release-note>
      
    <release-note plugin-version="9">
Added new property to append the vob name after the stream name. Fixed bugs with how the view is created and how the checkout step works.
    </release-note>
      
    <release-note plugin-version="10">
Minor fixes to the Cleanup step so it can properly parse the vob name from the Paths property and so it can actually clean up files. Fixes to the Changelog step so it can properly run the lshistory command
    </release-note>
      
    <release-note plugin-version="11">
Added a new property that determines if a populate step should pull from all components within a VOB or use the specified paths to pull specific files
    </release-note>
      
    <release-note plugin-version="12">
Updated the changelog step to fix an infinite loop when parsing comments
    </release-note>

    <release-note plugin-version="13">
Fix a bug where the changelog and quiet period steps were not respecting the view creation strategy
    </release-note>
    
  </release-notes>
</pluginInfo>