Just to be sure, I cleaned the third-party downloads in my local repository and ran ant all. The file ended up in the correct location, as it had when I originally tested my change. This seems to confirm that the 0.7.0 binary release was built using cached downloads, which were out of date.
To avoid this issue in the future, whichever ant target is used to create a binary release should probably clean everything first. Another potential issue is that someone might modify their downloaded files to test something locally and forget to revert them. In other words, local modifications could end up in a binary release without any kind of warning. If the full binary release build forced a clean and re-downloaded dependencies, that would handle both issues. Can we update the binary release of 0.7.0? Or do we need to do a 0.7.1? As far as I can tell, the source bits are fine because the downloads are part of building from source. - Josh On Thu, Sep 8, 2016 at 3:15 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: > The file js/lib/google/closure-library/closure/goog/bootstrap/nodejs.js > is missing from 0.7.0. This file is required to run debug builds produced > by asnodec with Node.js. Release builds aren't broken, but this still isn't > good. > > At some point, flex-asjs started using a subset of GCL, and this file was > accidentally omitted when the list of files to keep was created in > frameworks/downloads.xml. No big deal at the time. I added it to the list > back in July. I assumed a full release build would re-download all > dependencies just to be sure nothing was stale, but I guess maybe it still > uses cached downloads? > > - Josh > > > On Mon, Sep 5, 2016 at 7:39 AM, Alex Harui <aha...@adobe.com> wrote: > >> This is the discussion thread. >> >> >> Thanks, >> Alex Harui >> > >
