<?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: How to call the specific version of a routine in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308729#M80023</link>
    <description>Not sure about the use case of different trunks. But I always recommend to have 1 trunk and do all development in the trunk. You will tag your project as you go. Hence at any point in time you can go back to a tagged version of the project.
&lt;BR /&gt;
&lt;BR /&gt;You will build your jobs binaries from a tagged version. Hence your actual job binaries only change when you recompile the job. If you never recompile a job, and you have the binaries in Nexus, then you are safe. Nothing to worry about because each job binary is independent of each other?</description>
    <pubDate>Tue, 04 Jul 2017 21:41:14 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-07-04T21:41:14Z</dc:date>
    <item>
      <title>How to call the specific version of a routine</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308726#M80020</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm trying to upgrade some function in a routine that's available in a shared trunk in Talend, say "routine 0.1" in trunk "shared_trunk".&lt;/P&gt;
&lt;P&gt;I've exported then imported the routine in my personal workspace repository and upgraded the version, now I have "routine 0.2" in trunk "my_local_trunk".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I compile a job using a new public method only present in "routine 0.2", I've some errors because the new method "doesn't exists".&lt;/P&gt;
&lt;P&gt;How may I precise which routine to use in a job ?&lt;/P&gt;
&lt;P&gt;Talend seems to automatically calling the one in "shared_trunk" (the older).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestion as to where I'm doing something wrong ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks a lot for your suggestions,&lt;/P&gt;
&lt;P&gt;Ema&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jul 2017 14:06:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308726#M80020</guid>
      <dc:creator>Ema_fr</dc:creator>
      <dc:date>2017-07-03T14:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to call the specific version of a routine</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308727#M80021</link>
      <description>&lt;P&gt;Are you using SVN? &amp;nbsp;Are you using Talend subscription with SVN? &amp;nbsp;Keep it simple, merge the routine. &amp;nbsp;Adding a new method won't break the old code as long as the method is independent of the other methods in there. &amp;nbsp;Remember methods in routine are static.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jul 2017 16:49:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308727#M80021</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-07-03T16:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to call the specific version of a routine</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308728#M80022</link>
      <description>&lt;P&gt;Hi !&lt;/P&gt; 
&lt;P&gt;Thank you for your answer.&lt;/P&gt; 
&lt;P&gt;Yes we're using SVN. I missed to detail that "shared_trunk" is only readable for me.&lt;/P&gt; 
&lt;P&gt;I'll have to ask another team for a deployment of my new routine version without having being able to test it.&lt;/P&gt; 
&lt;P&gt;Not really comfortable.&lt;/P&gt; 
&lt;P&gt;Anyway, I will give it another name to test it before deployment and after will have to modify again the jobs impacted by the new method.&lt;/P&gt; 
&lt;P&gt;Bye,&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jul 2017 09:12:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308728#M80022</guid>
      <dc:creator>Ema_fr</dc:creator>
      <dc:date>2017-07-04T09:12:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to call the specific version of a routine</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308729#M80023</link>
      <description>Not sure about the use case of different trunks. But I always recommend to have 1 trunk and do all development in the trunk. You will tag your project as you go. Hence at any point in time you can go back to a tagged version of the project.
&lt;BR /&gt;
&lt;BR /&gt;You will build your jobs binaries from a tagged version. Hence your actual job binaries only change when you recompile the job. If you never recompile a job, and you have the binaries in Nexus, then you are safe. Nothing to worry about because each job binary is independent of each other?</description>
      <pubDate>Tue, 04 Jul 2017 21:41:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308729#M80023</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-07-04T21:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: How to call the specific version of a routine</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308730#M80024</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thank you for your time in this matter.&lt;/P&gt;&lt;P&gt;I didn't have a choice about how many trunks we have to use.&lt;/P&gt;&lt;P&gt;Anyway, I followed your suggestion and created a specific new routine for my jobs that will be deployed with them.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Ema&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2017 09:42:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-call-the-specific-version-of-a-routine/m-p/2308730#M80024</guid>
      <dc:creator>Ema_fr</dc:creator>
      <dc:date>2017-07-26T09:42:57Z</dc:date>
    </item>
  </channel>
</rss>

