Community
Participate
Working Groups
Please create an m2e marketplace catalog item for the Android Connector for M2E <catalogItem> <categoryId>org.eclipse.m2e.discovery.category.lifecycles</categoryId> <description>Android Configurator for M2E Maven Integration for Eclipse</description> <groupId>m2e-android</groupId> <id>me.gladwell.eclipse.m2e.android</id> <kind>lifecycles</kind> <license>EPL</license> <name>Android Connector</name> <provider></provider> <p2> <repositoryUrl>http://rgladwell.github.com/m2e-android/updates/</repositoryUrl> <iuId>me.gladwell.eclipse.m2e.android.feature</iuId> </p2> <overview> <summary>Android Configurator for M2E Maven Integration for Eclipse</summary> <url>http://rgladwell.github.com/m2e-android</url> </overview> </catalogItem> To create a sample project: 1. In Eclipse select File -> New -> Project... 2. Select Maven -> Maven Project and click "Next" 3. Click "Next" again 4. Click "Add Archetype..." 5. In Archetype Group Id enter "de.akquinet.android.archetypes" 6. In Archetype Artifact Id" enter "android-quickstart" 7. In Archetype Version enter "1.0.5" 8. Click "OK" 9. Click Next 10. Enter your desired project group and artefact ID, version and, optionally, set the "platform" property for the Android version (defaults to '7') 11. Click Finish
Please see here for more information on using m2e-android: https://code.google.com/a/eclipselabs.org/p/m2eclipse-android-integration/wiki/GettingStarted
Is https://github.com/jayway/maven-android-plugin the canonical source repository?
please disregard comment 2 (coffee obviously hadn't kicked in :-) )
I am having difficulties installing m2e-android on fresh/clean m2e install (for example, "IDE For Java Developers" Eclipse 3.7/Indigo EPP package). The basic assumption is that all m2e discovery catalog entries should automatically install all their dependencies. I realize ADT is a special case, so native SDK will likely need to be installed manually, but we can't accept m2e catalog entries that do not install on default m2e configuration. It usually takes adding associateSitesURL to <site/> element (see [1] for how it's done in m2e-wtp, for example) and proper dependencies in feature.xml to make eclipse automatically find and install all dependencies. Unfortunately, I am not sure if associateSitesURL works with Tycho eclipse-repository packaging type (it certainly works with eclipse-update-site and deployable features). [1] https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclipse.wtp.feature/category.xml The error message I get Cannot complete the install because one or more required items could not be found. Software currently installed: Android Configurator for M2E 0.3.0 (me.gladwell.eclipse.m2e.android.feature.feature.group 0.3.0) Missing requirement: Android Development Toolkit 12.0.0.v201106281929-138431 (com.android.ide.eclipse.adt 12.0.0.v201106281929-138431) requires 'bundle com.android.ide.eclipse.ddms 0.0.0' but it could not be found Cannot satisfy dependency: From: Android Configurator for M2E 0.3.0 (me.gladwell.eclipse.m2e.android.feature.feature.group 0.3.0) To: com.android.ide.eclipse.adt 0.9.9
Hi Igor That update site should point to a composite Repository. This should allow you to install M2E, the ADT and the Android Connector. Most Indigo installs already have M2E installed, so it should work if you select Android Connector and Development Tools: did you see those options when you installed? The idea is that it should automatically install the required plugins during an automatic install via the Eclipse Marketplace. I'm assuming the same thing will happen via a M2E Marketplace install: i.e. users will not have to manually select Development Tools. Please let me know if this worked.
I updated m2e catalog with few changes * In order for installation to succeed, I has to explicitly list ADP features in the catalog item. I think this is necessary because Google still publishes old-style update site. * I added <lifecycleMappingIU/> element to the catalog item descriptor. Without this element m2e will not be able to automatically discover m2e-android. * I used provide=eclipselabs.org as per parent pom [1]. If you want any of these changes, please reopen this request. Also, I am not sure if this is expected, but I was not able to successfully import test project I generated from android-quickstart. The project uses maven-jar-plugin during process-classes build phase and there is no mapping for this. [1] http://svn.codespot.com/a/eclipselabs.org/m2eclipse-android-integration/trunk/com.googlecode.eclipse.m2e.android.parent/pom.xml
Hi Igor Thanks for that, appreciate, will test. The provider information is incorrect, we recently moved the project to github and switched providers to my company[1]. Could you please update this information? [1] https://raw.github.com/rgladwell/m2e-android/master/pom.xml
Changed provide name to Gladwell Consultants Ltd. as requested.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
