Re: Using RDP 8.0 i Projects

Install the SVN Team provider, right click on your i project, select Team/Share Project/SVN and you're golden.

RDP 8.0 is hooked up to SVN and ready to roll.
This could make writing a specialized SVN client redundant and unnecessary.

You can easily push and pull IBM i source members for compiling at will as well as objects that you want to version control in SVN.

Probably not as cool as MKS and others, but this could work nicely for those who don't have the cash to buy a full blown source/application management suite.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxx>
Web Site: http://www.rjssoftware.com<http://www.rjssoftware.com/>
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
---------------------------------------------------------------------------------------------
I tend to prefer IBM<http://archive.midrange.com/wdsci-l/201107/msg00142.html> i projects over RSE because the filtering is easier to use. I create a new project, choose a few sources that I want to work<http://archive.midrange.com/wdsci-l/201107/msg00142.html> with, and am able to edit, compile, edit, compile, ... as much as I want.

The real<http://archive.midrange.com/wdsci-l/201107/msg00142.html> issue for source control is this, I have not been able to determine how that would work in an SVN environment where the entire application<http://archive.midrange.com/wdsci-l/201107/msg00142.html> is in the project. I want to just check out a few objects into my project and work exclusively with those, then check them back in. Not sure if RTC works that way or not, but I don't see using SVN due to the sheer size of the applications I work on.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx