Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
One of the 15 or so JavaScript files I’m combining using the Google Closure Compiler contains the tag @license WTFPL in one of its comments.
As a result, the Closure Compiler labels our entire set of JavaScript as if it were all licensed under WTFPL.
Obviously this is undesirable – even if just because we can’t relicense much of this code under WTFPL. How can I turn this off?
I’ve found re-running the closure compiler on the compiled output will get rid of the comment block containing the license.
Not sure if this would be desired in your case, but in mine (minifying a set of jQuery Tools scripts) it worked well and I didn’t need any other manipulation.