Continued Improvements to Build Toolchain
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, tooling
Research direction
Start by reading the Maven project files and reviewing the existing hygiene PRs mentioned in the issue. Check which properties and plugins are unused or outdated, then inspect module dependency versions for consistency with the project and Scala versions. Done means submitting a focused PR for one of these build improvements; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Description
A few hygiene PRs have already been merged, this issue tracks some additional hygiene improvements. None of these are expected to solve any bugs or vulns, they just improve the build experience. They will be solved across a set of PRs all associated with this issue.
Examples:
- Remove maven property settings that aren't used
- Update/remove old maven plugins (I did some plugin upgrades already, there are more)
use $project.version instead of hardcoded version when referring to other wayang modules as depsDONE- Eliminate build WARNING statements, many are from bad Javadoc
- mismatched versions being used for Jackson, Spark, Hadoop
- use $scala.major.version to pin deps on the right version of Scala
- Dominant language
- Java
- Stars
- 284
- Forks
- 147
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from apache/wayang
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
JavaReservoirSampleOperator returns the whole input when the dataset size is unknownPossibly taken @sasmith-14 claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/wayang#884 · 3 comments ·
Maintainers usually reply within 2 days
-
Record.compareTo() throws ClassCastException when comparing recordsPossibly taken @harshitsingh070 claimed this 69 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Unused parameter in function ProjectionDescriptor.createPojoJavaImplementation()Possibly taken @AliRana30 claimed this 77 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/wayang#732 · 3 comments ·
Maintainers usually reply within 2 days
-
DISCLAIMER and some "(incubating)" references are still around after graduationPossibly taken @sasmith-14 claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 66/100
apache/wayang#895 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jenkins-infra/plugin-modernizer-tool#2070 · 1 comment ·
Maintainers usually reply within 1 day
-
Event search answers 500 when calendars, attendees or organizers holds a null elementMay be free again A pull request for this issue was closed without being merged. Openai-driven-qa bug Minor
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
linagora/twake-calendar-side-service#1615 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
eclipse-tradista/tradista#371 ·
Maintainers usually reply within 1 day
-
critical
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mars-sim/mars-sim#2199 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
projeto-ong-amar/projeto-ong-amar-backend#26 ·
Maintainers usually reply within 1 day