Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-build-dev] The difference between "assemble" and "package"



On 2/28/07, Andrew Niefer <aniefer@xxxxxxxxxx> wrote:

Barrie,
Essentially, the assemble is collecting the pieces that were built and package is collecting the binary pieces.  The specific reasons for this are likely lost in antiquity :)
However, note that the package only runs if the property runPackager is set, so it is possible to only collect the built pieces.
As well, the package is used by the packager.xml script to repackage previously built zips.

I can't remember if there are any issues with only doing the zip on the package.  Take a look at the generateTarGZTasks and generateGZipTarget..  Notice that the GZip target when assembling only runs if the runPackager property is not set.
You could make the zipping during assemble conditional on the packager not running.  The only issue would be having the assemble fileset available when we are generating for package.

From what I can tell assemble and package are only used in a product build.
Building plugins or features does not use these files (even though they may get created by pde).

From this I think I can move any archiving steps out of assemble and into package, as long as I can get the assemble fileset available when running package.

Back to the top