Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Testcase included:yes
-
Number of attachments :
Description
I have run into a situation where running "mvn jetty:run" results in a NullPointerException when in reality, there should be none. When I run "mvn jetty:run-war" or "mvn jetty:run-exploded", the NPE does not manifest and the application runs properly. (If it is any consolation, "mvn test" runs the same as "mvn jetty:run" so this may be a little deeper than just the Jetty plugin.) Anyway, I have attached a project to help you reproduce this issue and respond accordingly. Here are some instructions:
Preparation
----------------
The README included with the attachment tells you how to install RIFE into your local Maven repository
Reproduction
------------------
If you are interested, run "mvn test" to reproduce the fact that Maven's test plugin suffers from this issue as well. If not, continue on by running "mvn jetty:run -o -Dmaven.test.skip=true". This should result in an NPE as part of the server startup. Then run "mvn jetty:run-exploded -o -Dmaven.test.skip=true" and this time, there should be no NPE. The same should happen if you use jetty:run-war as opposed to running jetty:run-exploded.
I would be extremely happy if this turns out to be a non-issue but a misunderstanding on my part. If not, I hope my attachment and documentation helps fix any issues found as a result of this Jira.
Take care,
Jeremy
Disregard the "mvn test" issues. Apparently I learned more about RIFE that made running unit tests work. This does appear to be more related to the Maven Jetty plugin than the Maven framework.
Take care,
Jeremy