search

adobe / aem-htl-repl

Read–Eval–Print Loop environment for HTL.
https://docs.adobe.com/docs/en/htl.html
Apache License 2.0
152 stars 63 forks source link

Build fails with check signature, not in GZIP format #8

Closed joannehoaz closed 8 years ago

joannehoaz commented 9 years ago

Running the command mvn clean install content-package:install

produces the following error and no package is built: Failed to execute goal com.day.jcr.vault:content-package-maven-plugin:0.0.20:check-signature (default-check-signature) on project com.adobe.granite.sightly.repl: Failed to check signatures: Not in GZIP format

Is there anything else to try?

gabrielwalt commented 9 years ago

Hi, I'm not sure what exactly is causing the problem you describe, but I've updated the installation instructions with a method that doesn't require Maven anymore. Have a look at https://github.com/Adobe-Marketing-Cloud/aem-sightly-repl.

ghost commented 9 years ago

Thank you!

From: Gabriel Walt [mailto:notifications@github.com] Sent: Tuesday, June 30, 2015 10:20 AM To: Adobe-Marketing-Cloud/aem-sightly-repl Subject: Re: [aem-sightly-repl] Build fails with check signature, not in GZIP format (#8)

Hi, I'm not sure what exactly is causing the problem you describe, but I've updated the installation instructions with a method that doesn't require Maven anymore. Have a look at https://github.com/Adobe-Marketing-Cloud/aem-sightly-repl.

— Reply to this email directly or view it on GitHubhttps://github.com/Adobe-Marketing-Cloud/aem-sightly-repl/issues/8#issuecomment-117243513.

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

Shivamurthy-MN commented 8 years ago

Hi all, How to make this work for all pages?

Thanks, Shiv MN

raducotescu commented 8 years ago

I think that this was fixed as a side-effect of #12. I cannot reproduce this issue with a fresh build. Feel free to reopen it if that's still the case.