×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




I tend to prefer IBM 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 with, and am able to edit, compile, edit, compile, ... as much as I want.

The real 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 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

-----wdsci-l-bounces@xxxxxxxxxxxx wrote: -----
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
From: David Gibbs
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
Date: 07/29/2011 04:39PM
Subject: Re: [WDSCI-L] Using RDP 8.0 i Projects

On 7/29/2011 3:15 PM, Richard Schoen wrote:
David, your bias is showing. You did promise to be open minded  :-)

I don't see where a bias is involved ... we're not talking about the SVN client project ... we're talking about IBM i project's in RDp.

I think that the SVN project you're looking into should hook into the RSE and *NOT* IBM i Projects, as IBM i Project's isn't a _natural_ way for IBM i developers to work.

IBM i project's present a development model that isn't natural for IBM i developers.  IBM i developers edit, compile, test, edit, compile, test, (repeat until it works).

They don't edit, edit, edit, edit, compile, test, done.

david



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.