Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
The index.html files are generated by the project-info-reports plugin, not the site plugin, you have to configure that instead. HTH, -Lukas Doug Daniels wrote: Sorry about that, you're correct, I had renamed some things in my pom.xml like my modules to make my example clearer and I forgot to rename that properly. I'm wondering if anyone knows of any issues with the site plugin and why my subproject modules would generate all the source files except for the index.html. I don't specify any src/site/ files like src/site/site.xml or src/site/apt/index.apt. -Original Message- From: Stevo Slavić [mailto:ssla...@gmail.com] Sent: Wednesday, November 11, 2009 4:30 PM To: Maven Users List Subject: Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1.2/version reportSets reportSet reports reportproject-team/report reportcim/report reportscm/report /reports /reportSet /reportSets /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version configuration
Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1.2/version reportSets reportSet reports reportproject-team/report reportcim/report reportscm/report /reports /reportSet /reportSets /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version configuration !-- Default configuration for all reports -- detectOfflineLinkstrue/detectOfflineLinks !-- detectLinkstrue/detectLinks -- detectJavaApiLinktrue/detectJavaApiLink linksourcetrue/linksource useStandardDocletOptionstrue/useStandardDocletOptions charsetUTF-8/charset encodingUTF-8/encoding docencodingUTF-8/docencoding breakiteratortrue/breakiterator versiontrue/version
RE: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
Sorry about that, you're correct, I had renamed some things in my pom.xml like my modules to make my example clearer and I forgot to rename that properly. I'm wondering if anyone knows of any issues with the site plugin and why my subproject modules would generate all the source files except for the index.html. I don't specify any src/site/ files like src/site/site.xml or src/site/apt/index.apt. -Original Message- From: Stevo Slavić [mailto:ssla...@gmail.com] Sent: Wednesday, November 11, 2009 4:30 PM To: Maven Users List Subject: Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1.2/version reportSets reportSet reports reportproject-team/report reportcim/report reportscm/report /reports /reportSet /reportSets /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version configuration !-- Default configuration for all reports --
RE: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
If I define a src/site/site.xml, and src/site/apt/index.apt in my parent and child projects, it will generate an index.html for all child subproject modules. I did have to do the workaround of defining a distributionManagement for each subproject module, but that's not that bad. -Original Message- From: Doug Daniels [mailto:ddani...@webwars.com] Sent: Wednesday, November 11, 2009 4:48 PM To: Maven Users List Subject: RE: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Sorry about that, you're correct, I had renamed some things in my pom.xml like my modules to make my example clearer and I forgot to rename that properly. I'm wondering if anyone knows of any issues with the site plugin and why my subproject modules would generate all the source files except for the index.html. I don't specify any src/site/ files like src/site/site.xml or src/site/apt/index.apt. -Original Message- From: Stevo Slavić [mailto:ssla...@gmail.com] Sent: Wednesday, November 11, 2009 4:30 PM To: Maven Users List Subject: Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1.2/version reportSets reportSet reports reportproject-team/report
Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
Hello Doug, Maybe I'm wrong but I have a feeling that you either haven't read completely my initial reply or didn't understand it. In that parent pom snippet you've configured maven-project-info-reports pluginhttp://maven.apache.org/plugins/maven-project-info-reports-plugin/not to generate index report, only cim, scm, and project-team reports. Regards, Stevo. 2009/11/12 Doug Daniels ddani...@webwars.com If I define a src/site/site.xml, and src/site/apt/index.apt in my parent and child projects, it will generate an index.html for all child subproject modules. I did have to do the workaround of defining a distributionManagement for each subproject module, but that's not that bad. -Original Message- From: Doug Daniels [mailto:ddani...@webwars.com] Sent: Wednesday, November 11, 2009 4:48 PM To: Maven Users List Subject: RE: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Sorry about that, you're correct, I had renamed some things in my pom.xml like my modules to make my example clearer and I forgot to rename that properly. I'm wondering if anyone knows of any issues with the site plugin and why my subproject modules would generate all the source files except for the index.html. I don't specify any src/site/ files like src/site/site.xml or src/site/apt/index.apt. -Original Message- From: Stevo Slavić [mailto:ssla...@gmail.com] Sent: Wednesday, November 11, 2009 4:30 PM To: Maven Users List Subject: Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution
