Null pointer on JSW app generation if no description set
--------------------------------------------------------

                 Key: MOJO-1112
                 URL: http://jira.codehaus.org/browse/MOJO-1112
             Project: Mojo
          Issue Type: Bug
          Components: appassembler
         Environment: MacOS X 10.5, Java 1.5
            Reporter: Christian Gruber


MavenModel.description is used to set the app.description property in the 
plugin in :

JavaServiceWrapperDaemonGenerator.createContext();

Line 199 does not test for null before setting the property.  
java.util.Properties cannot take null values for properties, so if a 
<description> is not set on the pom, then an NPE ensues.

java.lang.NullPointerException
        at java.util.Hashtable.put(Hashtable.java:396)
        at java.util.Properties.setProperty(Properties.java:128)
        at 
org.codehaus.mojo.appassembler.daemon.jsw.JavaServiceWrapperDaemonGenerator.createContext(JavaServiceWrapperDaemonGenerator.java:199)
        at 
org.codehaus.mojo.appassembler.daemon.jsw.JavaServiceWrapperDaemonGenerator.generate(JavaServiceWrapperDaemonGenerator.java:83)
        at 
org.codehaus.mojo.appassembler.daemon.DefaultDaemonGeneratorService.generateDaemon(DefaultDaemonGeneratorService.java:142)
        at 
org.codehaus.mojo.appassembler.GenerateDaemonsMojo.execute(GenerateDaemonsMojo.java:190)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)


The null should be tested, and either default behaviour provided, or a more 
meaningful error should be displayed.

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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to