Explore converging builder and library java projects
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Review the builder and library Java projects for the duplicated DMN-related code, then read the linked Kogito examples pom.xml for a multi-module dependency pattern. Done should be a concrete, agreed direction for sharing the code or structuring dependencies; the issue does not define an implementation target.
Written by the indexing model from the issue text.
Description
I have started to notice that we are duplicating some of the - especially DMN-related - code. Perhaps we could explore how to share the code between the two APIs... I don't really know how to do this in Java, but it might make sense to explore dependencies in general, because one thing that I imagine is that we should - eventually - have the ability to package up checks/benefits into plugins/packages that can be added to a universal core; this is the dream of fostering a community-developed library for different localities/types of benefits/etc.
Example multi-module java project:
https://github.com/apache/incubator-kie-kogito-examples/blob/main/pom.xml
- Dominant language
- Java
- Stars
- 16
- Forks
- 5
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 23
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 CodeForPhilly/benefit-decision-toolkit
-
documentation Good for newcomer quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#519 ·
Maintainers usually reply within 1 day
-
documentation quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#445 ·
Maintainers usually reply within 1 day
-
Make issue templatesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CodeForPhilly/benefit-decision-toolkit#425 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
CodeForPhilly/benefit-decision-toolkit#525 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CodeForPhilly/benefit-decision-toolkit#524 ·
Maintainers usually reply within 1 day
All issues in CodeForPhilly/benefit-decision-toolkit
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
apache/arrow-java#1311 ·
Maintainers usually reply within 2 days
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
IBM/networking-java-sdk#204 ·
-
bug Technical Debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
avniproject/avni-server#1080 ·