<?xml version="1.0" encoding="UTF-8"?><!--
- Licensed Materials - Property of IBM Corp.
- IBM UrbanCode Build
- IBM UrbanCode Deploy
- IBM UrbanCode Release
- IBM AnthillPro
- (c) Copyright IBM Corporation 2002, 2016. All Rights Reserved.
-
- U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by
- GSA ADP Schedule Contract with IBM Corp.
--><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="automation"/>


  <!--
  **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>
 Developed by UrbanCode, The File Utility plugin automates folder and file tasks.</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
  -->

  <!--
  **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>48.793720</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)

      To add a new release note add this with a description in it of the changes:
      <release-note plugin-version="10">....</release-note>

      Our automated release process will replace 'LATEST' with the released version.

      If this already exists in the file, then the described changes have not been released yet and
      you should just append to the existing 'LATEST' tag.
      -->

    <release-note plugin-version="10">
      Installing this plugin will give you access to the steps listed below. These steps can be used when designing a component process.
    </release-note>
    <release-note plugin-version="11">
      Add a step for flipping line endings.
    </release-note>
    <release-note plugin-version="12">
      Add an upgrade to upgrade Synchronize Directories step to set default values for overwrite, Preserve In Target Includes, and Preserver In Target Excludes.
    </release-note>
    <release-note plugin-version="13">
      Better handling of special characters in property values and name for Replace Tokens step. This requires uDeploy server version 4.5.2.
    </release-note>
    <release-note plugin-version="14">
      Add a step to create Zip archives.
    </release-note>
    <release-note plugin-version="15">
      Added a step to move files/directories. Added renaming functionality to "Copy Directory".
    </release-note>
    <release-note plugin-version="16">
      Updated Unzip step to allow file patterns in the zip field rather than expecting an explicit file name.
    </release-note>
    <release-note plugin-version="17">
      Performance improvements on move directories step when using default includes and excludes.
    </release-note>
    <release-note plugin-version="18">
      Add a step that can modify XML files using XPath expressions.
    </release-note>
    <release-note plugin-version="19">
      Update the modify XML files using XPath expressions step to allow for attribute insert/update along with XML insertion.
    </release-note>
    <release-note plugin-version="20">
      Update step name capitalization to be consistent and remove excess whitespace and newlines from some step descriptions.
    </release-note>
    <release-note plugin-version="21">
      Add upgrade path to fix component export.
    </release-note>
    <release-note plugin-version="23">
      Added step for retrieving properties from a file.
    </release-note>
    <release-note plugin-version="25">
      Update Replace Tokens step to no-longer require start and end delimiter fields and be able to use an already existing property file specified by Property File Name.
    </release-note>
    <release-note plugin-version="26">
      Update Synchronize Directories to have text area inputs for includes and excludes.
    </release-note>
    <release-note plugin-version="27">
      Updated Sync Dir, Copy Dir, and Move Dir's hint text so that file include and exclude's proper usage is more explicitly explained.
    </release-note>
    <release-note plugin-version="28">
      Updated Update Property File step to be able to take any number of properties defined in scopes like environment, component, etc and include them in the update.
    </release-note>
    <release-note plugin-version="29">
      Added step for retrieving properties from an XML file
    </release-note>
    <release-note plugin-version="31">
      Added Include and Exclude fields to the unzip plugin step, changed a step name and made some spelling and grammar corrections
    </release-note>
    <release-note plugin-version="32">
      Added Destination Directory field to the Update XML File with XPath step, changed a field name
    </release-note>
    <release-note plugin-version="33">
      Update Property File step to have text area inputs for includes and excludes to allow editing multiple property files.
    </release-note>
    <release-note plugin-version="34">
      Modified Untar step to allow wildcards for tarball name.
    </release-note>
    <release-note plugin-version="35">
      Updated Unzip step to use the system default encoding.
    </release-note>
    <release-note plugin-version="36">
      Updated the 'Update XML File with XPath' plugin step to correctly get the encoding from the prolog of the XML Document.
    </release-note>
    <release-note plugin-version="37">
      Updated the 'Update INI File' plugin step. Added option to allow users to add comments to sections. Added an option to give the user a choice between ';' and '#' for comments. The default comment charater will now be ';'. Fixed a bug where sections were deleted if they did not have a property. Multiple comments are allowed but empty lines between comments will not be preserved.
    </release-note>
    <release-note plugin-version="38">
      Added an option to the 'Update Property File' plugin step which causes it to read the properties file using the agent's native encoding or a custom character encoding
    </release-note>
    <release-note plugin-version="39">
      Changed name of the 'Update Property File' step to be 'Update Java Properties File' to clarify that it is used with Java Properties files. Fixed an issue in the 'Update INI File' step where comments at the end of the file would be deleted. Added option to the 'Update INI File' step to allow the user to specify the encoding of the INI file and added an option to let them delete sections from an INI file.

      Fixed APAR PI31431 - the 'Replace Tokens' properties file was not being deleted if the step failed.
    </release-note>
    <release-note plugin-version="40">
      Fixed APAR PI37793 - Update Java Properties File was throwing NullPointerException if property value was empty
    </release-note>
    <release-note plugin-version="41">
      Fix broken upgrades so the plugin can be loaded into servers with older versions of the plugin
    </release-note>
    <release-note plugin-version="42">
      Fixed APAR PI51450 - Update Java Properties File plugin does not create files if they do not exist
    </release-note>
    <release-note plugin-version="43">
      Added RPX dependency and English translations
    </release-note>
    <release-note plugin-version="44">
      Added the ability to specify a file encoding when using Create File
    </release-note>
    <release-note plugin-version="45">
      In the Replace Tokens step, made the Property File Name field not required, create temp property file in working directory if not specified. Rearranged order of other Replace Tokens properties.
    </release-note>
    <release-note plugin-version="46">
      Added the ability to specify a file encoding when using Create .zip File
    </release-note>
    <release-note plugin-version="47">
      Fixed APAR PI62114 - Step Unzip of plugin FileUtils results in garbled extracted files.
    </release-note>
    <release-note plugin-version="48">
      Fix APAR 152489: Added the ability to specify a file encoding when using Replace Tokens step.
    </release-note>
  </release-notes>
</pluginInfo>