You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gilles Scokart (JIRA)" <ji...@codehaus.org> on 2006/07/06 13:00:22 UTC

[jira] Created: (MSUREFIRE-144) Depencencies get precedence over test sources in classpath

Depencencies get precedence over test sources in classpath
----------------------------------------------------------

         Key: MSUREFIRE-144
         URL: http://jira.codehaus.org/browse/MSUREFIRE-144
     Project: Maven 2.x Surefire Plugin
        Type: Bug

    Versions: 2.2    
    Reporter: Gilles Scokart


Here is a concrete example :

I write a plugin for cruisecontrol.  The cruise control jar contains a log4J.properties.  I have placed a log4j.properties in my test ressources directory (I alsoe tried to place it in the main ressource directory).

When I run the test in eclipse, my log4j.property is used.  When I run it from maven, it is the log4j.properties contained in cruisecontrol.jar that is used.

When I modify the cruisecontrol jar store in my repositry to remove its log4j.properties, the log4j.properties of the test ressource directory is used.

I also made a test with a class instead of a property file.  I have re-written a class defined in my dependency (same name, same package) in my test source directory.  The result is the same.  In eclipse my class is used, in maven, it is the class present in the dependency that is used.

-- 
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-108) Depencencies get precedence over test sources in classpath

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

Brett Porter updated SUREFIRE-108:
----------------------------------

    Fix Version/s:     (was: 2.3)
                   2.4

> Depencencies get precedence over test sources in classpath
> ----------------------------------------------------------
>
>                 Key: SUREFIRE-108
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-108
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Gilles Scokart
>             Fix For: 2.4
>
>
> Here is a concrete example :
> I write a plugin for cruisecontrol.  The cruise control jar contains a log4J.properties.  I have placed a log4j.properties in my test ressources directory (I alsoe tried to place it in the main ressource directory).
> When I run the test in eclipse, my log4j.property is used.  When I run it from maven, it is the log4j.properties contained in cruisecontrol.jar that is used.
> When I modify the cruisecontrol jar store in my repositry to remove its log4j.properties, the log4j.properties of the test ressource directory is used.
> I also made a test with a class instead of a property file.  I have re-written a class defined in my dependency (same name, same package) in my test source directory.  The result is the same.  In eclipse my class is used, in maven, it is the class present in the dependency that is used.

-- 
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] Moved: (SUREFIRE-108) Depencencies get precedence over test sources in classpath

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

Brett Porter moved MSUREFIRE-144 to SUREFIRE-108:
-------------------------------------------------

    Affects Version/s:     (was: 2.0 (2.2 plugin))
                       2.0 (2.2 plugin)
        Fix Version/s:     (was: 2.3)
                       2.3
                  Key: SUREFIRE-108  (was: MSUREFIRE-144)
              Project: Maven Surefire  (was: Maven 2.x Surefire Plugin)

> Depencencies get precedence over test sources in classpath
> ----------------------------------------------------------
>
>                 Key: SUREFIRE-108
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-108
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Gilles Scokart
>             Fix For: 2.3
>
>
> Here is a concrete example :
> I write a plugin for cruisecontrol.  The cruise control jar contains a log4J.properties.  I have placed a log4j.properties in my test ressources directory (I alsoe tried to place it in the main ressource directory).
> When I run the test in eclipse, my log4j.property is used.  When I run it from maven, it is the log4j.properties contained in cruisecontrol.jar that is used.
> When I modify the cruisecontrol jar store in my repositry to remove its log4j.properties, the log4j.properties of the test ressource directory is used.
> I also made a test with a class instead of a property file.  I have re-written a class defined in my dependency (same name, same package) in my test source directory.  The result is the same.  In eclipse my class is used, in maven, it is the class present in the dependency that is used.

-- 
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: (MSUREFIRE-144) Depencencies get precedence over test sources in classpath

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSUREFIRE-144?page=all ]

Brett Porter updated MSUREFIRE-144:
-----------------------------------

    Fix Version/s: 2.3

> Depencencies get precedence over test sources in classpath
> ----------------------------------------------------------
>
>                 Key: MSUREFIRE-144
>                 URL: http://jira.codehaus.org/browse/MSUREFIRE-144
>             Project: Maven 2.x Surefire Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Gilles Scokart
>             Fix For: 2.3
>
>
> Here is a concrete example :
> I write a plugin for cruisecontrol.  The cruise control jar contains a log4J.properties.  I have placed a log4j.properties in my test ressources directory (I alsoe tried to place it in the main ressource directory).
> When I run the test in eclipse, my log4j.property is used.  When I run it from maven, it is the log4j.properties contained in cruisecontrol.jar that is used.
> When I modify the cruisecontrol jar store in my repositry to remove its log4j.properties, the log4j.properties of the test ressource directory is used.
> I also made a test with a class instead of a property file.  I have re-written a class defined in my dependency (same name, same package) in my test source directory.  The result is the same.  In eclipse my class is used, in maven, it is the class present in the dependency that is used.

-- 
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-108) Depencencies get precedence over test sources in classpath

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

Dan Fabulich closed SUREFIRE-108.
---------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.4)

This apparently got fixed at some point.  Now when I run tests I see the local artifacts first, then the test classes, then dependencies in the order declared in the POM.

> Depencencies get precedence over test sources in classpath
> ----------------------------------------------------------
>
>                 Key: SUREFIRE-108
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-108
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Gilles Scokart
>
> Here is a concrete example :
> I write a plugin for cruisecontrol.  The cruise control jar contains a log4J.properties.  I have placed a log4j.properties in my test ressources directory (I alsoe tried to place it in the main ressource directory).
> When I run the test in eclipse, my log4j.property is used.  When I run it from maven, it is the log4j.properties contained in cruisecontrol.jar that is used.
> When I modify the cruisecontrol jar store in my repositry to remove its log4j.properties, the log4j.properties of the test ressource directory is used.
> I also made a test with a class instead of a property file.  I have re-written a class defined in my dependency (same name, same package) in my test source directory.  The result is the same.  In eclipse my class is used, in maven, it is the class present in the dependency that is used.

-- 
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: (MSUREFIRE-144) Depencencies get precedence over test sources in classpath

Posted by "Ronny Naess (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MSUREFIRE-144?page=comments#action_76994 ] 
            
Ronny Naess commented on MSUREFIRE-144:
---------------------------------------

I think this is a bug mentioned in many posts concerning classpath loading when running test. I have the same issues mentioned in a comment in http://jira.codehaus.org/browse/MSUREFIRE-115, possible others are http://jira.codehaus.org/browse/MSUREFIRE-161 and http://jira.codehaus.org/browse/MSUREFIRE-121. Maybe there are more. We have to skip testing in maven and rely on the developers testing in Eclipse before checking in to SCM. Risky buisiness but the tests breakes to often becase test resources only appare randomly in our classpath.

> Depencencies get precedence over test sources in classpath
> ----------------------------------------------------------
>
>                 Key: MSUREFIRE-144
>                 URL: http://jira.codehaus.org/browse/MSUREFIRE-144
>             Project: Maven 2.x Surefire Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Gilles Scokart
>             Fix For: 2.3
>
>
> Here is a concrete example :
> I write a plugin for cruisecontrol.  The cruise control jar contains a log4J.properties.  I have placed a log4j.properties in my test ressources directory (I alsoe tried to place it in the main ressource directory).
> When I run the test in eclipse, my log4j.property is used.  When I run it from maven, it is the log4j.properties contained in cruisecontrol.jar that is used.
> When I modify the cruisecontrol jar store in my repositry to remove its log4j.properties, the log4j.properties of the test ressource directory is used.
> I also made a test with a class instead of a property file.  I have re-written a class defined in my dependency (same name, same package) in my test source directory.  The result is the same.  In eclipse my class is used, in maven, it is the class present in the dependency that is used.

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