File: control

package info (click to toggle)
jtreg7 7.5.1%2B1%2Bds1-3
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 51,224 kB
  • sloc: java: 409,123; xml: 8,266; sh: 1,966; ansic: 1,084; exp: 689; makefile: 387; javascript: 162; cpp: 120
file content (69 lines) | stat: -rw-r--r-- 1,742 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Source: jtreg7
Section: java
Priority: optional
Maintainer: Vladimir Petko <vladimir.petko@canonical.com>
Uploaders: Matthias Klose <doko@debian.org>
Build-Depends:
 ant,
 debhelper (>=11),
 default-jdk,
 help2man,
 javahelp2,
 javahelper,
 libasmtools-java,
 libjcommander-java,
 libslf4j-java,
 libguice-java,
 libjline2-java,
 zip,
 libjansi-native-java (>= 1.7),
 libmaven-bundle-plugin-java,
 maven-repo-helper,
 maven-debian-helper,
 gradle-debian-helper (>= 1.4),
 groovy (>= 2.4.10),
 libjna-java,
 libjuniversalchardet-java,
 libmaven-dependency-plugin-java,
 libmaven-source-plugin-java,
 libbuild-helper-maven-plugin-java,
 junit,
 libeasymock-java,
 libjmock-java,
 rsync,
 libmaven-shade-plugin-java,
 libassertj-core-java,
 libjtharness-java (>= 6.0),
 libyaml-snake-java,
 libfindbugs-java,
 libbsh-java,
 libasm-java,
 libcommons-lang-java,
 libmaven-plugin-tools-java,
 libplexus-component-metadata-java,
 libxbean-java,
Standards-Version: 4.6.2
Vcs-Git: https://salsa.debian.org/java-team/jtreg7.git
Vcs-Browser: https://salsa.debian.org/java-team/jtreg7
Homepage: https://openjdk.java.net/jtreg
Rules-Requires-Root: no

Package: jtreg7
Architecture: all
Depends:
 ${java:Depends},
 ${misc:Depends},
 javahelp2,
 libjtharness-java (>= 6.0),
 libxalan2-java,
 libasmtools-java,
 libjcommander-java,
 libslf4j-java,
 libguice-java,
Conflicts: jtreg, jtreg6
Description: Regression Test Harness for the OpenJDK platform
 jtreg is the test harness used by the OpenJDK test framework.
 This framework is intended primarily for regression tests.
 It can also be used for unit tests, functional tests, and even simple product
 tests -- in other words, just about any type of test except a conformance test,
 which belong in a TCK.