You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeremy Whitlock (JIRA)" <ji...@codehaus.org> on 2006/12/20 05:35:42 UTC
[jira] Created: (MSUREFIRE-186) Surefire ClassLoader Breaks RIFE's
ClassLoader
Surefire ClassLoader Breaks RIFE's ClassLoader
----------------------------------------------
Key: MSUREFIRE-186
URL: http://jira.codehaus.org/browse/MSUREFIRE-186
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Components: classloading
Affects Versions: 2.2
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
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
[jira] Updated: (SUREFIRE-163) Surefire ClassLoader Breaks RIFE's
ClassLoader
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Moved: (SUREFIRE-163) Surefire ClassLoader Breaks RIFE's
ClassLoader
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-186 to SUREFIRE-163:
-------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
Component/s: (was: classloading)
Key: SUREFIRE-163 (was: MSUREFIRE-186)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> Surefire ClassLoader Breaks RIFE's ClassLoader
> ----------------------------------------------
>
> Key: SUREFIRE-163
> URL: http://jira.codehaus.org/browse/SUREFIRE-163
> Project: Maven Surefire
> Issue Type: Bug
> 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
> 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
[jira] Updated: (SUREFIRE-163) Surefire ClassLoader Breaks RIFE's
ClassLoader
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-163:
----------------------------------
Fix Version/s: 2.3
> 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.3
>
> 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
[jira] Closed: (SUREFIRE-163) Surefire ClassLoader Breaks RIFE's
ClassLoader
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich closed SUREFIRE-163.
---------------------------------
Resolution: Incomplete
Fix Version/s: (was: 2.4)
Certainly RIFE is throwing a NPE, but the exact same thing happens when you run the test in Eclipse, so I'm pretty sure this isn't a Surefire bug. I don't know the first thing about RIFE, so it's impossible to say whether this is a bug in RIFE or a bug in the test (perhaps the test doesn't configure RIFE correctly) but regardless it's not a bug in Surefire.
> 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
> 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
[jira] Updated: (SUREFIRE-163) Surefire ClassLoader Breaks RIFE's
ClassLoader
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-163:
----------------------------------
Affects Version/s: 2.0 (2.2 plugin)
Component/s: classloading
> 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
> 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