Typically, I use the term "build process", as the process a developer uses to create their own local development environment. A "manufacturing process" is one that gets the project ready for other people to use. Back in the day when products were distributed via CDs and floppies. The manufacturing process involved getting the system built but also incorporating documentation, creating an installer, burning disks.
I think we are on the same page with what will be in the distribution file. Thanks for the feedback, Bob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Cooper Sent: Sunday, January 21, 2007 3:16 PM To: [email protected] Subject: Re: Manufacturing Checkin On 1/21/07, Bob Buffone <[EMAIL PROTECTED]> wrote: > > Hello Everyone, > > Just checked in the manufacturing process that will create a zip and > tarball for a sample application. Manufacturing process? That's a term I've never come across for a software project before. ;-) Is that the same as a build process? How much of the instructions on the wiki still apply, and how much needs updating? I'm thinking of the "getting started" instructions that begin here: http://wiki.apache.org/incubator/xap We do need to create a distro if we are going to release soon. My > suggestion for the content of the distro is follows: > > -docs > - documentation > -samples > - samples people could use as see different aspects of Xap -codebase > - file from the codebase directory in -dist > - contains a zip and tarbar of a basic applications developers could > use to get started Maybe it's just a terminology difference, but I'm a little confused here. You refer to 'dist' as "basic applications developers could use to get started", but doesn't that make them samples? I would expect 'dist' to contain the libraries I want to include with my own XAP application, and nothing else, but you seem to refer to that as 'codebase'. I would expect 'codebase' to be an unpackaged copy of the source files - that is, the input to the build process. So I guess I would expect to see: - docs - what you said ;-) - samples - any and all samples built with XAP - source - a copy of the source tree, that can be used to rebuild what is in 'dist' - dist - the distributable libraries, ready to drop into my own XAP application Does that make sense? Is there something I'm missing? (Entirely likely...) -- Martin Cooper README > LICENSE > > Thoughts??? > > One other thing, It was sugested the we create a maven process for Xap. > Not having done this in before; I was wondering if there were some > maven mavens out there in Xap land that could help? > > Bob (Buffone) > >
