Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363574

Summary: [catalog] m2e-android 0.3.0 -> 0.4.0
Product: z_Archived Reporter: Ricardo Gladwell <ricardo>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: igor
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: other   
Whiteboard:

Description Ricardo Gladwell CLA 2011-11-11 06:37:18 EST
Build Identifier: 

Could we please update the m2e-android (me.gladwell.eclipse.m2e.android) in the discovery catalog from 0.3.0 to the new 0.4.0 release, please?

Reproducible: Always
Comment 1 Igor Fedorenko CLA 2011-11-12 06:04:23 EST
Done.
Comment 2 Igor Fedorenko CLA 2011-11-12 17:29:06 EST
Turned out, I can't install the connector on clean Eclipse java epp package due to some missing dependencies (see poorly formatted p2 error report below). 

All m2e discovery catalog entries must install all required dependencies, which usually happens automatically as long as p2 has access to all required repositories.


Cannot complete the install because one or more required items could not be found.
Software currently installed: Android Configurator for M2E 0.4.0 (me.gladwell.eclipse.m2e.android.feature.feature.group 0.4.0)
Missing requirement: Android Development Toolkit 15.0.0.v201110251216-213216 (com.android.ide.eclipse.adt 15.0.0.v201110251216-213216) 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.4.0 (me.gladwell.eclipse.m2e.android 0.4.0)
To: bundle com.android.ide.eclipse.adt 15.0.0
Cannot satisfy dependency:
From: Android Configurator for M2E 0.4.0 (me.gladwell.eclipse.m2e.android.feature.feature.group 0.4.0)
To: me.gladwell.eclipse.m2e.android [0.4.0]
Comment 3 Ricardo Gladwell CLA 2011-11-13 05:48:32 EST
That's weird, I tested this when you approved it on a clean build of Eclipse with just m2e installed and it worked.

The update site points to a composite sites, that in turn points to a p2 mirror of the ADT update site.

We have seen intermittent connectivity problems with the ADT p2 repo which I thought we had resolved. Could you retry and let me know if you get the same problem again, please?
Comment 4 Igor Fedorenko CLA 2011-11-13 10:08:39 EST
Never mind, driver error, m2e/android integration installs without problems from m2e discovery catalog. Both m2e 1.0 and 1.1 work now, btw.
Comment 5 Ricardo Gladwell CLA 2011-11-14 03:47:51 EST
Thanks :)
Comment 6 Igor Fedorenko CLA 2011-11-14 06:26:16 EST
Did you really mean to reopen?
Comment 7 Ricardo Gladwell CLA 2011-11-14 06:26:51 EST
Sorry, no.
Comment 8 Denis Roy CLA 2021-04-19 13:22:56 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/