feat: Align exception types to Jakarta 3.1 specification
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
The issue title references aligning exception types to the Jakarta 3.1 specification. Research the Jakarta Messaging 3.1 spec to understand the required exception types. Look at the existing exception classes in the ActiveMQ codebase, likely in a package like org.apache.activemq or a subpackage. Compare them to the spec and plan the changes needed. Testing will involve ensuring the new or updated exceptions are thrown correctly in relevant scenarios.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1.5k
- Avg merge
- 9h 25m
- Merged PRs (30d)
- 81
Contributor guide
No contributing guide indexed for this repository
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.
More from apache/activemq
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Stale
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
inu-appcenter/memorIN-backend#288 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
frontend maui-pilot pilot-ask question
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area/plugin
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kestra-io/plugin-kestra#190 ·