nextflow-io / nextflow-io/nf-schema
Feature: Publish methods as separate Maven package
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 57
- Forks
- 31
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 1
Description
Based on #201 and @jorgeaguileraseqera's comment here, it may be useful to use some of the nf-schema utilities in other software. The code is structured in such a way that we should be able to repackage them and make them available in other software, allowing for easier co-development of related software.
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 reading issue #201 and the linked Slack discussion to understand the proposed reuse of nf-schema utilities. Then inspect how the code is currently structured. Done means agreeing on and publishing a separate Maven package that other software can use, but the issue does not identify files, tests, or a concrete packaging plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100