-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hadoop-lzo jar resolution #62
Comments
Not sure if this is the correct fix, but I was able to get past this issue by adding a new global exclusion to Ivy by editing the pants.ini file under [resolve.ivy]: |
I think that your fix is likely the right answer. We are getting ready to update fsq.io, would you be interested in sending a PR? |
Sure, I can submit it tonight (if that fits with your timeline).
|
That sounds great! The update is addressing unrelated bug in our dependencies, so we may need to land that first in order to get the build green anyway |
Hello,
I'm running into an issue using the latest fsqio master where ivy is consistently unable to resolve hadoop-lzo and fails to run serve.py.
I'm not all too familiar with the dependency management aspects of twofishes. I'm running this from an ubuntu 14.04 docker container, and everything has worked historically ... until now. Any recommendations on how to figure out what's going on / solve for this? I would greatly appreciate it.
Strangely, when I
git clone
the fsqio repo, and run serve.py from the command line on an Amazon Linux 1 EC2 instance it works perfectly. No dependency issues. I need to run it from a docker container, though preferably.The text was updated successfully, but these errors were encountered: