NO Access to compiler.jar on the Latest Release 20160713.0.0
yu-ahmed opened this issue · comments
Is there a specific reason why you renamed the compiler.jar ?
I cant access the compiler.jar cause its renamed into a prefixed version with a version number at the end of the name.
Can you please rename the file into compiler.jar back?
We didn't rename the compiler.jar. Are you sure you are using the correct package? Our package is named google-closure-compiler. See #25 - we have had reports that other packages not maintained by the Closure-Compiler team may be broken.
If you're getting the compiler from dl.google.com, we did rename it. This is in the release notes and was announced at https://groups.google.com/forum/#!topic/closure-compiler-discuss/7VyMemWKqdg
If you're getting it from the official npm package, everything should be the same as before, as Chad says.
I missed this. Why did we rename it? That seems like it would cause folks
unnecessary pain.
On Jul 20, 2016 8:33 AM, "Tyler Breisacher" notifications@github.com
wrote:
If you're getting the compiler from dl.google.com, we did rename it. This
is in the release notes and was announced at
https://groups.google.com/forum/#!topic/closure-compiler-discuss/7VyMemWKqdgIf you're getting it from the official npm package, everything should be
the same as before, as Chad says.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ChadKillingsworth/closure-compiler-npm/issues/29#issuecomment-233987082,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMDKp8phEd892xAXdzNsqFpWODDsXcWks5qXj_JgaJpZM4JQnz_
.
It simplifies our release process. If it causes pain a lot of pain we can rename it back to compiler.jar for the next release.
So far, the only reports have been from npm plugins that pre-date our official grunt/gulp plugins. I have no problem breaking plugins that haven't been updated in 3 years.