ok thanks. Do I need to put this in the report or plugins section. I'm a bit confused about the difference.
Kuno -----Ursprüngliche Nachricht----- Von: Nick Stolwijk [mailto:[EMAIL PROTECTED] Gesendet: Montag, 17. November 2008 15:30 An: Maven Users List Betreff: Re: Skipping dependency report during Maven2 site generation Do not confuse the Maven version number versus the Maven Project Info Reports Plugin version number. The option exists since 2.1 of the Maven Project Info Reports Plugin, which is usable with Maven 2.0.9. Changing your plugin configuration to: >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-project-info-reports-plugin</artifactId> <version>2.1</version> >> <configuration> >> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> >> </configuration> >> </plugin> Should solve your problem. Since Maven 2.0.9 the default plugins have a version specified in contrary to earlier Maven versions. There plugins were always resolved to the latest version, which can cause unstable builds. You can always specify the version of the different plugins yourself. Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Mon, Nov 17, 2008 at 3:21 PM, qnob <[EMAIL PROTECTED]> wrote: > > Hello, > > I've got the same problem with Maven 2.0.9. However, this option > (dependencyLocationsEnabled) does exist since 2.1 only, right? :-{ > > Thanks > > Kuno > > > > > espen.wiborg wrote: >> >> sinplicity <[EMAIL PROTECTED]> writes: >>> Sorry, this might be a re-post, but the first one did not go through >>> >>> I need to understand how we disable the dependencies report during >>> Maven2 site generation while leaving the other reports in place. We >>> use reports such as the dependency convergence report, but the >>> dependencies report just takes too long. The documentation does not >>> seem to be clear on how to disable a default report such as this >>> one. >> >> To make the dependency report generation LOTS faster, stick the >> following in the reporting/plugins section of your POM: >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-project-info-reports-plugin</artifactId> >> <configuration> >> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> >> </configuration> >> </plugin> >> >> Alternatively, run Maven with -Ddependency.locations.enabled=false. >> >> -- >> Espen Wiborg <[EMAIL PROTECTED]> - Veritas vos liberabit I know >> you believe you understand what you think I said. But I am not sure >> you realize that what you heard is not what I meant. -- Anon. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/Skipping-dependency-report-during-Maven2-site-generation-tp20116761p20540282.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
