nsoft opened a new pull request, #2017:
URL: https://github.com/apache/shiro/pull/2017
This updates main to 3.0-snapshot (so a branch for 2x should be made before
merging). In this PR I tried to use JakartaEE9 where possible with the
exception of spring boot which is forced to JakartaEE 10. Spring never released
an EE9 compatible release because by the time they did an update to Jakarta
namespaces the Tomcat version for EE9 was already EOL, and they elected to skip
EE9 for their test framework. They have EE9 compatibility in the runtime, but
since shiro is using their testing framework, this doesn't help. Guice does
not yet appear to have EE10 support, hence the EE9 focus.
`mvn install`/`mvn verify` pass in this branch, but 13 tests are @Disabled.
All of these tests are Integration tests and the failure mode in all cases is
that the integration infrastructure (meecrowave/openliberty/arquillian) fails
to launch. I am not very familiar with these and most of them are JaxRS/Jakarta
Restful Services related, also a space I don't play in very often. Hopefully
some here will be more familiar and be better able to address these issues.
Following this checklist to help us incorporate your contribution quickly
and easily:
- [x] Make sure there is a [GitHub
issue](https://github.com/apache/shiro/issues) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a GitHub issue. Your pull request should address just this
issue, without pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[#XXX] - Fixes bug in
SessionManager`,
where you replace `#XXX` with the appropriate GitHub issue. Best
practice
is to use the GitHub issue title in the pull request title and in the
first line of the commit message.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] add `fixes #XXX` if merging the PR should close a related issue.
- [x] Run `mvn verify` to make sure basic checks pass. A more thorough
check will be performed on your pull request automatically.
- [ ] If you have a group of commits related to the same change, please
squash your commits into one and force push your branch using `git rebase -i`.
- [ ] Committers: Make sure a milestone is set on the PR
Trivial changes like typos do not require a GitHub issue (javadoc,
comments...).
In this case, just format the pull request title like `[DOC] - Add javadoc
in SessionManager`.
If this is your first contribution, you have to read the [Contribution
Guidelines](https://github.com/apache/shiro/blob/master/CONTRIBUTING.md)
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf)
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the [Apache License
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
