RE: re: iSeries Projects -- WDSCI-L

I don't know about Vern, but I was hoping it would open up an entire new
view of source members and objects.  Right now if I switch to another filter
and open source members from there, my other source members are still open
from the last filter I worked out of.  Stuff like that would be beneficial,
IMO.

Aaron Bartell

-----Original Message-----
From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx]
Sent: Friday, June 06, 2003 8:30 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] re: iSeries Projects


My understanding is that the purpose of iSeries projects was to allow you 
to work offline.  In other words, pull some source down to your laptop and 
go home or back to your office and work on it.  Then when you reconnect 
later you push it back to build it.  I imagine it could also be used for 
someone that was always connected if they had a large project they were 
going to work on for several days/weeks and preferred to have the source 
on their PC.  But, in general, if you are connected to your system, why 
wouldn't you just use RSE anyway?

Mark








Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/06/2003 09:09 AM
Please respond to Websphere Development Studio Client for iSeries 
 
        To:     Websphere Development Studio Client for iSeries 
<wdsci-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: [WDSCI-L] re: iSeries Projects


Thanks, Diz.

My main issue now is, if I pull something from a location, why is it 
pushed 
somewhere else?

I can see numerous times where source could come from different places - a 

fix could involve both objects in common and specific to a product. A 
project could be set up for the entire product and would automatically 
pull 
from multiple sources. But I'd never want all that source to go somewhere 
else than where I took it from.

The CM products will pull things into a development area, as ACMS and 
TurnOver do - then promote up to QA and integration, and finally 
production 
(I forget TurnOver's versions of these terms as used in ACMS - sorry, 
Mark  ;-)  I had more time with ACMS, although I recommended TurnOver at a 

later job.). I can see this project model working when there is extensive 
software control of where things are.

It seems I'd be better off using a member (maybe object?) filter, adding 
the references to what I need at the time. This'd work OK, I think.

Oh, well, I was hoping for a poor-man's change management system. Sigh!

Now, how about including source from disparate systems - consider a Delphi 

GUI that uses certain iSeries programs - can they all be included under 
one 
umbrella somewhere in WDSC?

Regards

Vern

At 07:27 AM 6/6/2003 -0400, you wrote:
><So, does a project allow you to specify a build program? is this like 
>your "wizard" or "style"? Does this program run in the "associated" 
>library? Are these wizards part of TurnOver or of WDSC?
>
>Later
>
>Vern>

-snip-

>Both of the Program and Command build styles push your source changes 
back 
>to the project's associated library.  But the source can be pulled into 
>the project from any source library on the iSeries.

-snip-


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

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