Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
imagejan opened this issue Jun 28, 2020 · 0 comments
Open

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

imagejan opened this issue Jun 28, 2020 · 0 comments

Comments

@imagejan
Copy link
Member

imagejan commented Jun 28, 2020 •
edited
Loading

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 ?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@imagejan