I have a project, which i want to configure on my computer.
On anothe computer it works, but with old version of Android Studio 0.4.0 whenever I use 0.5.2
The proble is that after I launch app it show error
Build script error, unsupported Gradle DSL method found: 'coreLibrary()'!
Possible causes could be:
- you are using Gradle version where the method is absent
- you didn't apply Gradle plugin which provides the method
- or there is a mistake in a build script
But in order to make it work I have to use this flag! I already tried to enable it in the settings>Android compilers > "Add --core-library" flag, but it useless...
in the gradle i have next part of code:
dexOptions {
coreLibrary true;
}
This error showed only after activation this lines... Without them it don't work...
HOW SHOULD I FIX THIS? Maybe it is because of different versions.. if yes then how should I write to make it work?
After changing to coreLibrary = true It compilate Gradle fine BUt stille require after Run --core-library flag using.... But i already set it to true in settings...
It shows not almost the same error:
Error:Execution failed for task ':BusKg:preDexDebug'.
> com.android.ide.common.internal.LoggedErrorException: Failed to run command:
D:ProgrammsProgrammsadt-bundle-windows-x86_64-20131030sdkuild-toolsandroid-4.4dx.bat --dex --output D:Android2BUS.kgmarshrutkaBusKguildpre-dexeddebugannotations-api-6.0.26-27e56569b50edbdd453f9bc0e568cde1fbfa621b.jar C:UsersViacheslav.gradlecachesmodules-2files-2.1org.apache.tomcatannotations-api6.0.2650aeafa144ed17913ed44d18ac61afd505a9e3eannotations-api-6.0.26.jar
Error Code:
1
Output:
trouble processing "javax/xml/ws/WebServiceRef.class":
Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.
This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.
However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.
If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.
If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.
If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.
1 error; aborting
Thanks in advance for any help...
See Question&Answers more detail:
os