You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/02/23 08:06:03 UTC

[jira] Updated: (SUREFIRE-163) Surefire ClassLoader Breaks RIFE's ClassLoader

     [ http://jira.codehaus.org/browse/SUREFIRE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated SUREFIRE-163:
----------------------------------

    Fix Version/s:     (was: 2.3)
                   2.4

> Surefire ClassLoader Breaks RIFE's ClassLoader
> ----------------------------------------------
>
>                 Key: SUREFIRE-163
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-163
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading
>    Affects Versions: 2.0 (2.2 plugin)
>         Environment: Any operating system
> RIFE 1.5.1
> Maven 2.0.4
> Java 1.5.x (1.4.x was not tested)
>            Reporter: Jeremy Whitlock
>             Fix For: 2.4
>
>         Attachments: rife-maven-example.tar.gz
>
>
> Hi All,
>     I am developing a RIFE application with Maven.  Initially, there were no issues due to my unit tests not needing access to RIFE managed objects.  Once I wanted to start testing that the RIFE portions of my application were functioning properly, I began running into NullPointerExceptions (NPE) when RIFE was trying to instantiate objects.  I did some verification of my application's target directory and it appeared proper.  I messed around with the forkMode and childDelegation configurations but nothing made RIFE work properly.  This being said, I have created a sample RIFE application that I will attach to this JIRA.  There are two outcomes of this JIRA:
> 1.  Updated documentation in the event that this is a non-issue.
> 2.  This is an issue and should be fixed.
> There is a README file in the attachment that will explain how to configure the environment so that you can run my RIFE application properly, and without error, using the jetty plugin and then how to reproduce this problem with the surefire portion of Maven.  Using the "-X" flag during the "mvn test" call proves that the classes resulting in the NPE are in fact on the classpath.
> Take care,
> Jeremy

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