Hi guys,

mvn -U clean install 

This did the trick.  Thanks for the help.

Dave
  ----- Original Message ----- 
  From: Simon Laws 
  To: [email protected] 
  Sent: Friday, August 15, 2008 3:31 PM
  Subject: Re: Build Failure in node2-launcher-webapp





  On Fri, Aug 15, 2008 at 7:02 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:

    The NPE comes from maven war plugin. It seems that something is broken in 
that plugin.

    I just tried it and it works for me. Using -X debug flag, I can tell the 
plugin version I have is: 
org.apache.maven.plugins:maven-war-plugin:2.1-alpha-1:war

    Can you run mvn -X clean install to produce a debug output for that module? 
Can you try mvn -U clean install? 

    Thanks,
    Raymond


    From: scabooz 
    Sent: Friday, August 15, 2008 10:41 AM
    To: [email protected] 
    Subject: Build Failure in node2-launcher-webapp


    Hi all,

    I just updated to r682646, the build fails as follows in module 
node2-launcher-webapp.  Any ideas?

    Thanks

    Dave

    [INFO] Scanning for projects...
    [INFO] 
------------------------------------------------------------------------
    [INFO] Building Apache Tuscany SCA Node WebApp
    [INFO]    task-segment: [install]
    [INFO] 
------------------------------------------------------------------------
    [INFO] [resources:resources]
    [INFO] Using default encoding to copy filtered resources.
    [INFO] [compiler:compile]
    [INFO] Nothing to compile - all classes are up to date
    [INFO] [bundle:manifest {execution: bundle-manifest}]
    [INFO] [resources:testResources]
    [INFO] Using default encoding to copy filtered resources.
    [INFO] [compiler:testCompile]
    [INFO] Nothing to compile - all classes are up to date
    [INFO] [surefire:test]
    [INFO] Surefire report directory: 
G:\sandboxes\SCA2Proto\tuscany\modules\node2-launcher-webapp\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]
    [INFO] Packaging webapp
    [INFO] Assembling webapp[tuscany-node2-launcher-webapp] in 
[G:\sandboxes\SCA2Proto\tuscany\modules\node2-launc
    her-webapp\target\tuscany-node2-launcher-webapp-1.4-SNAPSHOT]
    [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(Dependenci
    esAnalysisPackagingTask.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:447)
            at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

            at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecut
    or.java:480)
            at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
            at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx
    ecutor.java:311)
            at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja
    va: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)
    [INFO] 
------------------------------------------------------------------------
    [INFO] Total time: 5 seconds
    [INFO] Finished at: Fri Aug 15 13:39:50 EDT 2008
    [INFO] Final Memory: 10M/19M
    [INFO] 
------------------------------------------------------------------------

  I saw this earlier. Did a clean and it went away so put it down to a maven 
funny. I'm getting a problem in itest/osgi-implementation and am just about to 
do an update/build so I'll let you know if I see the above problem again. 

  Simon

Reply via email to