Go to file
Chris Sarbora b1f4115b47 Prevent Maven target from grabbing transitive dependencies
Dependencies of Maven targets will have to be managed manually. The prebuilt
target that the Maven target is based off of wasn't designed to handle multiple
artifacts per project. Additionally, this target is mainly intended for grabbing
APKs or other standalone blobs, not for pulling in a full jar dependency tree.
If that is your use case, you may want to investigate simply converting your
project to Gradle (or the Maven build system, if you can stomach it).

Change-Id: Iaf48c95c704cfdc85e0074394ff3c7464937e60c
2015-07-08 08:27:29 -07:00
bash_completion repo bash completion: _find_repo: improve check 2013-05-05 21:37:17 -07:00
build Prevent Maven target from grabbing transitive dependencies 2015-07-08 08:27:29 -07:00
config cm: Update stagefright-plugins depdendencies 2015-06-18 02:22:35 -07:00
overlay vendor/cm: overlay start for ProfileService in external framework. 2015-06-29 14:39:24 -07:00
prebuilt/common Additional APN cleanup and modifications 2015-07-02 16:55:34 -07:00
sepolicy vendor/cm: overlay start for ProfileService in external framework. 2015-06-29 14:39:24 -07:00
.gitignore gitignore 2010-06-27 20:11:11 -07:00
CHANGELOG.mkdn Changelog: Add M11, remove M6 2014-10-09 15:29:18 +02:00
CONTRIBUTORS.mkdn vendor: cm: yet more updates to contributors 2015-05-01 22:57:05 +00:00
LICENSE LICENSE: update year 2012-09-19 16:29:50 +05:30
README.mkdn Updates for cm-12.1 2015-04-01 05:30:52 +03:00
vendorsetup.sh vendorsetup: Handle new jenkins build parameters 2015-07-01 11:40:48 -07:00

CyanogenMod

Submitting Patches

Patches are always welcome! Please submit your patches via CyanogenMod Gerrit! You can do this by using these commands:

(From root android directory)
. build/envsetup.sh
(Go to repo you are patching, make your changes and commit)
cmgerrit <for(new)/changes(patch set)> <branch/change-id> 

repo start cm-12.1 .
(Make your changes and commit)
repo upload .

Note: "." meaning current directory For more help on using this tool, use this command: repo help upload

Make your changes and commit with a detailed message, starting with what you are working with (i.e. vision: Update Kernel) Commit your patches in a single commit. Squash multiple commit using this command: git rebase -i HEAD~<# of commits>

To view the status of your and others' patches, visit CyanogenMod Code Review

Getting Started

To get started with Android/CyanogenMod, you'll need to get familiar with Repo and Version Control with Git.

To initialize your local repository using the CyanogenMod trees, use a command like this:

repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1

Then to sync up:

repo sync

Please see the CyanogenMod Wiki for building instructions, by device.

For more information on this Github Organization and how it is structured, please read the wiki article

Buildbot

All supported devices are built nightly and periodically as changes are committed to ensure the source trees remain buildable.

You can view the current build statuses in the Jenkins tool.