Code generation in build process?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 11
- Avg merge
- 8h 6m
- Merged PRs (30d)
- 1
Description
I'm not a fan of the code generation for jlems.model during the build process. Since the types in this repository are meant to be fairly stable now, it would be better to do the one-off schema generation and then a one-off generation of jlems.model from the schema and check it in. Most future schema changes should only add new classes, not modify existing ones.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by inspecting the build process that generates jlems.model and the generated model and schema sources. Determine how the current generation steps are invoked and which generated files would be checked in. Done means the one-off outputs are committed and routine builds no longer perform this code generation, with future schema changes still understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100