geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bohn <joe.b...@earthlink.net>
Subject Re: relativePath in our parent pom entries.
Date Thu, 25 Sep 2008 14:52:00 GMT
Probably not the cause of the failures ... but I went ahead and removed 
the relativePath references anyway.

Joe


Joe Bohn wrote:
> Hmmm ... perhaps it isn't just the relativePath.  I just attempted to 
> build site for trunk and received a similar warning attempting to load a 
> parent project (this time in buildsupport) followed by a bunch of 
> failures of this type:
> 
> [ERROR] RHS of #set statement is null. Context will not be modified. 
> META-INF/maven/site.vm [line 17, column 1]
> [WARNING] org.apache.velocity.runtime.exception.ReferenceException: 
> reference : template = META-INF/maven/site.vm [line 19,column 30] : $alt 
> is not a valid reference.
> [INFO] Generate "CPD Report" report.
> [ERROR] RHS of #set statement is null. Context will not be modified. 
> META-INF/maven/site.vm [line 17, column 1]
> 
> <snip/>
> and ....
> 
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] 'helpmojo' was specified in an execution, but not found in the 
> plugin
> 
> 
> 
> Joe Bohn wrote:
>> Is there ever a valid need to specify relativePath in the parent 
>> section of our poms?
>>
>> I noticed that nearly all of the relativePath entries have been 
>> removed from trunk but not branches/2.1.  The only existing 
>> relativePath entries in trunk are for concurrent-testsuite and 
>> command-testsuite ... which I suspect are the results of merged 
>> changes from branches/2.1.
>>
>> I'm asking because I've been trying to understand the site generation 
>> for multi-module builds so that I can get this to aggregate at the top 
>> level for samples -- BTW, any pointers there are also appreciated :-) 
>> .  In the process I attempted a site build for server branches/2.1 
>> which failed with the following exception that I suspect is due to 
>> relativePath not being set correctly in security-testsuite.
>>
>>
>> [WARNING] Unable to load parent project from repository: Could not 
>> find the model file '/Users/bohn/geronimo-2.1/../pom.xml'. for project 
>> unknown
>> [INFO] Skipped "Maven Surefire Report" report, file 
>> "surefire-report.html" already exists for the English version.
>> [INFO] Generate "Plugin documentation" report.
>> [INFO] Using 2 extractors.
>> [INFO] Applying extractor for language: java
>> [INFO] Extractor for language: java found 0 mojo descriptors.
>> [INFO] Applying extractor for language: bsh
>> [INFO] Extractor for language: bsh found 0 mojo descriptors.
>> [INFO] 
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.NullPointerException
>>     at 
>> org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute(PluginXdocGenerator.java:46)

>>
>>     at 
>> org.apache.maven.plugin.plugin.PluginReport.generatePluginDocumentation(PluginReport.java:192)

>>
>>     at 
>> org.apache.maven.plugin.plugin.PluginReport.executeReport(PluginReport.java:141)

>>
>>     at 
>> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)

>>
>>     at 
>> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:67)

>>
>>     at 
>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:239)

>>
>>     at 
>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:115)

>>
>>     at 
>> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:124)
>>     at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
>>     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: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)
>>
> 
> 


Mime
View raw message