You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 31, 2021. It is now read-only.
After running gradle eclipse and applying the workarounds from #14 and #15, I've got two remaining build errors:
The type BuildConfig is already defined.
The type R is already defined.
This is because andmore (0.5.1) creates these files into the gen folder, and this cannot be disabled afaik. And gradle-android-eclipse generates another set into build/generated/source/r/debug and build/generated/source/buildConfig/debug respectively.
I suggest gradle-android-eclipse should not create the own project's R.java and BuildConfig.java files, since andmore already takes care of this.
The text was updated successfully, but these errors were encountered:
gradle-android-eclipse isn't generating any java files directly, that must be coming from somewhere else (e.g. https://docs.gradle.org/current/userguide/eclipse_plugin.html, which this plug-in extends.) I recommend driving changes into that project instead.
After running
gradle eclipse
and applying the workarounds from #14 and #15, I've got two remaining build errors:This is because andmore (0.5.1) creates these files into the
gen
folder, and this cannot be disabled afaik. And gradle-android-eclipse generates another set intobuild/generated/source/r/debug
andbuild/generated/source/buildConfig/debug
respectively.I suggest gradle-android-eclipse should not create the own project's
R.java
andBuildConfig.java
files, since andmore already takes care of this.The text was updated successfully, but these errors were encountered: