You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin Gilday (JIRA)" <ji...@codehaus.org> on 2007/11/23 14:36:57 UTC

[jira] Created: (SUREFIRE-388) JUnit4 not activated when using junit-dep

JUnit4 not activated when using junit-dep
-----------------------------------------

                 Key: SUREFIRE-388
                 URL: http://jira.codehaus.org/browse/SUREFIRE-388
             Project: Maven Surefire
          Issue Type: Bug
          Components: Junit 4.x support
    Affects Versions: 2.3.1
            Reporter: Martin Gilday


In the central repo there is now a copy of JUnit 4 which is correctly Mavenised, it has a dependency tree rather than one single uber-jar. This artifact is used by the JMock 2 artifacts.  Ideally the presence of this artifact should activate JUnit4 runner as well as the original.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (SUREFIRE-388) JUnit4 not activated when using junit-dep

Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/SUREFIRE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Fabulich closed SUREFIRE-388.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4

This is fixed in 2.4 trunk

> JUnit4 not activated when using junit-dep
> -----------------------------------------
>
>                 Key: SUREFIRE-388
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-388
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.3.1
>            Reporter: Martin Gilday
>             Fix For: 2.4
>
>
> In the central repo there is now a copy of JUnit 4 which is correctly Mavenised, it has a dependency tree rather than one single uber-jar. This artifact is used by the JMock 2 artifacts.  Ideally the presence of this artifact should activate JUnit4 runner as well as the original.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SUREFIRE-388) JUnit4 not activated when using junit-dep

Posted by "Martin Gilday (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SUREFIRE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114662 ] 

Martin Gilday commented on SUREFIRE-388:
----------------------------------------

<dependency>
  <groupId>junit</groupId>
  <artifactId>junit-dep</artifactId>
  <version>4.4</version>
</dependency>

> JUnit4 not activated when using junit-dep
> -----------------------------------------
>
>                 Key: SUREFIRE-388
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-388
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.3.1
>            Reporter: Martin Gilday
>
> In the central repo there is now a copy of JUnit 4 which is correctly Mavenised, it has a dependency tree rather than one single uber-jar. This artifact is used by the JMock 2 artifacts.  Ideally the presence of this artifact should activate JUnit4 runner as well as the original.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (SUREFIRE-388) JUnit4 not activated when using junit-dep

Posted by "Mauro Talevi (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/SUREFIRE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi updated SUREFIRE-388:
----------------------------------

    Affects Version/s:     (was: 2.3.1)
                       2.3
        Fix Version/s: 2.3.1

Also backported to 2.3.1.  See SUREFIRE-370.

> JUnit4 not activated when using junit-dep
> -----------------------------------------
>
>                 Key: SUREFIRE-388
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-388
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.3
>            Reporter: Martin Gilday
>             Fix For: 2.3.1, 2.4
>
>
> In the central repo there is now a copy of JUnit 4 which is correctly Mavenised, it has a dependency tree rather than one single uber-jar. This artifact is used by the JMock 2 artifacts.  Ideally the presence of this artifact should activate JUnit4 runner as well as the original.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira