-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Android studio 3.0 beta can't use generator 3.2.2 #755
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
Comments
It looks like I have the same issue. I use Android Studio 3.0 beta2. objc[79443]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/java (0x1079024c0) and /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre/lib/libinstrument.dylib (0x1079ca4e0). One of the two will be used. Which one is undefined. Process finished with exit code 1 |
I have the same issue. Please, could you give us some guidelines to repair it? |
Solved!! After executed gradle/application/run and viewed other error in this line: This is my DaoGenerator build.gradle:
References: |
Changing from 2 dots to 1 dot worked for me. Thank you. |
So the issue is just that paths are resolved differently? Closing this then. -ut |
Tried doing this on android studio 2.3.3, works just fine.
Brand new project(android studio 3.0 beta2), using gradle to compile the generator, would get
Error:Execution failed for task ':lib:run'.
If use the play button to compile(a java library) it would give
Exception in thread "main" java.lang.NoClassDefFoundError: org/greenrobot/greendao/generator/Schema
at com.askjeffreyliu.lib.myClass.main(myClass.java:16)
Caused by: java.lang.ClassNotFoundException: org.greenrobot.greendao.generator.Schema
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 1 more
Process finished with exit code 1
The text was updated successfully, but these errors were encountered: