From 022171be9d0a7db42fca6fe6d3f3c547ed2f4efb Mon Sep 17 00:00:00 2001
From: Dirk Dougherty
One library project cannot reference another
- -A library cannot depend on another library.
-A library project can include a JAR library
You can develop a library project that itself includes a JAR library, however
@@ -664,13 +661,6 @@ application must declare the external library their manifest files, in a <uses-library>
element.
Library project can not include AIDL files
- -The tools do not support the use of AIDL files in a library project. -Any AIDL files used by an application must be stored in the application project -itself.
-Library project can not include raw assets
The tools do not support the use of raw asset files in a library project. @@ -730,8 +720,76 @@ project can reference the library project by a relative link. You can place the library project What is important is that the main project can reference the library project through a relative link.
+This section provides information about how to migrate a library project +created with ADT 0.9.7 to ADT 0.9.8 (or higher). The migration is needed only if +you are developing in Eclipse with ADT and assumes that you have also upgraded +to SDK Tools r7 (or higher).
+ +The way that ADT handles library projects has changed between
+ADT 0.9.7 and ADT 0.9.8. Specifically, in ADT 0.9.7, the src/
+source folder of the library was linked into the dependent application project
+as a folder that had the same name as the library project. This worked because
+of two restrictions on the library projects:
gen/ source folder), andsrc/ and be
+stored at the root of the project.In ADT 0.9.8, both of those restrictions were removed. A library project can
+have as many source folders as needed and each can have any name. Additionally,
+a library project can store source folders in any location of the project. For
+example, you could store sources in a src/java/ directory. In order
+to support this, the name of the linked source folders in the main project are
+now called <library-name>_<folder-name> For
+example: MyLibrary_src/ or MyLibrary_src_java/.
Additionally, the linking process now flags those folders in order for ADT to +recognize that it created them. This will allow ADT to automatically migrate the +project to new versions of ADT, should they contain changes to the handling of +library projects. ADT 0.9.7 did not flag the linked source folders, so ADT 0.9.8 +cannot be sure whether the old linked folders can be removed safely. After +upgrading ADT to 0.9.8, you will need to remove the old linked folders manually +in a simple two-step process, as described below.
+ +Before you begin, make sure to create a backup copy of your application or +save the latest version to your code version control system. This ensures that +you will be able to easily revert the migration changes in case there is a +problem in your environment.
+ +When you first upgrade to ADT 0.9.8, your main project will look as shown
+below, with two linked folders (in this example, MyLibrary and
+MyLibrary_src — both of which link to
+MyLibrary/src. Eclipse shows an error on one of them because they
+are duplicate links to a single class.
+
+To fix the error, remove the linked folder that does not contain the
+_src suffix.
MyLibrary folder) and choose Build Path >
+Remove from Build Path, as shown below.
+
+
+This should resolve the error and migrate your library project to the new +ADT environment.
-One library project cannot reference another
- -A library cannot depend on another library.
-A library project can include a JAR library
You can develop a library project that itself includes a JAR library. When
@@ -858,13 +854,6 @@ application must declare the external library their manifest files, in a <uses-library>
element.
Library project cannot include AIDL files
- -The tools do not support the use of AIDL files in a library project. -Any AIDL files used by an application must be stored in the application project -itself.
-Library project cannot include raw assets
The tools do not support the use of raw asset files in a library project. diff --git a/docs/html/images/developing/lib-migration-0.png b/docs/html/images/developing/lib-migration-0.png new file mode 100644 index 0000000..226b0a5 Binary files /dev/null and b/docs/html/images/developing/lib-migration-0.png differ diff --git a/docs/html/images/developing/lib-migration-1.png b/docs/html/images/developing/lib-migration-1.png new file mode 100644 index 0000000..f413dab Binary files /dev/null and b/docs/html/images/developing/lib-migration-1.png differ diff --git a/docs/html/images/developing/lib-migration-2.png b/docs/html/images/developing/lib-migration-2.png new file mode 100644 index 0000000..0aa5849 Binary files /dev/null and b/docs/html/images/developing/lib-migration-2.png differ diff --git a/docs/html/sdk/adt_download.jd b/docs/html/sdk/adt_download.jd index f98caf5..126c052 100644 --- a/docs/html/sdk/adt_download.jd +++ b/docs/html/sdk/adt_download.jd @@ -22,11 +22,18 @@ ADT Installation.
+ADT 0.9.8 (August 2010)
+ ADT 0.9.8 is designed for use with SDK Tools r7 and later. Before +updating to ADT 0.9.8, we highly recommend that you use the Android SDK and +AVD Manager to install SDK Tools r7 into your SDK.
src/. There is now support for any number of source folders,
+with no name restriction. They can even be in subfolder such as
+src/java. If you are already working with library projects created
+in ADT 0.9.7, see Migrating
+library projects to ADT 0.9.8 for important information about moving
+to the new ADT environment.car/desk, night/notnight and
+navexposed/navhidden.
ADT 0.9.7 (May 2010)
diff --git a/docs/html/sdk/index.jd b/docs/html/sdk/index.jd
index 5e92253..7016eee 100644
--- a/docs/html/sdk/index.jd
+++ b/docs/html/sdk/index.jd
@@ -1,17 +1,17 @@
page.title=Android SDK
sdk.redirect=0
-sdk.win_download=android-sdk_r06-windows.zip
-sdk.win_bytes=23293160
-sdk.win_checksum=7c7fcec3c6b5c7c3df6ae654b27effb5
+sdk.win_download=android-sdk_r07-windows.zip
+sdk.win_bytes=23669664
+sdk.win_checksum=69c40c2d2e408b623156934f9ae574f0
-sdk.mac_download=android-sdk_r06-mac_86.zip
-sdk.mac_bytes=19108077
-sdk.mac_checksum=c92abf66a82c7a3f2b8493ebe025dd22
+sdk.mac_download=android-sdk_r07-mac_x86.zip
+sdk.mac_bytes=19229546
+sdk.mac_checksum=0f330ed3ebb36786faf6dc72b8acf819
-sdk.linux_download=android-sdk_r06-linux_86.tgz
-sdk.linux_bytes=16971139
-sdk.linux_checksum=848371e4bf068dbb582b709f4e56d903
+sdk.linux_download=android-sdk_r07-linux_x86.tgz
+sdk.linux_bytes=17114517
+sdk.linux_checksum=e10c75da3d1aa147ddd4a5c58bfc3646
@jd:body
@@ -50,7 +50,7 @@ for Eclipse.
4. Add Android platforms and other components to your SDK
Use the Android SDK and AVD Manager, included in the SDK starter package, to -add one or more Android platforms (for example, Android 1.6 or Android 2.0) and +add one or more Android platforms (for example, Android 1.6 or Android 2.2) and other components to your SDK. If you aren't sure what to add, see Which components do I need?
diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index 404e938..a665e95 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -75,8 +75,8 @@
+SDK Tools, Revision 7 (September 2010)
+ If you are developing in Eclipse with ADT, note that SDK Tools r7 is +designed for use with ADT 0.9.8 and later. After installing SDK Tools r7, we +highly recommend updating your ADT Plugin to 0.9.8.
+-pre-build, -pre-compile, and
+-post-compile.android -h update sdk
+for more information.
SDK Tools, Revision 6 (May 2010)