|
Yes Mark, I am beginning to think that something like that plus reverting to your other suggestion where each developer has an ISeries project that is unique to him/her or a specific task - checking out ONLY the objects they need rather than the whole shooting match. I think my main problem stems from the belief that we could use Eclipse in the same way we use Visual Studio for non-ISeries work - but clearly we cannot since we are all ultimately sharing the same location for compiles etc. -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Phippard Sent: 07 February 2006 20:01 To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Using Eclipse and Subclipse wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/07/2006 02:50:36 PM: > Does anyone else have this issue and what is the recommended work around? I doubt that there are many people that are using iSeries Projects in conjunction with a source repository. Could you reduce the problem a bit by having each developer work in their own library? With a common "integration" library also in the library list? Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
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.
midrange.com
