Closed jcputney closed 7 months ago
@xeno6696 and @jeremiahjstacey - I will approve this after my PR #809 gets merged. If it gets merged now, I think it likely will cause merge conflicts.
If this worked, it may be good to go update the README to reflect that this JAR now exists and is published to maven central?
It did work. I mentioned it in the release notes and on the Discussion
for the suggestion.
-kevin
On Tue, Jan 30, 2024, 3:45 PM Jonathan Leitschuh @.***> wrote:
If this worked, it may be good to go update the README to reflect that this JAR now exists and is published to maven central?
— Reply to this email directly, view it on GitHub https://github.com/ESAPI/esapi-java-legacy/pull/799#issuecomment-1917863840, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO6PGZNGQBC5G3IUTYUPETYRFLXXAVCNFSM6AAAAAA4QTTABSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJXHA3DGOBUGA . You are receiving this because you modified the open/close state.Message ID: @.***>
This PR adds a Maven profile called "jakarta" that will generate a transformed JAR file, compatible with the
jakarta.servlet
changes for Jakarta EE 9+I don't know how you public packages, and I doubt this is a full solution, but it at least gets you pointed in the right direction.