Mmm. Interesting. I 'll check that out as an example for tagging the
source members for build. I would want to make a similar usage for CL or
RPG OR DDS or whatever.
Ultimately my initial goal is an easy environment where I can
code/compile/checkout/checkin from either WDSC or SEU/PDM.
Blowing SVN integration out into a full blown change management is not
the goal.
I've definitely received a lot of good input from this group so far
though :-)
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: 6
date: Fri, 14 May 2010 22:31:32 +0200
from: Arco Simonse <arco400@xxxxxxxxx>
subject: Re: Subversion and RPG source change management
I fully agree on that. Do not merge the things. But Richard, if you are
looking for a good and easy to use build system, did you have a look to
Scott Klement's BUILD utility? I do use it, and it is a very handy tool.
You
can add your build instructions to the RPG source, and can use
replacement
variables, so that you can even use it from within WDSC / RDI.
Regards,
-Arco
2010/5/14 jim@xxxxxxx <jim@xxxxxxx>
So, it sounds like MKS Implementer is a source version control system
as
well as an integrated build system. That's not what SVN is. There is
no
doubt that I see the value in the combination, my point is just to
keep SVN
what it is and not add on other things that make it IBMi specific.
midrange.com
