<?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: Deployment artifact filenaming? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/deployment-artifact-filenaming/m-p/169637#M123007</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Don't think there is a reasoning behind it. If I do need to make a guess: most of the times, you only have 1 process per deployment (unless you're using subprocesses etc). It makes sense to have the bar named after this process, in case you have multiple processes in your project.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It all depends on your deployment-needs, but most people use deployments with 1 or only a few processes in it… Feel free to rename the file, offcourse &lt;img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Dec 2013 09:25:04 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2013-12-05T09:25:04Z</dc:date>
    <item>
      <title>Deployment artifact filenaming?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deployment-artifact-filenaming/m-p/169636#M123006</link>
      <description>As far as I can tell the file name given to the deployment artifacts .bar or .jar is taken from the first .bpmn file found in the project. Is there any particular rationale to use this and not the project name?</description>
      <pubDate>Wed, 27 Nov 2013 21:25:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deployment-artifact-filenaming/m-p/169636#M123006</guid>
      <dc:creator>aapthorp</dc:creator>
      <dc:date>2013-11-27T21:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment artifact filenaming?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deployment-artifact-filenaming/m-p/169637#M123007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Don't think there is a reasoning behind it. If I do need to make a guess: most of the times, you only have 1 process per deployment (unless you're using subprocesses etc). It makes sense to have the bar named after this process, in case you have multiple processes in your project.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It all depends on your deployment-needs, but most people use deployments with 1 or only a few processes in it… Feel free to rename the file, offcourse &lt;img id="smileywink" class="emoticon emoticon-smileywink" src="https://connect.hyland.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Dec 2013 09:25:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deployment-artifact-filenaming/m-p/169637#M123007</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-12-05T09:25:04Z</dc:date>
    </item>
  </channel>
</rss>

