|
I just used the merge source function for the first time.
I had to fix a bug on a programme currently undergoing modifications. This meant that there were 3 versions of the RPG source :
The version in production, a version that a developper is currently working on and my version.
I needed to update the production version and then copy my modifications in the other developper's version.
To merge my modifications am I right in saying you need to download the two sources into an iSeries project?
Anyway that's how I did it, then hit the button to insert all the modifications. That was the production library version taken care of. I was very impressed. I even found it hard to believe. So I uploaded the modified (merged) source and compared it again with the version on the i5. I guess I'll just have to trust it!
I then wanted to do the same with the other developper's version. The compare took a long time and I got the message that there were too many differences. It said to ignore the spaces or analyze separately the structures. I see in the preferences under workbench/ comparaison I can select ignore the spaces but I don't think that's going to make much difference. How do I analyze only parts of the source ?
Now I have to go through all my modifications using the date and insert them into the other source manually. It is rather delicate.
Any suggestions ?
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.