Skip to content

Shouldn't junit dependency in POM have test scope? #14

Description

@vvdleun

Hi,

I noticed my application bundles JUnit in its production JAR files. After looking around, I think it is caused by the POM file of mDNSJava:

<dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>4.12</version>
</dependency>

Shouldn't the "test" scope be specified here as well, or is there a reason for its compile scope?

Kind regards (and many thanks for your work on this awesome library!),
Vincent

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions