-
Notifications
You must be signed in to change notification settings - Fork 30
/
config.inc
67 lines (50 loc) · 3.39 KB
/
config.inc
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
///////////////////////////////////////////////////////////////////////
NOTE TO WRITERS:
The following sections should be customized for the technology.
This text was originally from the Jakarta RESTful Web Services TCK. Most references
to Jakarta RESTful Web Services have been parameterized to serve as a simple starting
point for customization. There are still many details that will
need to be changed or removed. The major sections 4.1, 4.2, and
4.3 should be preserved. If their titles are changed, the links
at the top of config.adoc will need to be changed as well as well
as toc.adoc.
///////////////////////////////////////////////////////////////////////
[[GBFVU]][[configuring-your-environment-to-run-the-tck-against-the-reference-implementation]]
[NOTE]
=======================================================================
In these instructions, variables in angle brackets need to be expanded
for each platform. For example, `<JAVA_HOME>` becomes `$JAVA_HOME` on
Solaris/Linux and `%JAVA_HOME%` on Windows. In addition, the forward
slashes (`/`) used in all of the examples need to be replaced with
backslashes (`\`) for Windows. Finally, be sure to use the appropriate
separator for your operating system when specifying multiple path
entries (`;` on Windows, `:` on UNIX/Linux).
On Windows, you must escape any backslashes with an extra backslash in
path separators used in any of the following properties, or use forward
slashes as a path separator instead.
=======================================================================
4.1 Download the Jakarta Authentication TCK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Jakarta Authentication TCK is retrieved from
```
https://download.eclipse.org/jakartaee/authentication/3.0/jakarta-authentication-tck-3.0.1.zip
```
4.2 Setting up an Evironment for the Maven Surefire based TCK Against a Compatible Implementation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The current JUnit based set of tests runs under a Maven surefire runner and needs a profile configured for your compatible
implementation to test. The top level tck/pom.xml includes example profiles including one for GlassFish. To configuration a
profile for your compatible implementation, start with the GlassFish glassfish-ci-managed profile, and modify the dependencies
and configuration to support your implementation and Arqulillian container implementation. The Arqulillian container implementation
starts up your container and deploys the test wars into it.
4.3 Setting up an Evironment Against a Jakarta EE {JakartaEEVersion} CI for legacy TCK tests
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The legacy tests which are part of the latest Jakarta Authentication TCK use `KEYWORDS` parameter to identify the
tests that need to be executed for JakartaEE Full and Web profile implementations. The tck/old-tck/run/pom.xml includes
example of using the profiles `platform` (for JakartaEE Platform - Full profile by default) and `web` (for Web Profile)
that sets the appropirate values for `KEYWORDS` in the CI.
```
For JakartaEE Platform Full profile , KEYWORDS = jaspic_baseline|javaee
For JakartaEE Platform Web platform , KEYWORDS = jaspic_web_profile
```
The `tck/old-tck/source/src/com/sun/ts/lib/harness/keyword.properties` has the full list of keywords
mapped to the test directories in tck/old-tck/