Closed GoogleCodeExporter closed 9 years ago
I think that all thats required is a change tot he manifest. at the moment the
dependencies specify 11 inclusive to 15 exclusive.
Original comment by o...@sixgreen.com
on 28 Oct 2011 at 8:09
Index: META-INF/MANIFEST.MF
===================================================================
--- META-INF/MANIFEST.MF (revision 62)
+++ META-INF/MANIFEST.MF (working copy)
@@ -2,13 +2,13 @@
Bundle-ManifestVersion: 2
Bundle-Name: Android API Analysis
Bundle-SymbolicName: com.android.ide.eclipse.api.analysis;singleton:=true
-Bundle-Version: 1.0.2.qualifier
+Bundle-Version: 1.0.3.qualifier
Bundle-Activator: com.android.ide.eclipse.api.analysis.Activator
Bundle-Vendor: The Android Open Source Project
Require-Bundle: org.eclipse.ui;bundle-version="3.6.2",
org.eclipse.core.runtime;bundle-version="3.6.0",
org.eclipse.jdt.core;bundle-version="3.6.1",
- com.android.ide.eclipse.adt;bundle-version="[11.0.0,15.0.0)",
+ com.android.ide.eclipse.adt;bundle-version="[11.0.0,15.0.0]",
org.eclipse.core.resources;bundle-version="3.6.0"
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ActivationPolicy: lazy
Original comment by o...@sixgreen.com
on 28 Oct 2011 at 8:16
well there is a patch that makes 15.0.0 inclusive rather than exclusive, but
really you could likely get away with no maximum dependency:
+ com.android.ide.eclipse.adt;bundle-version="11.0.0",
it would likely work for the next several plugin updates... you would
eventually have to fix it, but maybe not right at the next update.
Original comment by o...@sixgreen.com
on 28 Oct 2011 at 8:18
> + com.android.ide.eclipse.adt;bundle-version="11.0.0",
These settings can cause that main ADT plugin crash when ADT team change API
and it is harder to detect.
I have upgrade to ADT 15 and test it.
Original comment by snp...@gmail.com
on 28 Oct 2011 at 9:37
Original issue reported on code.google.com by
o...@sixgreen.com
on 28 Oct 2011 at 8:00