Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "docs: migration guide link update" into mnc-preview-docs

Browse Source
This commit is contained in:
Rich Slogar
2015-06-30 22:21:16 +00:00
committed by Android (Google) Code Review
parent ed053477d0 a351bca51a
commit 761b4a7deb
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/html/sdk/installing/migrate.jd
View File

@@ -50,7 +50,7 @@ the key changes you should be aware of as you prepare to migrate to Android Stud
<p>Android Studio uses a different project structure. Each Eclipse ADT <p>Android Studio uses a different project structure. Each Eclipse ADT
project is called a module in Android Studio. Each instance of Android project is called a module in Android Studio. Each instance of Android
Studio contains a project with one or more app modules. For more information see, Studio contains a project with one or more app modules. For more information see,
<a href="{@docRoot}tools/studio/eclipse-migration-guide.html#project-structure">Project <a href="{@docRoot}tools/studio/eclipse-transition-guide.html#project-structure">Project
Structure</a>.</p></li> Structure</a>.</p></li>
<li><strong>Manifest settings</strong> <li><strong>Manifest settings</strong>
@@ -59,14 +59,14 @@ the key changes you should be aware of as you prepare to migrate to Android Stud
<code>build.gradle</code> file. These elements are still valid manifest entries and may <code>build.gradle</code> file. These elements are still valid manifest entries and may
appear in manifests from older projects, imported projects, dependencies, and libraries. For appear in manifests from older projects, imported projects, dependencies, and libraries. For
more information see, more information see,
<a href="{@docRoot}tools/studio/eclipse-migration-guide.html#manifest-settings">Manifest <a href="{@docRoot}tools/studio/eclipse-transition-guide.html#manifest-settings">Manifest
Settings</a>.</p></li> Settings</a>.</p></li>
<li><strong>Dependencies</strong> <li><strong>Dependencies</strong>
<p>Library dependencies are handled differently in Android Studio, using Gradle dependency <p>Library dependencies are handled differently in Android Studio, using Gradle dependency
declarations and Maven dependencies for well-known local source and binary libraries with declarations and Maven dependencies for well-known local source and binary libraries with
Maven coordinates. For more information see, Maven coordinates. For more information see,
<a href="{@docRoot}tools/studio/eclipse-migration-guide.html#dependencies">Dependencies</a></p> <a href="{@docRoot}tools/studio/eclipse-transition-guide.html#dependencies">Dependencies</a></p>
</li> </li>
<li><strong>Test code</strong> <li><strong>Test code</strong>
@@ -261,7 +261,7 @@ Android Studio project and does not impact the existing Eclipse ADT project. </p
<a href="http://www.gradle.org">Gradle</a>-based build system to become familiar with the new <a href="http://www.gradle.org">Gradle</a>-based build system to become familiar with the new
project and module structure, flexible build settings, and other advanced Android development project and module structure, flexible build settings, and other advanced Android development
capabilities. For a comparison of Eclipse ADT and Android Studio features and usage, see capabilities. For a comparison of Eclipse ADT and Android Studio features and usage, see
<a href="{@docRoot}tools/studio/eclipse-migration-guide.html">Transitioning to Android Studio from <a href="{@docRoot}tools/studio/eclipse-transition-guide.html">Transitioning to Android Studio from
Eclipse</a>. For specific Android Studio how-to documentation, see the pages in the Eclipse</a>. For specific Android Studio how-to documentation, see the pages in the
<a href="{@docRoot}tools/workflow/index.html">Workflow</a> section. <a href="{@docRoot}tools/workflow/index.html">Workflow</a> section.
</p> </p>