Migrating from IntelliJ Projects-低调大师

Migrating from IntelliJ Projects

2016-09-27 622

We might provide an automatic migration option in Android Studio in the future.

For now, to migrate your IntelliJ project to an Android Gradle project (which can then be imported into IntelliJ and supported directly in IntelliJ), follow the following steps:

Create a basic "build.gradle" file. Unlike the default Gradle file created by Android Studio when you create a new project, the following gradle file will point the source code directories to the existing folders (e.g. res/, src/) instead of the default new directory structure used for Gradle projects (src/main/java/, src/main/res/, etc). A sample gradle file is given below.
Identify which library projects you are using (such as ActionBarSherlock). In Gradle you no longer need to add in these libraries as source code projects; you can simply refer to them as dependencies, and the build system will handle the rest; downloading, merging in resources and manifest entries, etc. For each library, look up the corresponding AAR library dependency name (provided the library in question has been updated as a android library artifact), and add these to the dependency section.
- To find the right declaration statements for your libraries, you might find the following useful: http://gradleplease.appspot.com/
Test your build by running gradle assembleDebug in your project. If you have not built with Gradle before, install it from http://www.gradle.org/downloads. Note that when you create new projects with Studio, we create a gradle wrapper script ("gradlew" and "gradlew.bat") in the project root directory, so any users of the project can just run "gradlew assembleDebug" etc in your project and gradle is automatically installed and downloaded. However, your existing IntelliJ projects presumably does not already have the gradle scripts.)
Note that IntelliJ projects for Android generally follow the same structure as Eclipse ADT projects, so the instructions in the Eclipse migration guide might be helpful.

build.gradle:

buildscript {

repositories {

mavenCentral()

}

dependencies {

classpath 'com.android.tools.build:gradle:0.5.+'

}

apply plugin: 'android'

dependencies {

compile fileTree(dir: 'libs', include: '*.jar')

}

android {

compileSdkVersion 18

buildToolsVersion "18.0.1"

sourceSets {

main {

manifest.srcFile 'AndroidManifest.xml'

java.srcDirs = ['src']

resources.srcDirs = ['src']

aidl.srcDirs = ['src']

renderscript.srcDirs = ['src']

res.srcDirs = ['res']

assets.srcDirs = ['assets']

}

// Move the tests to tests/java, tests/res, etc...

instrumentTest.setRoot('tests')

// Move the build types to build-types/<type>

// For instance, build-types/debug/java, build-types/debug/AndroidManifest.xml, ...

// This moves them out of them default location under src/<type>/... which would

// conflict with src/ being used by the main source set.

// Adding new build types or product flavors should be accompanied

// by a similar customization.

debug.setRoot('build-types/debug')

release.setRoot('build-types/release')

}

For more information on customizing your build once you have the basics set up, see the new build system user guide. For additional information, see the build system overview page.

http://tools.android.com/tech-docs/new-build-system/migrating-from-intellij-projects

微信关注我们

原文链接：https://yq.aliyun.com/articles/269396

转载内容版权归作者及来源网站所有！

低调大师中文资讯倾力打造互联网数据资讯、行业资源、电子商务、移动互联网、网络营销平台。持续更新报道IT业界、互联网、市场资讯、驱动更新,是最及时权威的产业资讯及硬件资讯报道平台。

【聚划算 Android 技术周刊第六期- 20160923】

我们是聚划算无线Android团队，目前负责聚划算客户端、手淘天猫聚划算插件、淘抢购插件、俪人购客户端等，欢迎交流同时欢迎优秀的人才转岗或者加盟 --- 金秋十月，又到了可以拿秋乏当借口打打盹的季节了，不过打盹之前，何不花几分钟来看看我们的 Android 技术周刊呢 ~ （这周我们聚划算Android开发组的小伙伴都来投稿了哦！） Android 热点资讯谷歌安卓Lollipop成使用最广泛安卓系统，安卓7.0低于千分之一经过谷歌和oem厂家不断的努力，以及老旧安卓手机的自然退出使用，安卓系统碎片化的问题已经得到了较大的改善，从最近一期谷歌安卓系统统计来看，低于安卓4.x的系统已经几乎可以忽略不记了。不过目前使用最广泛的安卓 ... http://www.inexus.co/article-4800-1.html 谷歌官方确认

2016-09-28

599

前言随着移动互联网的兴起，Webapp开始大行其道。大概在15年下半年的时候我接触到了HybridApp。因为当时还没毕业嘛，所以并不清楚自己未来的方向，所以就投入了HybridApp的怀抱。 HybridApp最早好像是国外的PhoneGap，然后国内有AppCan、Dcloud、APICloud等等。我当时接触的是APICloud，相比于其他平台，APICloud最大的特点是它的混合程度比较高！要知道，Webapp最大的问题就是性能问题始终无法和原生App相比，由此才发展出来HybridApp。界内公认的最稳定的的Hybrid开发方式就是：由Native解决交互问题，由H5解决应用层问题。比如AppStore就是采用这种模式。在这一点上APICloud做的还是不错的，它的交互都是调用原生的接口，而应用层开发者可以自行通过H5进行开发。当然了，HybridApp的坑还是比较多的。在大概半年的时间里我踩了无数的坑。。。想起来都是泪啊。不说了，今天说说React Native。 React Native React Native 因为Hybrid的平台太多了，所以一直以为R...

2016-09-28

629

资源下载

更多资源

优质分享App

近一个月的开发和优化，本站点的第一个app全新上线。该app采用极致压缩，本体才4.36MB。系统里面做了大量数据访问、缓存优化。方便用户在手机上查看文章。后续会推出HarmonyOS的适配版本。

Nacos

Nacos /nɑ:kəʊs/ 是 Dynamic Naming and Configuration Service 的首字母简称，一个易于构建 AI Agent 应用的动态服务发现、配置管理和AI智能体管理平台。Nacos 致力于帮助您发现、配置和管理微服务及AI智能体应用。Nacos 提供了一组简单易用的特性集，帮助您快速实现动态服务发现、服务配置、服务元数据、流量管理。Nacos 帮助您更敏捷和容易地构建、交付和管理微服务平台。

Spring

Spring框架（Spring Framework）是由Rod Johnson于2002年提出的开源Java企业级应用框架，旨在通过使用JavaBean替代传统EJB实现方式降低企业级编程开发的复杂性。该框架基于简单性、可测试性和松耦合性设计理念，提供核心容器、应用上下文、数据访问集成等模块，支持整合Hibernate、Struts等第三方框架，其适用范围不仅限于服务器端开发，绝大多数Java应用均可从中受益。

Rocky Linux

Rocky Linux（中文名：洛基）是由Gregory Kurtzer于2020年12月发起的企业级Linux发行版，作为CentOS稳定版停止维护后与RHEL（Red Hat Enterprise Linux）完全兼容的开源替代方案，由社区拥有并管理，支持x86_64、aarch64等架构。其通过重新编译RHEL源代码提供长期稳定性，采用模块化包装和SELinux安全架构，默认包含GNOME桌面环境及XFS文件系统，支持十年生命周期更新。