maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Billemont (JIRA)" <>
Subject [jira] Commented: (MWAR-169) NPE during packaging.
Date Fri, 05 Sep 2008 14:33:48 GMT


Maarten Billemont commented on MWAR-169:

This might be interesting; done after the process of building from the parent failed on artifact

cd "safe-online-owner-webapp"
cp -a target target~
mvn clean install # successful
diff -ur target~ target

The result shows only one file is different: "war/work/webapp-cache.xml"
The old version of this file (from target~; the target dir that caused the build to fail)
contained an entry for "" which is NOT the
artifact that should be overlayed on this artifact.
The new version of this file (from target; the target dir that caused the build to succeed)
contained an entry for "" which IS the artifact
that should be overlayed on this artifact.  So that's good.

Basically; I conclude something has gone wrong in the caching backend of maven-war-plugin.

> NPE during packaging.
> ---------------------
>                 Key: MWAR-169
>                 URL:
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>            Reporter: Maarten Billemont
> The following NPE happens when I run maven from the parent in a multi-module project;
though it does not occur when I run mvn clean install from within the module itself.
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[safe-online-startup-runtime] in [/Users/mbillemo/Documents/workspace/safe-online/safe-online-startup-runtime/target/safe-online-startup-
> runtime-1.1-SNAPSHOT]
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
>         at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(
>         at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(
>         at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(
>         at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(
       at org.apache.maven.plugin.war.WarMojo.performPackaging(        at
org.apache.maven.plugin.war.WarMojo.execute(        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
       at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>         at org.apache.maven.DefaultMaven.doExecute(        at org.apache.maven.DefaultMaven.execute(
       at org.apache.maven.cli.MavenCli.main(        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)        at sun.reflect.NativeMethodAccessorImpl.invoke(
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(
       at java.lang.reflect.Method.invoke(
>         at org.codehaus.classworlds.Launcher.launchEnhanced(
>         at org.codehaus.classworlds.Launcher.launch(
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(
>         at org.codehaus.classworlds.Launcher.main(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message