Re: Subversion

iSeries Projects can provide the bridge between Subversion and the i5/OS
native QSYS file system. Each iSeries project gets associated with a
library and the project can download / upload members from that library.
The members stored in the iSeries projects are stream based files encoded
in UTF8 (as opposed to record-based EBCDIC on the i5/OS side). The
iSeries project handles the conversion between the two. So there's no
need to use the IFS. And you can use the regular Eclipse subversion
client to sync between subversion and the iSeries project.

Although I haven't tried this, one person on the team could use Subversion
and WDSC while others continue to use SEU / PDM (although I'm not sure I
would recommend this). You would have to treat the copy of the source in
the i5/OS library as the "master copy" and basically use Subversion just
to track changes to the source member (normally the copy in subversion
would be considered the "master" copy). Before you modify the source in
the iSeries project you would have to first retrieve the latest copy from
the library, make your modifications in the iSeries project then upload
the changes to both the i5/OS library and Subversion (Subversion would
detect all changes (both yours and everyone else's) since the last time
you did this).

Warning: the one warning here is that while you edit the file in an
iSeries project it is not locked in the library like it is when editing
with SEU or the RSE. So someone could make changes while you are making
yours. iSeries projects will detect this on the upload and warn you.

Hope this helps clarify things a bit.

Don Yantzi
Technical Lead
WebSphere Development Studio Client for iSeries
IBM Toronto Lab





Buck <kc2hiz@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
04/03/2007 11:17 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
wdsci-l@xxxxxxxxxxxx
cc

Subject
Re: [WDSCI-L] Subversion

The problem of stream file vs. SRCF is
what keeps me from playing with it.

Use it for your own personal tools, like a particular service program
and it's constituent modules. That way you won't interfere with the
other developers in your group's ability to look at production source.

One idea that's crossed my mind is
writing some sort of utility
that converts the SRCF version
to a stream file and back again
at the appropriate times.

Wouldn't CPYxxSTMF work? I haven't tried at all, but couldn't one put
that in the builder of your iSeries Project?