On 12/18/13 3:08 PM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote:
>Sorry Alex, I missed you proposition in the last email (this interleaved >multithreaded discussions are a real pain...) > >> Right now, I'm thinking of: >> 1) adding a pixelbender.xml file with a main target that does the >> compile, a clean target that deletes the PBJ and a copy target that >> copies the PBJs into place in the sdk tree. >> 2) add more to the release notes that point you to this xml file >> 3) Separate NOTICE >> 4) tagging flex-sdk repo >> 5) Add git location to README (actually describe how this is a subset >> of >> flex-sdk) >> >> You'll still use release-pixelbender from the main build.xml to create >> the package. > > >I don't understand the steps. >You say that the new "pixel-bender.xml" does the compile and copies the >PBJ into the SDK trees. >What's the difference with the release-pixelbender that will create the >package. > >Does it mean there are two ways of compiling the PBK? One to make the PB >package, and another one directly inside the SDK, like it works currently >? Our build scripts for flex-sdk, flex-falcon, and flex-asjs have a "main" target that compiles the sources, and a separate "release" target that creates the artifacts for the release by compressing the source files. I'm proposing that the pixelbender.xml only contains the "main" target as the release policy only seems to require instructions on how to compile the source, not necessarily create a release. The release-pixelbender target will remain in the main build.xml -Alex
