<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: file system deployment target implementation in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/file-system-deployment-target-implementation/m-p/126286#M88873</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Never fear!!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This was the case with 2.1.1E and earlier releases.&amp;nbsp; With our upcoming 2.2 Enterprise this December, this restriction (along with numerous others!) has been lifted.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For details on the very significant deployment enhancements (we think they'll be a sleeper hit) in our upcoming 2.2, please refer to our wiki:&amp;nbsp; &lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/New_Deployment_Requirements" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/New_Deployment_Requirements&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers!&amp;nbsp; This stuff is 80% complete and available for checkout for enterprise subscription customers on the V2.2 branch.&amp;nbsp; I am really psyched about these upcoming changes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Nov 2007 01:22:42 GMT</pubDate>
    <dc:creator>kvc</dc:creator>
    <dc:date>2007-11-23T01:22:42Z</dc:date>
    <item>
      <title>file system deployment target implementation</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/file-system-deployment-target-implementation/m-p/126285#M88872</link>
      <description>I found that the default deployment target is hard coded into the AVMDeploySnapshotAction, so even though the deployment receiver is capable of distinguishing between several deployment targets, this feature is not actually being used.I assume this is a bit of functionality that will eventually be i</description>
      <pubDate>Sun, 28 Oct 2007 14:52:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/file-system-deployment-target-implementation/m-p/126285#M88872</guid>
      <dc:creator>salbanese</dc:creator>
      <dc:date>2007-10-28T14:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: file system deployment target implementation</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/file-system-deployment-target-implementation/m-p/126286#M88873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Never fear!!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This was the case with 2.1.1E and earlier releases.&amp;nbsp; With our upcoming 2.2 Enterprise this December, this restriction (along with numerous others!) has been lifted.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For details on the very significant deployment enhancements (we think they'll be a sleeper hit) in our upcoming 2.2, please refer to our wiki:&amp;nbsp; &lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/New_Deployment_Requirements" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/New_Deployment_Requirements&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers!&amp;nbsp; This stuff is 80% complete and available for checkout for enterprise subscription customers on the V2.2 branch.&amp;nbsp; I am really psyched about these upcoming changes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2007 01:22:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/file-system-deployment-target-implementation/m-p/126286#M88873</guid>
      <dc:creator>kvc</dc:creator>
      <dc:date>2007-11-23T01:22:42Z</dc:date>
    </item>
  </channel>
</rss>

