Use version field in plugin classpath definition
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system
Research direction
Start with the plugin classpath definition and its version field, using pull request 90 for the relevant context. Trace where the plugin version is currently declared and identify the duplicated value; done means the classpath definition uses the single existing version field without duplication.
Written by the indexing model from the issue text.
Description
See https://github.com/canonical/devpack-for-spring/pull/90 - the version for the plugin should be defined in a single place, it should not be duplicated in the version field.
- Dominant language
- Java
- Stars
- 6
- Forks
- 5
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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 canonical/devpack-for-spring
-
Dependency DashboardOpen
Difficulty 3/5 1-2 days Newbie friendliness 20/100
All issues in canonical/devpack-for-spring
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
checkstyle/checkstyle#22145 ·
Maintainers usually reply within 1 day
-
rset command throws NPE in ResultsFormat.guessSyntaxPossibly taken @Ostrzyciel claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
objectionary/eo#9593 ·
Maintainers usually reply within 1 day
-
release bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/open-liberty#36124 ·
Maintainers usually reply within 1 day