android - Last ADT update (22.6.3) spoiled my Eclipse -


I'm using mavenized library project with the following plugin:

  & lt ; Plugin & gt; & Lt; Group & gt; Com.jayway.maven.plugins.android.generation2 & lt; / Group & gt; & Lt; ArtifactId & gt; Android-maven-plugin & lt; / ArtifactId> & Lt; Version & gt; 3.6.0 & lt; / Edition & gt; & Lt; Extensions & gt; True & lt; / Extensions & gt; & Lt; Configuration & gt; & Lt; NativeLibrariesDirectory & gt; Ignored & lt; / NativeLibrariesDirectory & gt; & Lt; AttachSources & gt; True & lt; / AttachSources & gt; & Lt; / Configuration & gt; & Lt; / Plugin & gt;  

But after the last update of ADT (22.6.3), everything went wrong, Jar is not manufactured by Eclipse, and I found an error message of lyfecicle like this:

Description resource path type type conflicting life cycle mapping (plugin execution "com.jayway.maven.plugins.android.generation2: android-Maven-plugin: 3.6.0: ProGuard (Execution: Default- ProGuard , Step: process-class) "). To enable full functionality, remove the conflicting mapping and turn on Maven-> Update Project Configuration. Pom.xml / actionbarsherlock Line 1 Meven Project Lifecycle mapping created the problem

I have followed those instructions to solve the problems, and in fact they have gone, but the jar Not being built. Attempts were made with this: but no success.

This is my eclipse (Kepler) installation description:

  • Android configurator for M2E 1.0.0 me.gladwell.eclipse.m2e .android.feature.feature.group Gladwell.me
  • Android DDS 22.6.3.v201404151837-1123206 com.android.ide.eclipse.ddms.feature.group Android open source project
  • Android Development Tool 22.6.3. V201404151837-1123206 Android open source project com.android.ide.eclipse.adt.feature.group
  • Android Hierarchy Viewer 22.6.3.v201404151837-1123206 com.android .ide.eclipse.hierarchyviewer.feature.group Android open source project
  • Andrew D Traceview 22.6.3.v201404151837-1123206 Android open source project com.android.ide.eclipse.traceview.feature.group
  • Java EE Developers 2.0.2.20140224-0000 epp.package.jee eclipsed for null IDE
  • Genymotion Eclipse Tool 1.0.3.201403261147 com.genymobile.genymotion.ide.eclipse.feature.group Genymobile
  • M1e - Maven 1.4.1.20140328-1905 for Eclipse org.eclipse .m2e.feature.feature.group Eclipse.org - m2e
  • to enter slf4j over M2e - logback (optional) 1.4.1.20140328-1905 org.eclipse.m2e.logback.feature.feature.group Eclipse .org - m2e
  • OpenGL ES 22.6.3.v201404151837-1123206 Tracer Open Source for Android com.android.ide.eclipse.gldebugger.feature.group Number Project

Any ideas?

We had this problem again after rebuilding the entire environment (latest Eclipse Juno JEE 2E + The latest Maven-Android plugin) It has been detected that the problem is actually in the Maven-Android plugin. There is an update problem: Output directory sets are set to set targets / classes instead of bin / classes. The source of the build path of each project The tab to allow the output folder for "source folder to" box can be unchecked. For more information about this, please check it out:


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

lua - HowTo create a fuel bar -