-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #90 from Pandrex247/FISH-10024-Use-Zips-EE10-Squash
FISH-10024 FISH-10044 Download and Use Zips (EE10)
- Loading branch information
Showing
62 changed files
with
2,255 additions
and
2,245 deletions.
There are no files selected for viewing
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,11 @@ | ||
[submodule "inject-tck/ditck-porting"] | ||
path = inject-tck/ditck-porting | ||
url = https://github.com/payara/ditck-porting | ||
branch = EE10 | ||
[submodule "cdi-tck/glassfish-cdi-porting-tck"] | ||
path = cdi-tck/glassfish-cdi-porting-tck | ||
url = https://github.com/payara/glassfish-cdi-porting-tck | ||
[submodule "cdi-tck/cditck-porting"] | ||
path = cdi-tck/cditck-porting | ||
url = https://github.com/payara/cditck-porting | ||
branch = EE10 | ||
[submodule "inject-tck/ditck-porting"] | ||
path = inject-tck/ditck-porting | ||
url = https://github.com/payara/ditck-porting | ||
branch = EE10 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,6 @@ | ||
# jakartaee-10-tck-runners | ||
|
||
## Jakarta JSON Processing | ||
Payara runners for the standalone Jakarta EE TCKs. | ||
See individual module READMEs for details, but general usage is: | ||
|
||
### Prerequisites | ||
To be able to run the TCK test, you need to setup remote Payara Server in order to run the Arquillian against the container | ||
|
||
### Test Executions | ||
**(Make sure the Payara server up and running)** | ||
|
||
Run maven test from jsonp-tck module | ||
|
||
cd jsonp-tck | ||
mvn test | ||
`mvn clean verify -Dpayara.version=${payaraVersion} -Ppayara-server-managed -pl . -pl tck-download -pl tck-download/${tckToRun} -pl ${tckToRun}` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Jakarta Authorization TCK Runner | ||
|
||
## Prerequisite | ||
|
||
Download and install the TCK into your local Maven repo. | ||
From the top-level directory: `mvn clean install -pl . -pl tck-download -pl tck-download/jakarta-authorization-tck -Pjakarta-staging` | ||
|
||
## Test Execution | ||
|
||
To execute the full TCK against a managed Payara Server | ||
|
||
``` | ||
mvn clean verify | ||
``` | ||
|
||
### Debugging | ||
|
||
Utilise the `payara-server-remote` profile. | ||
This profile expects that the TCK has been run in its entirety at least once to perform the necessary setup. | ||
|
||
* Move into the TCK for the rerun: `cd authorization-tck/target/authorization-tck-3.0.0/tck` | ||
* Install the common TCK module (make sure you don't clean!): `mvn install -Ppayara-server-remote,jakarta-staging -pl . -pl common -DskipTests` | ||
* Start the configured Payara Server found at `authorization-tck/target/authorization-tck-3.0.0/tck/target/payara7` and attach your debugger | ||
* Run your specific TCK module test (make sure you don't clean!), for example: `mvn verify -Ppayara-server-remote,jakarta-staging -f app-custom-policy2 -Dit.test=AppCustomPolicy2IT#testAuthenticatedSpecial` |
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.