RE: [WDSCI-L] Re: iSeries Project

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

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