This might be related to his use of the scope system for the dependency.
Tom/etc, can you perhaps use "mvn install:install-file" to copy the
tools.jar file into your Maven repo, and then change the dependency to
"provided", and re-run your site generation? Just to see if this is a
valid work-around for the problem...
Wayne
On 4/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Did someone post an answer to this, I am having the same problem!
>
> Thanks
>
>
> On 4/6/06, Tom Joad <[EMAIL PROTECTED]> wrote:
> >
> > Hello all,
> > When I add ${java.home}/../lib/tools.jar
> >
> > <dependency>
> > <groupId>sun.jdk</groupId>
> > <artifactId>tools</artifactId>
> > <version>1.4.2</version>
> > <scope>system</scope>
> > <systemPath>${java.home}/../lib/tools.jar</systemPath>
> > </dependency>
> > as dependency of my project and run mvn site I get following error
> > ...
> > [DEBUG] -- end configuration --
> > [INFO] [site:site]
> > [INFO] Generate "Continuous Integration" report.
> > [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got
> > 0
> > [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
> > [INFO] Generate "Dependencies" report.
> > [INFO]
> > ----------------------------------------------------------------------------
> > [ERROR] FATAL ERROR
> > [INFO]
> > ----------------------------------------------------------------------------
> > [INFO] null
> > [INFO]
> > ----------------------------------------------------------------------------
> > [DEBUG] Trace
> > java.lang.NullPointerException
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:82)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:63)
> > at
> > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > (DefaultMavenProjectBuilder.java:3
> > 86)
> > at
> > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
> > DefaultMavenProjectBuilder.java:351)
> > at
> > org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository
> > (Dep
> > endenciesReport.java:362)
> > at
> > org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody
> > (DependenciesReport.jav
> > a:242)
> > at org.apache.maven.reporting.AbstractMavenReportRenderer.render(
> > AbstractMavenReportRenderer.java:65)
> > at
> > org.apache.maven.report.projectinfo.DependenciesReport.executeReport(
> > DependenciesReport.java:157)
> > at org.apache.maven.reporting.AbstractMavenReport.generate(
> > AbstractMavenReport.java:98)
> > at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(
> > SiteMojo.java:802)
> > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java
> > :301)
> > at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> > DefaultPluginManager.java:415)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> > (DefaultLifecycleExecutor.java:531)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> > (DefaultLifecycleExecutor.java:47
> > ....
> > Is it a bug ?
> >
> > Tom.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
