RE: Re: iSeries Project

Vern,

In TurnOver we have something called "worklists" which are geared around a 
particular assignment.  These provide subsetting functionality like 
iSeries Projects, but support unlimited libraries and by default work via 
an RSE-style of editing.  We provide an option to create an iSeries 
Project from a worklist.  This will create the iSeries Project and 
populate it with everything on your worklist.  If you have items from 
multiple source libraries, it has to create multiple iSeries Projects.

TurnOver then supplies a build style to the iSeries Project so that when 
you use the build option it hands it back over to TurnOver.  This lets us 
do stuff like add new members you might have created off-line to your 
worklist as well as run our build wizard to build everything.  iSeries 
Projects are extensible via these build styles, but it is up to someone to 
contribute them,  In this case, TurnOver does.  As someone else pointed 
out, it comes with two styles, CL program and command.

Mark






Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/06/2003 01: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 Project


Mark, you've given me stuff to think about. I'll be taking another look. 
Someone once said (Violaine? Phil C.?) that the project is not a 
full-fledged change management tool. It looks as if you all are able to 
take good advantage of it in your product, however.

Consider this scenario -

1. our header files in the same library as C source, both for common 
objects and product-specific objects
2. different libraries for the common and product stuff
3. target library for objects is separate from either of these other 2, 
except modules
    - modules usually in one of the source libraries - not distributed
4. a build program that establishes a compilation environment (lib list, 
etc.) and creates all the objects

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

At 07:30 PM 6/5/2003 -0400, you wrote:

>Vern,
>
>But wouldn't the build just be a "sandbox" type build that you might use
>for some Unit testing before promoting the items to your formal testing
>areas?
>
>Also, the Build in iSeries Projects is somewhat flexible.  With TurnOver 
we
>contribute a "build style" to the project that lets TurnOver do the 
build.
>We have made the whole build process a wizard.  I know you do a lot with 
C.
>Say you had some header files and C modules in your project.  The build
>wizard would not only build those items, but it would (optionally) show 
you
>all of the related objects and build those.  So every module that used
>those header files would be built and every program/service program that
>used those modules would be built etc.
>
>The build is not tied to the library, it is just the default build styles
>that are.  I think you could use the CL build style and then modify the
>program it generates.
>
>Mark
>
>       Subject:    RE: [WDSCI-L] Re: iSeries Project
>Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
>
>Mark
>
>I looked again - the library is also where the builds are run, it says. 
So
>I can't have a separate destination. Now we don't use a full-fledged CM
>product like yours - I've used yours and Aldon's and appreciate their
>benefits. But we have some procedures in place that this model just does
>not fit.
>
>I'm ready to hear more.
>
>Vern


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