openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-233) Top level POM declares a compile-time dependency on JUnit
Date Wed, 02 May 2007 15:28:15 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493122
] 

Craig Russell commented on OPENJPA-233:
---------------------------------------

> Why not move on up to the 4.1 junit suite as well while we are at it. Backwards compatible
and more robust? 

I guess because I believe in making one change at a time. I'm not sure I have the complete
test infrastructure to make sure that a new version of JUnit would work. There are several
test suites outside of the project that might be affected.

> Top level POM declares a compile-time dependency on JUnit
> ---------------------------------------------------------
>
>                 Key: OPENJPA-233
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-233
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: build / infrastructure
>    Affects Versions: 0.9.7
>            Reporter: Craig Russell
>            Priority: Trivial
>             Fix For: 0.9.8
>
>
> trunk/pom.xml declares the following maven dependency on JUnit. 
>         <dependency>
>             <groupId>junit</groupId>
>             <artifactId>junit</artifactId>
>             <version>3.8.1</version>
>             <scope>compile</scope>
>         </dependency>
> The dependency should be test, not compile, as required only by test components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message