I understand the SVN methodology as we use it quite heavily for everything except iSeries source.
I would love to be able to manage my IBM I projects the same way where I simply check out/check in and edit source and run a build process from the repo when it's time to build an end-release. The RDP project stuff falls WAAAY short.
My idea is also that I could rebuild the entire environment from SVN and rebuild a project from the ground up with the repo being the source.
In mental design I have it working correctly, but in my copious free time I haven't had a chance to complete my thoughts into a complete spec.
Still waiting to see the elusive RTC IBM I integration in action. About as easy as getting the Orioles to stay around all summer in my back yard, except at least I've seen the Orioles :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 5
date: Sun, 22 May 2011 11:05:47 -0500
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Tutorial on RDP i Projects ?
Those clients that are using projects do it slightly differently, Richard. They tend to use an offline repository (such as Subversion) and then they check out and commit directly to/from their project folder. The repository is the official location of source code. They use the i source files solely as temporary compilation containers, pushing the source to the i only for compiling and testing. They leave it on the host, but the golden version is in the repository.
The interesting side effect is that you can completely delete the source from your i; you can always rebuild it from the repository.
This is not the IBM-recommended approach. IBM is pushing RTC. I was involved with RTC back at the beginning, but I haven't take a look at it in some time. I have no idea how RTC and projects interact.
Joe
The whole offline source thing seems a bit counterintuitive.
Would be nice to have a way to simply check out a source member copy and work it offline and then commit just like SVN, but it's not quite that nice..
Are you actually using offline projects today ?
If so, can you describe your process.
midrange.com
