Skip to content

Commit e942bc3

Browse files
committed
fix spelling
1 parent 6b7d156 commit e942bc3

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ add
150150
```xml
151151
<classifier>jakarta</classifier>
152152
```
153-
and include whatever jakara.servlet:jakarta.servlet-api version you are using with
153+
and include whatever jakarta.servlet:jakarta.servlet-api version you are using with
154154
```xml
155155
<scope>provided</scope>
156156
```

documentation/esapi4java-core-2.5.3.0-release-notes.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This is a patch release with the primary intent of providing a Jakarta compatibl
1616
Encryptor.DigitalSignatureAlgorithm=SHA256withDSA # The old SHA1withDSA doesn't support 2048-bit RSA modulus length
1717
Encryptor.DigitalSignatureKeyLength=2048
1818
Note that if you have persisted previous digital signatures that you must continue to verify, you will have to regenerate them.
19-
* Thanks to a PR by @jcputney (PR #799), I have attempted to upload additional artifacts to Maven Central that will be a transformed jar suitable for use with the new 'jakarata.servlet' changes for Jakarata EE 9 and later. (Previously, 'javax.servlet' was the name space). Because we are still supporting JDK 8 at this point, we still need to support the 'javax.servlet' namespace as well. In addition to the standard jar artifacts, there should be a new esapi-<release>-jakarta.jar (which uses 'jakarta.servlet' instead of 'javax.servlet' namespace) as well as corresponding *-javadoc.jar and *-sources.jar files. I am not sure it will work as we have no tests for it, but looing at the binaries, it seems like it should.
19+
* Thanks to a PR by @jcputney (PR #799), I have attempted to upload additional artifacts to Maven Central that will be a transformed jar suitable for use with the new 'jakarta.servlet' changes for Jakarta EE 9 and later. (Previously, 'javax.servlet' was the name space). Because we are still supporting JDK 8 at this point, we still need to support the 'javax.servlet' namespace as well. In addition to the standard jar artifacts, there should be a new esapi-<release>-jakarta.jar (which uses 'jakarta.servlet' instead of 'javax.servlet' namespace) as well as corresponding *-javadoc.jar and *-sources.jar files. I am not sure it will work as we have no tests for it, but looing at the binaries, it seems like it should.
2020
For additional details, see:
2121
https://github.com/ESAPI/esapi-java-legacy/pull/799
2222
https://github.com/ESAPI/esapi-java-legacy/discussions/768

0 commit comments

Comments
 (0)