-
Notifications
You must be signed in to change notification settings - Fork 444
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
Compilation errors: classes missing on v2 version #81
Comments
|
[Cross-linking for reference: https://stackoverflow.com/questions/40746004/compiling-dropbox-api-classes-missing / https://www.dropboxforum.com/t5/API-support/Compilation-error-whren-installing-API/m-p/195237#M8889 ] Can you let us know what commands you're running, and which one in particular fails with this error? Thanks in advance! |
|
Sure: |
|
Thanks! Did the other commands from the Building from source instructions run successfully? |
|
No. The errors is exactly the same. I downloaded the zip file instead of to clone repository. |
|
I'm not sure I follow. Did you run those as well, and receive errors there as well? If you can share the full log, including the output for the other commands, that would be helpful so we can make sure we reproduce exactly what you're seeing. |
|
Executed command: ./gradlew build --stacktrace Result: |
|
I've attached a log file now |
|
Thanks, that's helpful. We'll look into it. |
|
I have the same problem |
|
Running ./update-submodules before ./gradlew as described in ReadMe.md fixed the missing classes for me. An error message like "stone: Submodule missing. Did you run ./update-submodules?" would be nice, though. However, I had to do some more work to make the build succeed.
$ git describe --tags According to typing docs, the module is new in Python 3.5. So let's use Python 3 instead of Python 2: $ ./gradlew test Some experiments show that, at least on Windows, gradle's Exec command line arguments are not passed literally. As a result, stone.cli is called with auth=user for the routeFilter instead of auth="user", and that is not valid syntax. Adding the following quotes make stone.cli succeed: $ ./gradlew test Python 3 does not have iteritems, and it needs a slightly different syntax when using the abc module: $ ./gradlew test |
|
@drizzd I had the same issue yesterday (on macOS), but instead of using python3, which comes bundled with typing, I installed the typing module and some other missing ones via |
|
I get this too. I followed the instructions exactly. Fresh clone of the repo. |
|
I think there are two issues here 1. You need to pull in submodules Like the That said, 2. You need to install Stone's dependencies Stone depends on That said:
|
|
drizzd commented on Nov 27, 2016 |
|
Working on my Mac, followed @cakoose advice, installed my python version and manage to get it build successfully.
DONE! |
Compiling latest dropbox sdk produces these errors:
Starting a new Gradle Daemon for this build (subsequent builds will be faster).
Parallel execution with configuration on demand is an incubating feature.
Set JDK6_HOME environment to disable boot classpath warnings.
:generateStone UP-TO-DATE
:compileJava
warning: [options] bootstrap class path not set in conjunction with -source 1.6
/usr/local/AndroidProjects/dropbox-sdk-java-master/src/main/java/com/dropbox/core/v2/DbxTeamClientV2.java:24: error: cannot find symbol
public class DbxTeamClientV2 extends DbxTeamClientV2Base {
^
symbol: class DbxTeamClientV2Base
/usr/local/AndroidProjects/dropbox-sdk-java-master/src/main/java/com/dropbox/core/v2/DbxClientV2.java:19: error: cannot find symbol
public class DbxClientV2 extends DbxClientV2Base {
^
symbol: class DbxClientV2Base
/usr/local/AndroidProjects/dropbox-sdk-java-master/src/main/java/com/dropbox/core/v2/DbxAppClientV2.java:20: error: cannot find symbol
class DbxAppClientV2 extends DbxAppClientV2Base {
^
symbol: class DbxAppClientV2Base
3 errors
:compileJava FAILED
FAILURE: Build failed with an exception.
Execution failed for task ':compileJava'.
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
The text was updated successfully, but these errors were encountered: