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".
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".
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".
How may I precise which routine to use in a job ?
Talend seems to automatically calling the one in "shared_trunk" (the older).
Any suggestion as to where I'm doing something wrong ?
Are you using SVN? Are you using Talend subscription with SVN? Keep it simple, merge the routine. Adding a new method won't break the old code as long as the method is independent of the other methods in there. Remember methods in routine are static.
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.
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?
