summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorPaul Duffin <paulduffin@google.com>2016-11-21 15:26:00 +0000
committerPaul Duffin <paulduffin@google.com>2016-11-22 12:27:53 +0000
commit0342ab5b9447481ad82740dde01595bf3c288e15 (patch)
treee6bec185c8117cd62fb0baaebb8a7591c90789c2 /tools/aapt2/java/JavaClassGenerator_test.cpp
parentc6c005ef5b927be1b49b4d18a0b887b571fb3ca4 (diff)
Move JUnit classes from here into external/junit
Checked that android.test.runner had the same classes in as before the change. These classes are legacy 3.8.1 classes, they are not in 4.10 at all. They appear to have been left here by accident. Looking at the history it appears that at one time there were copies of JUnit 3.8.1 junit.runner classes in frameworks and external/junit. The classes here were upgraded to 4.10 but even though these classes had been deleted immediately after 3.8.2 was released they were not removed, instead they appear to have been reformatted as part of the upgrade. The external/junit source was upgraded to 4.10 about two weeks later which seems to have been done correctly. About three months after that the classes here that were duplicates of those in external/junit were removed from here leaving the legacy classes from 3.8.1. I could not find any usages of these classes and they are not in the public API so they can probably be removed altogether. However, for now I will simply move them into external/junit as described and remove them when upgrading JUnit there to 4.12. Bug: 30188076 Test: Built android.test.runner and checkapi Change-Id: I88687889315c041d999fe7e61b9652ac8406165c
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions