Skip to content

Consider moving main method in test scope (reduce dependency footprint) #4

@imagejan

Description

@imagejan

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 ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions