On 11/11/14, 2:32 PM, "Christofer Dutz" <christofer.d...@c-ware.de> 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
