imagej / imagej/example-imagej2-command
Consider moving main method in test scope (reduce dependency footprint)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 35
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Having a `main` method in the example command that calls `final ImageJ ij = new ImageJ();` requires a dependency on `net.imagej:imagej`.
In order to help projects inheriting from this example to keep their dependency footprint minimal, we should maybe move that `main` method into a test class and make the `imagej` dependency test scope only.
What do others think of that idea? @ctrueden @etadobson @frauzufall ?
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
Inspect the example command containing the main method and the Maven dependency declaration for net.imagej:imagej. Check how the command is built and run in tests, then confirm that the main entry point is test-scoped and the dependency is no longer required at runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100