TimefoldAI / TimefoldAI/timefold-solver
Solver Core: split up gizmo generation and gizmo runtime code in seperate packages
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 228
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 46
Description
The gizmo generated runtime code should not import io.gizmo.
The (MemberAccessor)Factory should generate the bytecode for non-quarkus cases and require gizmo on classpath at runtime.
Quarkus does that during the build, so no need for gizmo on the classpath.
The code generating code and the runtime code must be in separate packages (runtime/deployment?)
Related issues:
- GizmoMemberDescriptor naming. It does not extend MemberDescriptor.
- GizmoClassLoader naming. It's part of Timefold.
- ...
Contributor 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.
Assessment
This issue has not been assessed yet.