|
midrange.com
The articles on this are fairly old, and I haven't tracked them down, but
they say something like the following:
One of the assumptions of iSeries projects is that each developer works in
a separate library (that project's associated library), backed by a team
library in the library list that holds common objects (source files,
display and data files, data areas). This way, each developer can make
changes to their own programs without overwriting the others. From time to
time, one developer from the team will update the team library -- this one
would tend to have the copybook members. You're correct in that if all team
members work in the same library they will collide if their projects
overlap. If you all want to work in the same library, then its best to have
several related projects that don't overlap and have members of the team
push only those that they are working on.
The "push" function for iSeries projects is not a general synchronization
mechanism. There have been requests for this, and it would help to solve
your problem as well.
_______________________
David Dykstal
david_dykstal@xxxxxxxxxx
"Kevin Turner"
<kevin.turner@cor
altree.co.uk> To
Sent by: "Websphere Development Studio
wdsci-l-bounces@m Client for iSeries"
idrange.com <wdsci-l@xxxxxxxxxxxx>
cc
02/07/2006 01:50 Subject
PM Re: [WDSCI-L] Using Eclipse and
Subclipse
Please respond to
Websphere
Development
Studio Client for
iSeries
Sorry for extending this thread still further, but we are still
experiencing some fundamental issues with ISeries Projects. As it stands,
the ISeries Project is very small with only two developers working on the
feature.
This is what happens:
** 2 developers do a "Team/Update" to get the latest version(s) of the
source from the repository. They both get a copybook source member and
various RPGLE modules.
** Developer 1 makes some changes to an RPGLE module and an associated
copybook source member.
** Developer 1 sends a compile to the iSeries. This pushes everything (his
recent changes and everything he received from the "update") down to the
iSeries and compiles.
** Developer 2 then makes some changes to a different RPGLE module.
** Developer 2 sends a compile to the iSeries. This pushes everything (his
recent changes and everything he received from the "update") down to the
iSeries and compiles.
** Developer 2 has now overwritten Developer 1's RPGLE module changes and
copybook source member changes on the iSeries with out-of-date versions
(even though he has made no changes to them).
** Developer 1 changes his RPGLE module again, but not the copybook source
member.
** Developer 1 sends his changes module to the iSeries but this time it
won't compile because Developer 2 overwrote the associated copybook member.
This causes a great deal of confusion. Developer 1 eventually works out the
problem and has to "force" his copybook changes back to the iSeries (even
though he hasn't changed it).
Add a couple more developers to the scenario and its mayhem! Everyone
keeps overwriting each others source.
Does anyone else have this issue and what is the recommended work around?
Maybe we should do a "Push" as soon as we retrieve and "Update" to ensure
that once we start working only our specific changes get sent to the
iSeries.
Any insight gratefully received.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of David Dykstal
Sent: 06 February 2006 23:15
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Using Eclpise and Subclipse
ISeries Project's "push changes" for a project will push all members that
have had their timestamps updated since the last push. It doesn't matter if
they came from the repository or from an edit.
"Push changes" is intended to make the associated library up to date with
your project in WDSC in preparation for a build or a compile. Why push ALL
the changes? Well, you may have changed copy members or file definitions
and those need to be pushed to provide the correct context for a compile or
build. WDSC doesn't have any dependency analysis built into it yet. And,
unfortunately, we haven't put the knobs in place yet to let you turn off
the automatic push for compiles.
The original thought behind the associated library was that this was to be
a scratch library (backed by a team library in the library list) that only
one or two people worked at a time. It seems however, that folks tend to
want to use this as a team library. In that case, the idea that all team
members have to push every change received from the repository is strange
since that results in a lot of unnecessary pushes. Clearly, in this case,
some kind of two-way synchronization that depends on something besides a
timestamp is needed.
These are all great points and I'll enter them into our feedback database.
_______________________
David Dykstal
david_dykstal@xxxxxxxxxx
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.2/251 - Release Date: 04/02/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.2/252 - Release Date: 06/02/2006
"NOTICE: The information in this electronic mail transmission is intended
by CoralTree Systems Ltd for the use of the named individuals or entity to
which it is directed and may contain information that is privileged or
otherwise confidential. If you have received this electronic mail
transmission in error, please delete it from your system without copying or
forwarding it, and notify the sender of the error by reply email or by
telephone, so that the sender's address records can be corrected."
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
