[ http://jira.codehaus.org/browse/CONTINUUM-1000?page=all ]
fabrizio giustina closed CONTINUUM-1000.
----------------------------------------
Assignee: fabrizio giustina
Resolution: Duplicate
Fix Version/s: 1.0.3
this is a maven issue, see MNG-2746
as a workaround, you can specify a full path to a parent pom like "../pom.xml"
instead of ".." in child projects
> NullPointerException in maven 2 builder on build failure
> --------------------------------------------------------
>
> Key: CONTINUUM-1000
> URL: http://jira.codehaus.org/browse/CONTINUUM-1000
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.1
> Environment: JDK v1.4.2 on RHAS4, with maven 2.0.4.
> Reporter: Graham Leggett
> Assigned To: fabrizio giustina
> Priority: Critical
> Fix For: 1.0.3
>
>
> When an attempt is made to build a maven 2 subproject, and that subproject is
> known to fail to build, the following build error is logged during the
> continuum build:
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1078)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:674)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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: < 1 second
> [INFO] Finished at: Wed Nov 08 14:43:16 SAST 2006
> [INFO] Final Memory: 3M/239M
> [INFO]
> ------------------------------------------------------------------------
> It's not clear at this point whether this is a maven 2 bug, or a continuum
> bug.
--
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
