| /external/proguard/examples/ |
| servlets.pro | 7 # Specify the input jars, output jars, and library jars.
|
| /prebuilts/tools/common/proguard/proguard4.7/examples/ant/ |
| applets.xml | 14 <!-- Specify the input jars, output jars, and library jars. -->
|
| applications2.xml | 13 <!-- Specify the input jars, output jars, and library jars. -->
|
| proguard.xml | 17 <!-- Specify the input jars, output jars, and library jars. -->
|
| servlets.xml | 14 <!-- Specify the input jars, output jars, and library jars. -->
|
| /prebuilts/tools/common/proguard/proguard4.7/examples/ |
| applets.pro | 7 # Specify the input jars, output jars, and library jars.
|
| applications.pro | 7 # Specify the input jars, output jars, and library jars.
|
| library.pro | 8 # Specify the input jars, output jars, and library jars.
|
| servlets.pro | 7 # Specify the input jars, output jars, and library jars.
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/ |
| build.properties | 25 jars.compile.order = performanceui.jar
|
| /external/jacoco/org.jacoco.doc/javadoc/ |
| overview.html | 8 regular JARs in your classpath.
|
| /external/proguard/examples/ant/ |
| proguard.xml | 17 <!-- Specify the input jars, output jars, and library jars. -->
76 <!-- If we have the Gradle jars, we can properly process the Gradle task. -->
|
| /external/proguard/examples/gradle/ |
| proguard.gradle | 28 // Specify the input jars, output jars, and library jars.
75 // jars.
|
| /external/proguard/src/proguard/ |
| DataEntryReaderFactory.java | 31 * The readers will unwrap the input data entries from any jars, wars, ears,
96 // Unzip any jars, if necessary.
132 // Unzip any jars, if necessary.
151 // Only unzip the right type of jars.
|
| UpToDateChecker.java | 46 * of the input jars, output jars, and library jars (or directories).
59 // Check the dates of the program jars, if any.
72 // Check the dates of the library jars, if any.
|
| /external/slf4j/log4j-over-slf4j/compatibility/ |
| readme.txt | 9 logback jars instead.
|
| /cts/tools/tradefed-host/tests/ |
| run_unit_func_tests.sh | 40 JARS="tradefed-prebuilt.jar hosttestlib.jar old-cts-tradefed.jar old-cts-tradefed-tests.jar"
42 for JAR in $JARS; do
|
| run_unit_tests.sh | 40 JARS="tradefed-prebuilt.jar hosttestlib.jar old-cts-tradefed.jar old-cts-tradefed-tests.jar"
42 for JAR in $JARS; do
|
| /external/deqp/android/cts/runner/tests/ |
| run_tests.sh | 43 JARS="
52 for JAR in $JARS; do
|
| /external/robolectric/v3/ |
| build.gradle | 3 // Create an implicit target which is a collection of jars
30 // Jars built by the Robolectric team used across all
|
| /frameworks/base/cmds/uiautomator/cmds/uiautomator/src/com/android/commands/uiautomator/ |
| RunTestCommand.java | 42 private static final String JARS_PARAM = "jars";
188 * Add test classes from jars passed on the command line. Use this if nothing was explicitly
192 String jars = mParams.getString(JARS_PARAM); local
193 if (jars == null) return;
195 String[] jarFileNames = jars.split(JARS_SEPARATOR);
233 + " <class spec>: <JARS> < -c <CLASSES> | -e class <CLASSES> >\n"
234 + " <JARS>: a list of jar files containing test classes and dependencies. If\n"
241 + " all the tests in provided jars will be run automatically.\n"
|
| /sdk/eclipse/scripts/ |
| build_adt.sh | 37 # 2. Copy dependent jars into the libs folder of each plugin
38 echo Copying jars to be embedded inside the ADT plugins
|
| /external/proguard/docs/manual/ |
| introduction.html | 43 <td rowspan="4" class="lightblock">Input jars</td>
57 <td rowspan="2" class="lightblock">Output jars</td>
69 <td class="darkblock">Library jars</td>
71 <td class="darkblock">Library jars</td>
77 ProGuard first reads the <b>input jars</b> (or aars, wars, ears, zips, apks,
81 more <b>output jars</b> (or aars, wars, ears, zips, apks, or directories). The
85 ProGuard requires the <b>library jars</b> (or aars, wars, ears, zips, apks, or
86 directories) of the input jars to be specified. These are essentially the
89 The library jars themselves always remain unchanged. You should still put them
|
| /prebuilts/tools/common/proguard/proguard4.7/docs/manual/ |
| introduction.html | 42 <td rowspan="4" class="lightblock">Input jars</td>
56 <td rowspan="2" class="lightblock">Output jars</td>
68 <td class="darkblock">Library jars</td>
70 <td class="darkblock">Library jars</td>
76 ProGuard typically reads the <b>input jars</b> (or wars, ears, zips, or
80 one or more <b>output jars</b> (or wars, ears, zips, or directories). The
84 ProGuard requires the <b>library jars</b> (or wars, ears, zips, or
85 directories) of the input jars to be specified. These are essentially the
88 The library jars themselves always remain unchanged. You should still put them
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/builderTemplate/componentScripts/ |
| build.properties | 15 # bootclasspath - The base jars to compile against (typicaly rt.jar)
108 # The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
120 # Whether or not to include debug info in the output jars
126 # Sets the value of the -source command line switch for javac version 1.4. Used when compiling the jars for the plug-ins.
132 # Sets the value of the -target command line switch for javac. Used when compiling the jars for the plug-ins.
|
