mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRMINA-619) Mark easymock as test dependency in maven pom.xml
Date Thu, 04 Sep 2008 08:17:44 GMT

    [ https://issues.apache.org/jira/browse/DIRMINA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628277#action_12628277

Emmanuel Lecharny commented on DIRMINA-619:


this was certainly not noise ! We really appreciate those kind of reports. This is the way
to go, definitively : we can quickly check if it's a real bug or not, and if not, we simply
close the JIRA. It's a 5 minutes process, and it's asynchronous, compared to a mail which
must be processed quick immediatly, or forgetten for ever...

Thanks !

> 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.

View raw message