[
https://issues.apache.org/jira/browse/DIRMINA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627963#action_12627963
]
Niklas Gustavsson commented on DIRMINA-619:
-------------------------------------------
They are already scoped as test in the parent POM:
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymock</artifactId>
<version>2.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymockclassextension</artifactId>
<version>2.3</version>
<scope>test</scope>
</dependency>
As a downstream user of MINA in FtpServer, I don't get these included as
transitive dependencies so I think the scoping work as expected.
> Mark easymock as test dependency in maven pom.xml
> -------------------------------------------------
>
> Key: DIRMINA-619
> URL: https://issues.apache.org/jira/browse/DIRMINA-619
> Project: MINA
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0-M3
> Reporter: syvalta
>
> Currently Maven pom.xml for core includes following dependencies:
> <dependency>
> <groupId>org.easymock</groupId>
> <artifactId>easymock</artifactId>
> </dependency>
>
> <dependency>
> <groupId>org.easymock</groupId>
> <artifactId>easymockclassextension</artifactId>
> </dependency>
> I would assume that they are test dependencies, so adding <scope>test</scope>
> to them would be good to prevent them to be included in wars etc. Unless I'm
> mistaken and they really are needed at runtime, which I find highly unlikely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
