On 2011-02-09 19:49, Jochen Wiedmann wrote: > Thanks. I don't understand the reason for removing the deployment by > default (one more example where the POM grows without an apparent > reason), but your explanation helped.
The reason was to properly separate Maven 3 from the documentation generation framework (i.e. Doxia) on one hand and the Site Plugin on the other hand. This makes it possible to use other documentation generation frameworks or plugins. > On Wed, Feb 9, 2011 at 7:12 PM, lukewpatterson <[email protected]> > wrote: >> >> >> jochen-2 wrote: >>> >>> ... because the parent POM doesn't have a site and, in particular, no site >>> descriptor. >>> >> >> the parent's site.xml isn't deployed to the site repo, it's deployed to the >> end-state repo alongside the primary artifact (jar,pom,etc.) >> >> "If you want your project's site descriptor to be inherited, you need to >> attach it to the project's main artifact. You use the site:attach-descriptor >> goal to attach the site descriptor to your project's main artifact." >> http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html >> , "Inheritance" section >> >> "In Maven 2 the site descriptor is attached automatically for projects with >> packaging set to "pom". >> I'd check to see if the site.xml is sitting alongside the parent pom in the >> repo >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Require-site-descriptor-of-parent-POM-tp3377537p3378023.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] >> >> > > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
