| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Also fix a bug in a custom ant task where minSdkVersion and targetApi
were swapped.
Change-Id: Id9bac802377a04270e76def42eaf6a8fb4b3f874
|
|
|
|
|
|
|
|
| |
Rather than containing the generic devices which are now packaged with
ADT itself, it contains the nexus devices using the new device
specification.
Change-Id: I09b38b8166ba558800c2cf03150d8a3e9dd33a4f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
First, this changeset allows the arguments passed to --sources and
--classpath (renamed from --classes) to specify not just a directory,
but to specify a path as well. This might make it easier to invoke
lint from scripts if you have a path variable, so you don't have to
split it into multiple arguments.
Second, it makes the lint task in ant use these, such that any
build.xml customizations to the source paths or class paths are
automatically used rather than relying on lint's default structure
check.
Change-Id: Id8e4caf0010d7fd7245844b3099b5dc0607f0aba
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This checkin adds typo databases for six additional languages, as well
as several fixes to the infrastructure.
First, it now supports "globbing", since for example the German typo
database contains glob patterns of the form
"asymetrisch*->asymmetrisch*".
Second, it supports multiword typos (such as "all zu->allzu") which
caused some complications (since this means that the typo detector
can match beyond the word boundary it was passed in).
Third, it adds a bunch of validation code to the type dictionaries,
which uncovered a bunch of inconsistencies (duplicate entries, using
"-" instead of "->" for some separators, etc). There's now a unit test
which produces a cleaned up version of each dictionary file, as well
as tests to ensure that the ASCII and the UTF-8 comparison methods are
in sync (and this uncovered some bugs which were fixed.)
Finally, it fixes the HTML reporter such that it properly handles
UTF-8.
Change-Id: Ie32cbbe489687a7b50184696a027f87c2e21c409
|
|
|
|
|
|
|
| |
This changeset generalizes the lint typo checker to handle
non-ASCII languages (with UTF-8 encoded typo dictionaries).
Change-Id: If21a2047a127848db77d9ec6f9aae3c052e0f288
|
|
|
|
| |
Change-Id: Idde24b6b893d1029d48ba32766110a6a3cdf73c6
|
|
|
|
| |
Change-Id: I4b6f33a919e4879b57fae62651f101ced82e02d0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Running "ant lint" will now run lint on the project, and dump out the
errors to the console as well as also export the errors to lint.xml
and lint.html int the bin/ directory.
This changeset also modifies the lint CLI to allow multiple
simultaneous result reporters - so you don't have to run lint twice in
order to get both an .xml and an .html report for example (which is
useful when you're running lint on a continuous integration server,
and you want the .xml file for the lint plugin trend graph and the
html file as a user readable report to click through to from the build
page.)
Change-Id: Idf8f3f5de0857eb9e7180267a066ae933640682d
|
|
|
|
| |
Change-Id: Ie9fa05173a5e4e1c7cae48cabb37f3cfe7d085cb
|
|
|
|
|
|
|
| |
The checks were done before reading the properties.
Bug: http://code.google.com/p/android/issues/detail?id=34127
Change-Id: I954d1e2c585ec57ed3c1f5fc371b0af7dfa3c369
|
|
|
|
|
|
|
|
|
|
|
| |
This changeset adds a new typo detector. There
are also some lint infrastructure fixes to better
handle positions within text nodes, and to allow
Eclipse lint quickfixes to supply multiple fixes
for a single issue (such as multiple misspelling
alternative replacements.)
Change-Id: Ie26f0bafc571e02ae09ff27a7f4b221fe0c2ea5b
|
|
|
|
|
|
| |
(cherry picked from commit 93ebf9bf54c3e052a49f68a221b57577e5f602ef)
Change-Id: I3d70a48286674d43a7af6212dabce7053e2e1c7c
|
|
|
|
|
|
|
| |
This allows seeing the library source code in the HTML
report.
Change-Id: I30cd9fa99d2962bb4c12cba6f2ba044857836b93
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They actually were instrumented but the emma output file was not
passed to the report task.
After trying to make each library generate its own .em file and
passing to the report task, I gave up due to FileSet (and the
report task) being stupid.
So the main fix is having the libraries contribute to the main coverage.em
file (since it's build using the merge option) which location is passed
to the library project.
The changes to the custom task was to support querying the libraries for
a path with a given leaf (from the lib root folder) but this is not
used at the moment. The other tasks are slightly cleaned up due to
this though and are getting prepared to support customized folder
names in folder.
Change-Id: Ife59a2971ce6f2acf01b923abe90dea8adee462a
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The location of the .em file was wrong. Changing its location
means it gets put in the tested project so we need a way to know where
the output of the project is.
As we need to be better at supporting customized projects folder, we
introduce a new task that will be able to look for the customized
path of any projects. So far we only support the output folder
and the source folder.
Change-Id: Id8db82e254baae2088827c96b7719f94c92c927c
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a new proguard-android-optimize.txt file alongside the
default proguard-android.txt file in tools/proguard/ which
project.properties files can point to. The shrinking rules
are the same, but unlike proguard-android.txt, the new config
file leave optimization enabled. This allows users to point
to a tool-managed proguard file rather than forking the
default file in order to edit out the -dontoptimize flag.
Change-Id: I2f0fc8361e3964843a4cafe4f4087a6dee68b5ce
|
|
|
|
|
|
|
| |
This is from review comments. I meant to upload
this before commit but forgot.
Change-Id: Ia2eef22f2a5e6a5120110e69b49491a803636768
|
|
|
|
|
|
|
|
|
|
|
| |
Library projects now copy their aidl files into bin/aidl.
Aidl is now called with this import path for all referenced
library projects.
Also added a test project.
Change-Id: I7f94489e87450be67a16ed7198f85b8b472f5025
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to only keep classes that are really used either
through code or through XML. Also tweak the default rules for
better control of animated properties.
Added a test of a custom property animation and fixed some other
misc test files.
Change-Id: I7cc5839a764881d8d3c7bfce0a3f12ea7cba660e
|
|
|
|
|
|
| |
Requires change Ia4caa2a8 from frameworks/base.git
Change-Id: Ifcb469a64146ac2ae65f8516ee9dcfb857a7e2aa
|
|\
| |
| |
| |
| |
| |
| | |
* changes:
Revert the disable flag of the manifest merger to be enable instead.
Minor fixes in Ant.
Manifest merger in Ant build.
|
| |
| |
| |
| | |
Change-Id: I4f89b469e06f741b95b92d7a4826f979c64dab1b
|
| |
| |
| |
| |
| |
| |
| | |
Moved the definition of the custom Ant tasks
into a properties file put in the jar files.
Change-Id: I33b49c9f8f51ffa4f8a8dcaefccc6e0d874a6a9d
|
| |
| |
| |
| |
| |
| |
| | |
This merges the manifest of the libraries into the application's
manifest.
Change-Id: I425e7b75f71d3f50c6422cdb62bb5ec6811ce99d
|
|/
|
|
|
|
|
|
| |
This ensure they are always put in the bin folder
even if the script is run from another folder than
the project one.
Change-Id: Iafda3217f4ddc03f11e8821f089bf855caa99e7d
|
|
|
|
|
|
|
|
| |
Using a custom task to create the filter based on the
app packages for the main project and its library projects and
the list of class to exclude.
Change-Id: Id37862bf53656bd17991b5c307d772ed2019650b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Split NewSetupTask in several tasks to make things more flexible.
Particularly this allows more targets to get access to the project
type (app, lib, test, ...) as it's not so computive intensive.
- Fix test project to give them access to the full tested project's
classpath.
- Fix support for projects that test themselves.
- Make sure library projects are instrumented when using the
emma target.
Change-Id: Ia0c9564eacee2521e7cbd5154b8a85ea287ad4fd
|
|
|
|
| |
Change-Id: I3877a7418da193cbe3759f25daafa3309bb8c05a
|
|\
| |
| |
| |
| | |
* commit '767262f720a14928dc934b26d0f763cdb70fe5ac':
Add 'asset.dir' property to build.xml
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The 'asset.dir' property was available in previous releases.
It was possible to set the assets directory that should be used in
the build process by defining 'asset.dir=../relative/path' in the
ant.properties file. Currently, only the "asset.absolute.dir"
property is available. While one can override this property with a
relative path, the name suggests that this shouldn't be done.
Change-Id: Ia421862c9eb736e3e1dfedaa8bdd4ff3e943941e
|
|/
|
|
| |
Change-Id: I3906416a7b5a4bf7b7e2f86ee3155c22d93a3c2b
|
|
|
|
|
|
|
| |
Also make sure the Renderscript files are rebuilt when the build type
(debug/release) changes.
Change-Id: I688fc3f8550e3133ee32de3ef074efa75ccc3b67
|
|
|
|
|
|
|
|
|
|
| |
JDK7 changes the default signing algorithm and breaks release
builds where the ant script does the signing after building
the apk.
This changes the Ant script to use a custom task that uses
the same code that is already used to sign debug apps.
Change-Id: I0df7378a7a59b54ef6a17db363a2127736f4434e
|
|
|
|
|
|
|
| |
Also tweak the level of our <echo> message which should be of
level INFO but the attribute defaults to WARN
Change-Id: I5f302400e24c250cada8fb883678264b57480615
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I8c6affe825b93eefb7ed60000740aa2783d93a20
|
| |
| |
| |
| | |
Change-Id: I158e85a3c0a831788b11350ea7b33d41d9b5b0a4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the list of jar files was sanitized (to remove
duplicates) in the dex task, but this meant the full list
(with duplicates) was passed to proguard when building in release
mode.
This changeset move the sanitization of the jar files in the
Setup Task so that the script later only deals with a sanitized
list. The means the content of libs/*.jar for the current project
must be looked at in the task instead of later in the XML script.
Change-Id: Ib5253b80ee7c1ded004bcdad6184e0900b7a7543
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Requires dev.git change I250fe7a3 to build properly.
Also requires Change Ia307af09 for addon.
Change-Id: Ib0363f06ce2754c58b5f2ba31c4f0720b933f0d8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the project is a library itself then there's no need to generate
them.
Change-Id: I9896e2bac81979797cca10fc606c66e5139fc9a1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previous change added excluding Manifest and BuildConfig but
made it so that it was only for the current app package.
The problem is that project that depends on libraries also generates
R classes for their libraries.
If the project itself is a library then the R classes from the libraries
would get in the library jar output.
If the main project had some diamond dependencies in its libraries
then the same R class from a library could be added twice to its
dex input causing an error.
Change-Id: I0ef4a3c3f84bf9099de27e275fa856b6c044978d
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
This is done by going through the flat dependency of the main
project and not having the libs look at their own dependencies.
This is similar to what has been done for the regular build steps.
Change-Id: I597c8f931c231c5260cc5b33965b9938fe24c01f
|
|/
|
|
|
|
|
| |
First, their are not needed there, second they can create a dx conflict
if the library uses the same package as the app.
Change-Id: I67b3f478d5d7ab79d02b6ece8b1eae31b8ed104e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Windows, when using java 1.5/1.6 running javac without
fork=true can result in file locking preventing further changes
to them.
This changes sets fork=true in this case (win, java 1.5/1.6).
More info: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6558476
Bug: 24577
Change-Id: I6477ab0615c5a535b2011f2e9f40bc8f818f67a2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changeset splits the proguard.cfg into two halves:
(1) All the general Android settings go into
$ANDROID_SDK/proguard/proguard-android.txt.
This defines shrinking rules like keep custom views, etc. The
crucial point is that this information is maintained and updated
by Tools updates, so whenever new APIs are added to Android, or
whenever bugs are found in the configuration such as flags needed
to work with Dalvik, we can make the updates - we don't have old
snapshots living on in projects.
(2) Any project specific settings go to proguard-project.txt in the
project.
(3) The proguard.config property in project.properties now refers to a
*path* of configuration files, which are all passed to ProGuard in
the given order. The code which processes this setting will
substitute android.sdk.home and user.home variables, so the path
does not have to be hardcoded to point to the project-android.txt
file.
The default project templates have been updated to include a
commented out configuration setting up proguard as described
above.
The default proguard file name was changed from proguard.cfg to
proguard-project.txt such that it can be directly opened in Eclipse
and to make it clear it's an editable text file.
Lint was updated to find the Proguard file via the proguard.config
property as well as via the old and new default names for projects not
enabled with ProGuard.
A subsequent CL will add a lint check which identifies projects
containing the old setup (full local configuration) and offer to
replace it with the new setup.
Change-Id: I44b4c97a160114c2382f02f843c95486a0dc9d6b
|
|
|
|
| |
Change-Id: I22b4a05a2fee098aeb83b42101d5585a3933dce0
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This changeset updates the default proguard.cfg file bundled with the
tools.
Change-Id: If7163a3b8855dd88a58a3e83bb05793733764209
|