Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update readme with description and API path #131

Merged
merged 1 commit into from
Jul 14, 2019
Merged

Update readme with description and API path #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Jakarta Security can be built by executing the following from the project root:

``mvn clean package``

The API jar can then be found in /target.
The API jar can then be found in /api/target.

Making Changes
--------------
Expand All @@ -21,4 +21,8 @@ To make changes, fork this repository, make your changes, and submit a pull requ
About Jakarta Security
-------------

For more information about Jakarta Security, see the project web site at [github.com/eclipse-ee4j/security-api](https://github.com/eclipse-ee4j/security-api).
Jakarta Security defines a standard for creating secure Jakarta EE applications in modern application paradigms.
It defines an overarching (end-user targeted) Security API for Jakarta EE Applications.

Jakarta Security builds on the lower level Security SPIs defined by Jakarta Authentication and Jakarta Authorization,
which are both not end-end targeted.