Yeah ... I was afraid of that. Perhaps I could whip up a mechanism. I would strongly suggest not to expect our users to follow any form of documentation. >From my experience giving support for Flexmojos is simply that they won't read >it. I bet they even woudln't read stuff, even if the text was written in big, fat, blinking neonlights :-(
That's why I try to make stuff work without expecting the user to follow any documentation. I just got Falcon to dump resources to the bin/js-debug dir using the Reflection tool. I'll invest a few hours to code a manual replacement for that somehow. Then we won't have to bother with any license crap. Chris ________________________________________ Von: Alex Harui <[email protected]> Gesendet: Dienstag, 11. November 2014 23:45 An: [email protected] Betreff: Re: AW: AW: AW: AW: AW: [FLEX-JS] Streamlining the packaging On 11/11/14, 2:32 PM, "Christofer Dutz" <[email protected]> wrote: >In order to automatically download the closure-library, a maven >dependency is added to the corresponding jar file available at >Maven-Central. This is not extracted to the filesystem, but is available >to the compiler as static resources in the Java classpath. In order to >write these resources to the bin/js-debug directory, I need to select >these parts from the classpath and separate these from the rest and have >the recourses written to disk. > >Hope this explains things a little better. OK, I get it now. Is there a reason we can’t or shouldn't extract to the file system? Are there other alternatives like making sure the Closure jar is downloaded to a known location and/or has a particular name? I would prefer to not have Apache Flex releases use code with licenses that have “bad” words in it, which appears to be the case for the https://code.google.com/p/reflections/ library. I would not like the Installer to have to offer up those bad words for approval by the customer. And, if we decide to bundle that jar some day, our LICENSE file will have to have those same bad words in it. -Alex
