You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Corridor Software Developer (JIRA)" <ji...@codehaus.org> on 2008/09/24 21:34:45 UTC

[jira] Created: (MWAR-170) NPE in WebappStructure, Line 109

NPE in WebappStructure, Line 109
--------------------------------

                 Key: MWAR-170
                 URL: http://jira.codehaus.org/browse/MWAR-170
             Project: Maven 2.x War Plugin
          Issue Type: Bug
    Affects Versions: 2.1-alpha-2
         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
                <version>2.1-alpha-2-SNAPSHOT</version>

            Reporter: Corridor Software Developer


Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
java.lang.NullPointerException
        at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
        at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
        at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
        at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
        at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
        at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
        at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        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:597)
        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)
[INFO] ------------------------------------------------------------------------

NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148901#action_148901 ] 

Wendy Smoak commented on MWAR-170:
----------------------------------

Does it happen with the 2.1-alpha-2 release?

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Tim Harsch (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188723#action_188723 ] 

Tim Harsch commented on MWAR-170:
---------------------------------

The maven-war-plugin.  2.2.1 is not using the latest.
here's a basic definition you can put in your pom
{code:xml}
<plugin>
	<artifactId>maven-war-plugin</artifactId>
	<version>2.1-beta-1</version>
</plugin>
{code}

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Olivier Lamy
>             Fix For: 2.1-beta-1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Corridor Software Developer (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149102#action_149102 ] 

Corridor Software Developer commented on MWAR-170:
--------------------------------------------------

Nope. You're correct. the build succeeded in the release. I'll close the issue.


> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Tim Harsch (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187497#action_187497 ] 

Tim Harsch commented on MWAR-170:
---------------------------------

I am seeing this issue in Maven 2.2.1 using m2eclipse 0.9.6 when executing mvn package.  The error does not happen when running from cmd line only.  The project I created was using the maven-archtype-webapp described here:
http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto

Here is the console output:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building mvn-simple-auth Maven Webapp
[INFO]    task-segment: [package]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\wspaces\eclipse\SoRSVN_AfterAccurevPort\mvn-simple-auth\src\test\resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: C:\wspaces\eclipse\SoRSVN_AfterAccurevPort\mvn-simple-auth\target\surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[mvn-simple-auth] in [C:\wspaces\eclipse\SoRSVN_AfterAccurevPort\mvn-simple-auth\target\mvn-simple-auth]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
	at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
	at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
	at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
	at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
	at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
	at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
	at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
	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:597)
	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)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Tue Aug 18 08:35:37 PDT 2009
[INFO] Final Memory: 10M/19M
[INFO] ------------------------------------------------------------------------




> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Olivier Lamy
>             Fix For: 2.1-beta-1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Paul Taylor (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188721#action_188721 ] 

Paul Taylor commented on MWAR-170:
----------------------------------

Upgrade what exactly.
I just upgraded from maven 2.0.9 to maven 2.2.1 and now I get this error, I havent specified a version of Maven War plugin

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Olivier Lamy
>             Fix For: 2.1-beta-1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187498#action_187498 ] 

Stephane Nicoll commented on MWAR-170:
--------------------------------------

The version is the version of the plugin, not the version of Maven. Your log probably don't use maven war plugin 2.1-beta-1 but an older version.  Just upgrade.

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x WAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Olivier Lamy
>             Fix For: 2.1-beta-1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Mathias Bogaert (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150999#action_150999 ] 

Mathias Bogaert commented on MWAR-170:
--------------------------------------

Seeing this as well, using Maven 2.0.9 and maven-war-plugin 2.1-alpha-2.

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Stephane Nicoll
>             Fix For: 2.1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MWAR-170.
-----------------------------

      Assignee: Olivier Lamy  (was: Stephane Nicoll)
    Resolution: Fixed

tested with use case provided in MWAR-169

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Olivier Lamy
>             Fix For: 2.1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153611#action_153611 ] 

Olivier Lamy commented on MWAR-170:
-----------------------------------

NPE check added in rev 712569.
Can you test with your project ?
Thanks.

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Stephane Nicoll
>             Fix For: 2.1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll updated MWAR-170:
---------------------------------

    Fix Version/s:     (was: 2.1-alpha-2)
                   2.1

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Stephane Nicoll
>             Fix For: 2.1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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] Reopened: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll reopened MWAR-170:
----------------------------------

      Assignee: Stephane Nicoll

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>            Assignee: Stephane Nicoll
>             Fix For: 2.1
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Corridor Software Developer (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corridor Software Developer closed MWAR-170.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1-alpha-2

fixed in actual release.

> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>             Fix For: 2.1-alpha-2
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

-- 
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: (MWAR-170) NPE in WebappStructure, Line 109

Posted by "Torsten Juergeleit (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MWAR-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149644#action_149644 ] 

Torsten Juergeleit commented on MWAR-170:
-----------------------------------------

We still see the same NPE running the 2.1-alpha-2 release with Maven 2.0.9 from within Hudson: 

java.lang.NullPointerException 
at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109) 
at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288) 
at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46) 
at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439) 
at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375) 
at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) 
at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) 
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) 
at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:159) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) 
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:42) 
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) 
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) 
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 
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 hudson.maven.agent.Main.launch(Main.java:133) 
at hudson.maven.MavenBuilder.call(MavenBuilder.java:139) 
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:543) 
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:489) 
at hudson.remoting.UserRequest.perform(UserRequest.java:69) 
at hudson.remoting.UserRequest.perform(UserRequest.java:23) 
at hudson.remoting.Request$2.run(Request.java:213) 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) 
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) 
at java.util.concurrent.FutureTask.run(FutureTask.java:123) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 
at java.lang.Thread.run(Thread.java:595) 

We had to downgrade to the 2.1-alpha-1 release to workaround this issue.


> NPE in WebappStructure, Line 109
> --------------------------------
>
>                 Key: MWAR-170
>                 URL: http://jira.codehaus.org/browse/MWAR-170
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>         Environment:                 <version>2.1-beta-1-SNAPSHOT</version>
>                 <version>2.1-alpha-2-SNAPSHOT</version>
>            Reporter: Corridor Software Developer
>             Fix For: 2.1-alpha-2
>
>
> Both of these versions (see environment) introduce a NullPointerException not exhibited in the current release:
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109)
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288)
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>         at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>         at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>         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:597)
>         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)
> [INFO] ------------------------------------------------------------------------
> NPE's are usually self-explanatory, but if you need a pom or test case project, let me know...

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