GitLab

Change-Id: I4dac34f88b23484643bce31e5f25ac6eb1fea426

Jar arg list file can not handle correctly if file name with "#" in it
is not quoted.
Also change to use a module specific tmp directory, instead of out/tmp.

Change-Id: I2b73f0826f845381a8457f0d342c736bea33a7c2

I think this was left in by accident from the days when we had tests in the
same package as the classes they were testing.

Change-Id: I45901714c33007aba139b22bfb7b660f038a1883

cp ~/android/dalvik/profiler/src/main/java/dalvik/profiler/* ~/android/master/libcore/dalvik/src/main/java/dalvik/system/profiler/
cp ~/android/dalvik/profiler/src/test/java/dalvik/profiler/* ~/android/master/libcore/dalvik/src/test/java/dalvik/system/profiler/
perl -p -i -e 's/package dalvik.profiler;/package dalvik.system.profiler;/' ~/android/master/libcore/dalvik/src/*/java/dalvik/system/profiler/*.java
perl -p -i -e 's/import dalvik.profiler./import dalvik.system.profiler./' ~/android/master/libcore/dalvik/src/*/java/dalvik/system/profiler/*.java

Change-Id: Iae3f63327f4a9dde7f037e69c22057e2ea704aaa

Change-Id: If02a0973eb7ba0291a75397dda5f221b810890de

Change-Id: I1782aa53b05b959100c9fe3a55a718121e3b0f58

Change-Id: I825ef2ed2fa3b277c12566f0e900e86d3e140cbb

Change-Id: I9df312fc2f887372e3fdb35863fa572020eb36f2

Summary:
- rewrote CollectAllTests to not depend on now deleted AllTests
- flattened core-tests into one static jar (enh)
- used static lib in cts build process

Details:

build

    allow static libraries to contain resources
    used by core-tests module
	core/java_library.mk

    collapse CTS_CORE_CASE_LIST to android.core.tests.libcore
    change generate-core-test-description to take a jar of tests to run instead of an AllTests class name
    move common options from callers of generate-core-test-description to its definition
    updated classpath for running generate-core-test-description for libcore tests
	core/tasks/cts.mk

cts

    Restore temporarily disabled cts build
	tests/core/Android.mk

    Updated BUILD_CTSCORE_PACKAGE
    - don't overwrite LOCAL_STATIC_JAVA_LIBRARIES, just append to it so we can use a static library to build android.core.tests.libcore
    - clarify some comments
    - change some @ to $(hide) to clarify operations in showcommands
    - update rules now that input is a static library
	tests/core/ctscore.mk

    New android.core.tests.libcore built from static core-tests library
    Note dummy file is necessary for build to process static library into an APK.
    I first tried to change build to allow a package with only a static library
    but it would require changing how static libraries are packed in to APK,
    which right now is done at the time Java sources are compiled.
	tests/core/libcore/Android.mk
	tests/core/libcore/AndroidManifest.xml
	tests/core/libcore/src/Dummy.java

    Removing old core-tests packages
	tests/core/dom/Android.mk
	tests/core/dom/AndroidManifest.xml
	tests/core/luni-io/Android.mk
	tests/core/luni-io/AndroidManifest.xml
	tests/core/luni-lang/Android.mk
	tests/core/luni-lang/AndroidManifest.xml
	tests/core/luni-net/Android.mk
	tests/core/luni-net/AndroidManifest.xml
	tests/core/luni-util/Android.mk
	tests/core/luni-util/AndroidManifest.xml
	tests/core/xml/Android.mk
	tests/core/xml/AndroidManifest.xml

     Rewrite of logic in CollectAllTests for finding tests to run.
     Previously it acted as a JUnit TestRunner for a specific TestSuite,
     with the runner modified to do no-op runs just to collect the names of tests.
     Now it takes a jar file argument and walks the entries looking for TestCase
     classes and then walking the methods to find the tests.

	tools/utils/CollectAllTests.java

libcore

    fix all-test-java-files-under to work like all-main-java-files-under (to support multiple directories)
    flatten separate core-tests-* into core-tests
    make core-tests a static Java library, avoiding dex overhead (which will only now be done when building CTS packages)
    remove old RI core-tests.jar build which seems obsolete given our use of vogar
    removd core-tests-supportlib since core-tests can now be used in its place

	JavaLibrary.mk

frameworks/base

    Change tracking move from core-tests-supportlib to core-tests

	core/tests/coretests/Android.mk

Change-Id: Id5d965dd96d257544ce27a1e0fcde65901e9c573

Change-Id: I9c83326d36232233b86891a607e8c581c1b0d27a

Change-Id: I1ac2e099f4b8c5002e24eb18a3b14cdc193e610f
http://b/3351604

Change-Id: I482ba29551423c682696db44f78bc6b74fa04341
http://b/1414929

Add a local droiddoc target that cuts the review time for javadoc
changes from several minutes to less than a minute.

Docs.mk is the list of directories to javadoc within libcore that was
refactored from frameworks/base/Android.mk

Change-Id: I5c12b48e71b849c2883ebaafaddea5f6c6dea857

Actually, this is more of a workaround. The real fix would be:

1. work out why @SuppressWarnings("unchecked") isn't working.
2. move the XML crap (which we're not maintaining, and where we don't fix
   warnings) out into external/.
3. uncomment the commented-out line in this patch.

(I've fixed our real non-"unchecked" warnings in earlier patches.)

Change-Id: I5a2dcb071eef5b46c8f166f9492d56cfdb5c6fa5

Bug: 3087671
Change-Id: I95eb77ea66e289c9ea1c6106b4eb4654ca15215d

Change-Id: Iac339144ed448848c96852da8d301d528ebfa0e6

Change-Id: Iadd023fbc4f11b10d1f76c92c1cfad7ff21dde97

Uses LOCAL_BUILD_HOST_DEX:=true to do the heavy lifting.

See Ying Wang's example, which this obsoletes:
  https://android-git.corp.google.com/g/67581

Change-Id: I7ebfd7033e130280e473b1a42624c5d375d7eaed

Summary:
- libcore: new Java based SamplingProfiler
- dalvik: remove old SamplingProfiler native bits
- frameworks/base: New placeholder SamplingProfilerIntegration
- vendor/google: remove old profiler snapshot parsing code

Details:

libcore

   A new 100% Java SamplingProfiler. While it has more overhead that
   the old native one, the new one can actually collect more than the
   current PC and frame pointer, so you can get useful context of
   where your app is spending time. It currently provides ASCII hprof
   format output for use with tools like PerfAnal
	dalvik/src/main/java/dalvik/system/SamplingProfiler.java

    Unit test for the new SamplingProfiler
	dalvik/src/test/java/dalvik/system/SamplingProfilerTest.java

    Add core-tests-dalvik
	JavaLibrary.mk

dalvik

    Removing native code that supported the old SamplingProfiler
	vm/Dvm.mk
	vm/native/InternalNative.c
	vm/native/dalvik_system_SamplingProfiler.c

frameworks/base

  Placeholder SamplingProfilerIntegration. Later plans include
  generating EventStackTrace protobufs.

    New SamplingProfiler does not have a global instance, so
    SamplingProfilerIntegration provides one in INSTANCE. Old binary
    snapshot format is temporily replaced with ASCII hprof data.
	core/java/com/android/internal/os/SamplingProfilerIntegration.java

    Simplified interface for zygote profile snapshotting
	core/java/com/android/internal/os/ZygoteInit.java

    Current SamplingProfilerIntegration does not track event loop
    explicitly, but hprof information does include thread information.
	core/java/android/app/ActivityThread.java

vendor/google

    Removing code for parsing old SamplingProfiler snapshot format
	tools/samplingprofiler/Android.mk
	tools/samplingprofiler/NOTICE
	tools/samplingprofiler/profiler.iml
	tools/samplingprofiler/profiler.ipr
	tools/samplingprofiler/pull-snapshots.sh
	tools/samplingprofiler/sorttable.js
	tools/samplingprofiler/src/com/android/profiler/PrintHtml.java

Summary:
- libcore: new Java based SamplingProfiler
- dalvik: remove old SamplingProfiler native bits
- frameworks/base: New placeholder SamplingProfilerIntegration
- vendor/google: remove old profiler snapshot parsing code

Details:

libcore

   A new 100% Java SamplingProfiler. While it has more overhead that
   the old native one, the new one can actually collect more than the
   current PC and frame pointer, so you can get useful context of
   where your app is spending time. It currently provides ASCII hprof
   format output for use with tools like PerfAnal
	dalvik/src/main/java/dalvik/system/SamplingProfiler.java

    Unit test for the new SamplingProfiler
	dalvik/src/test/java/dalvik/system/SamplingProfilerTest.java

    Add core-tests-dalvik
	JavaLibrary.mk

dalvik

    Removing native code that supported the old SamplingProfiler
	vm/Dvm.mk
	vm/native/InternalNative.c
	vm/native/dalvik_system_SamplingProfiler.c

frameworks/base

  Placeholder SamplingProfilerIntegration. Later plans include
  generating EventStackTrace protobufs.

    New SamplingProfiler does not have a global instance, so
    SamplingProfilerIntegration provides one in INSTANCE. Old binary
    snapshot format is temporily replaced with ASCII hprof data.
	core/java/com/android/internal/os/SamplingProfilerIntegration.java

    Simplified interface for zygote profile snapshotting
	core/java/com/android/internal/os/ZygoteInit.java

    Current SamplingProfilerIntegration does not track event loop
    explicitly, but hprof information does include thread information.
	core/java/android/app/ActivityThread.java

vendor/google

    Removing code for parsing old SamplingProfiler snapshot format
	tools/samplingprofiler/Android.mk
	tools/samplingprofiler/NOTICE
	tools/samplingprofiler/profiler.iml
	tools/samplingprofiler/profiler.ipr
	tools/samplingprofiler/pull-snapshots.sh
	tools/samplingprofiler/sorttable.js
	tools/samplingprofiler/src/com/android/profiler/PrintHtml.java

Change-Id: I4a7d7b86b45a806021249c83ab32e52d3d53f33c

external/bouncycastle
- Change to be the primary build for bouncycastle sources (as opposed to part of libcore)
- Moved OpenSSLMessageDigest from libcore to OpenSSLDigest
  It uses NativeCrypto API from core, but implements a bouncycastle specific interface
- restored registration of bouncycastle MessageDigests for SHA-1, SHA-256, MD5
  OpenSSLProvider versions take precedence, but explicit provider of "BC" allows choice
- enabled native versions of SHA-384 and SHA-512
- pruned MD4 implementation

frameworks/base
- frameworks and CoreTests modules now depend on bouncycastle
- update preloades classes for NativeBN package change
- moved CryptoTest to libcore

libcore
- core now builds without bouncycastle sources
- core-tests, core-tests-support, core-tests-supportlib now depend on bouncycastle
- removed libcore/openssl directory, moving NativeBN to java/math
- minor cleanup of Provider, Security, Services style while working on ProviderTest
- added new OpenSSLProvider registered as first provider to have
  priority over the others to ensure our native implementations are used
- moved BouncyCastle to have priority as a provider over Harmony
- JarVerifier and JarUtils now implicitly use OpenSSLMessageDigest
- Cleanedup OpenSSLSignature, implementation needs to be finished to move to OpenSSLProvider
- To avoid using PEMWriter from BouncyCastle, NativeCrypto now takes binary encoded certs and keys
  This is more efficient as well avoiding the base64 decode/encode of the binary data
- removed SHA-224 to match the RI

packages/apps/CertInstaller
- CertificateInstaller module now depends on bouncycastle
  this is the only app to depend on bouncycastle

system/core
- updated BOOTCLASSPATH

Change-Id: I6205366b12baec4331b4a76e2c85d8324bf64b2c

libcore/luni/src/main/java/org/bouncycastle moved to external/bouncycastle/src/main/java/org/bouncycastle

Change-Id: I288db1607ad6f45dea71e7496d4d94c9707779f6

Bouncy Castle has UTF-8 javadoc, but we also want this for character examples

Change-Id: I734890ddafc49bcf2ce71c60947e9cf4c95712b2

libcore/luni/src/main/java/org/bouncycastle moved to external/bouncycastle/src/main/java/org/bouncycastle

Change-Id: Ic8d81f1c057458e9fdf9b648c9d976a552b785b8

Change-Id: Ib9484dd4caca75ae662be9baa887adb387f583fc

Also exposing core-tests-support for use by tests in frameworks/base.
I'm not particularly happy about this, but it seems to be the best
way to share test support code between the two build targets.

Change-Id: I5e8dcac90fc5d9be791e46c2606498978212108e

Change-Id: I6a739028c4c7bcda12b905116166e119720e69c2

Change-Id: I4d4287a7d91ba39e97fd907eae9fd0c93e026d02
I8e65d375: no emma instrumentation on core-test
I09725483: include emma into core library on conditional flag

Adapted from master:
  https://android-git.corp.google.com/g/50612

Change-Id: I24cde108f1dd70532ff217545445cdc0b2650a48

This cherry picks the critical parts of enh's original change:
7ee3a061

This is a stopgap fix; eventually when dalvik-dev's changes
are committed to master this should be obsolete.

Change-Id: Ieb04253fb7387ffa37452992c8a5af739fbbc45f

Previously it wasn't possible to start a dalvikvm without
a copy of JUnit on the boot class path.

Change-Id: I52f924207efe0a115e69616111807c6738d1a17f
https://android-git.corp.google.com/g/#change,50609
https://android-git.corp.google.com/g/#change,50610
https://android-git.corp.google.com/g/#change,50611

Merge xml except xmlpull and kxml into luni

Change-Id: I0dcadda241e7fd2a7429f9dd43d1ff5e945e5467

* applying emma instrumentation causes OOM in dx
* test packages don't need emma instrumentation anyway, it's the
  package under test that needs to be processed by emma

Change-Id: I8e65d3750aae716c52fb98d0b8cd41a748344516

Change-Id: Ib4356b3cd57490df8ff246ea6a4bc1c269ba848b

Also move our ICU tests into our little tree of tests.

Bug: 2596471
Change-Id: I73b53d74c26ef9bf670f12cac58b51ba61eefead

emma library is used for collecting code coverage. Current pain point is that
for collecting code coverage, developers either need to include emma as a
local static library, or change BOOTCLASSPATH to include emma which includes
hacking boot image and reflashing it.

With this change, emma will be integrated into core.jar if EMMA_INSTRUMENT flag
is on, so pushing the updated framework.jar and perform a runtime restart will
make emma globally available to all code coverage tests.

This change will only affect code coverage builds.

Change-Id: I097254835ef4817d068e8946ecbec60135e1f515

The JDBC driver is from a different source
(http://www.ch-werner.de/javasqlite/overview-summary.html) and is only
really needed for testing.

Bug 2468870 asks that we don't eagerly register the native methods for
these classes. That bug is fixed by this change.

Bug 2198667 asks that we stop shipping this JDBC driver as part of the
base system. That bug is not addressed by this change: the classes and
native code are now in their own, separate, .jar and .so files -- so
they'll be easier to remove in future -- but for now those files are
still in /system/framework and /system/lib respectively.

Bug: 2468870
Bug: 2198667

(I removed the unused parameter from the wrong macro!)