slackapi / slackapi/java-slack-sdk
Jakarta EE support in Slack Java SDK
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 602
- Forks
- 232
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 7
Description
I'm trying to migrate Java EE to Jakarta EE for some reason (e.g. native-image, spring 6).
This project has example code for many platform.
It's good for SDK users, but it includes some problems.
Now, some projects depends javax namespace, some other projects depends jakarta namespace.
(e.g. Jetty already migrated. Quarkus desided to stay javax)
So, I propose to separate example code from this project before Jakarta EE migration.
How do you think about this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named; start by reviewing the project’s example code and its javax and jakarta dependencies. Done means producing an agreed separation of the examples that supports the proposed Jakarta EE migration without leaving the existing namespace users unclear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100