Support token with jira-report
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- authentication, build-system
Research direction
Start with the authentication and client setup in src/main/java/org/apache/maven/plugins/changes/jira/RestJiraDownloader.java around lines 415-420 and 753, then compare the older implementation linked in the issue. Trace how jira-report currently authenticates and identify the relevant project checks. Done means the report supports token-only authentication without relying on the removed maintain-session context.
Written by the indexing model from the issue text.
Description
New feature, improvement proposal
jira-report auth regression in the 3.x milestone
The auth support in the jira-report has room for improvement. Similar to #86 the jira-report should be changed to support tokens only. Atlassian has similarly deprecated basic auth.
This looks to no longer be true, auth can be required on this endpoint.
https://github.com/apache/maven-changes-plugin/blob/25fb83c96d6d9f3333ef205974b1cd89aded650c/src/main/java/org/apache/maven/plugins/changes/jira/RestJiraDownloader.java#L415-L420
The client setup looks to have removed the maintain session context when uplifted. Which if the report is changed to token only, would no longer be relevant.
https://github.com/apache/maven-changes-plugin/blob/25fb83c96d6d9f3333ef205974b1cd89aded650c/src/main/java/org/apache/maven/plugins/changes/jira/RestJiraDownloader.java#L753
- Dominant language
- Java
- Stars
- 15
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 7
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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/maven-changes-plugin
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#633 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
apache/maven-changes-plugin#619 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/maven-changes-plugin#610 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
apache/maven-changes-plugin#608 ·
-
NullPointerException: Cannot invoke "java.lang.CharSequence.toString()" because "target" is nullOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#130 · 1 comment ·
All issues in apache/maven-changes-plugin
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/notes-android#3367 ·
Maintainers usually reply within 1 day
-
:wave: team-triage a:chore in:isolated-projects in:kotlin-dsl
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day