It's all about the answers!

Ask a question

Template versioning application like Project Area Updater


Stefania Axo (12621513) | asked Oct 13 '10, 7:45 p.m.
is it possible to manage the versioning of process templates?

I am looking for something similar to what the Project Area Updater Tool did for 1.0 to 2.0.
I have my own template that will go trough different stages of releases to different organization. Like myTemplate_1, myTemplate_2, ...myTemplate_n.
I want the organizations who i sent myTemplate to be able to update their existing project areas with the new release of myTemplate, in the same fashion that the Project Area Updater Tool did for scrum and OpenUP from RTC 1.0 to RTC 2.0.

thanks
Stefania

13 answers



permanent link
Marc Towersap (481711) | answered Feb 14 '13, 3:32 p.m.
That is odd.  What I'm hearing is, yes, we can easily create customized templates, but out-of-the-box, there is NO way to make customized templates updateable for project areas that have older versions of those same templates, that instead we have to hack around in the source code?  Good luck figuring it out.  Really?  Really? Doesn't sound like RTC is ready for primetime (on a 4.x release!).  I would expect this feature to be just there, as a default option when saving my own process templates, because why the heck would I NOT want this feature?

Comments
Marc Towersap commented Feb 18 '13, 1:57 p.m.

and the other thing is, I tried downloading the RTC-SDK-4.0.zip (for windows 7), and it's failing for me when I try to extract it, saying it's an invalid zip.

Another question, what the heck is in the SCMtools zip?  I downloaded it, I see some graphical tools (Cairo).  Looking at the readme, it says stuff about a Jazz SCM command line Interpretter (they mispelled interpreter).  Is this just a command line tool for scm work?  If so, maybe one should specify in the downloads section what it is. Is this different than the RTC windows shell integration?  Why isn't it part of the big install of the server-side?


permanent link
SEC Servizi (97123860) | answered Oct 28 '13, 10:30 a.m.
 It seems like this Plain Java Client:
IProcessItemService processClient = (IProcessItemService) repo.getClientLibrary(IProcessItemService.class);
IWorkingCopyManager workingCopyManager = processClient.getWorkingCopyManager();
IProjectAreaWorkingCopy prjAreaFreshCopy = (IProjectAreaWorkingCopy) workingCopyManager.getWorkingCopy(prjArea);
final String xml = ...
prjAreaFreshCopy.getProcessSpecification().set(xml);
prjAreaFreshCopy.save(null);
it is not enough to add new custom attributes to work-items.
@mandrew Any advice?
Thanks in advance. 

permanent link
KB 20 (123) | answered Apr 30 '14, 3:30 p.m.
  Hey guys, I am also trying to post the process config source xml file back to the project and following your examples and some others, I have been getting this error: " com.ibm.team.process.common.service.ProcessDataValidationException: content is not allowed in prolog".

I have edited the file on my local machine and now want to post it back to the project and save it. Any ideas, why I could be getting this error?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.