× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/06/2006 04:46:06 PM:

> Yes your assumption of the scenario is correct and yes, you are probably 
right
> as to why it is happening.  The question is - should this be happening? 
It 
> seems a bit odd that 5 team members all update their project in the 
morning 
> and then all simultaneously start pushing identical source down to the 
> iSeries. It is also quite irritating if you have pulled, say, 20 changes 
into 
> your project and then just want to make a small change and compile of 
one 
> source member.  Seems like a bug to me - bit I don't know if this is a 
> Subclipse issue or an Eclipse issue. 

I do not think there is a bug in anything.  Eclipse plays no role in this, 
other than as a host for all of these plugins.  Subclipse sounds like it 
is behaving correctly.  It is the iSeries Projects code from IBM that 
decides what to push and when to push it.  You could call this a bug, but 
I suspect they would call it a design limitation.

Personally, I do not think the idea of using the iSeries Projects feature 
and then storing the source in a PC-style version control system really 
works for iSeries development.  You get the basic functionality you are 
looking for but I do not think that all of the tooling is in place to make 
this work well.  I also do not think as a general solution it would scale 
really well.  Imagine the problem you are facing in a more realistic 
iSeries application with over a thousand source members.  I also do not 
think iSeries Projects themselves were really meant to be used on that 
large of a scale.

In my opinion, iSeries Projects was meant to more solve the problem that 
"I am working on FeatureX" that involves these 10-20 source members.  I 
can group them and work on them in a project.  I suppose I could form a 
small adhoc team and temporarily coordinate our work in a PC-style 
repository like Subversion.  But when the "project/feaure" was complete 
you would throw it away and repeat for the next project.

In order to use the feature on a long term basis, your iSeries Project 
would need to contain all of your source code for your application and 
that is not what it was intended to do.

I think you will get better results from an iSeries-specific solution.

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 thread ...

Replies:

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

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.