site:stage gets processed first. I got the problem though. I now do a 'site-deploy' and all the links are working fine. There was a jira issue filed which said that the top most pom should have a <url> tag in it or else the modules links wont work good.
franz see wrote: > > Good day to you, Dmystery, > > In the build output, what gets processed first, javadoc or site:stage? > > Thanks, > Franz > > > Dmystery wrote: >> >> I've a multi-module project for which i'm generating a site. >> >> I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works >> fine and the modules are linked properly too. However, the Java doc >> generated are not copied to the staging directory. Only the index.html is >> copied, the rest remains in the project build directory. >> >> My parent pom looks like, >> ................. >> ................. >> <distributionManagement> >> <site> >> <id>my-site</id> >> <name>my-site</name> >> <url>file://</url> >> </site> >> </distributionManagement> >> >> <reporting> >> <plugins> >> <plugin> >> <artifactId>maven-javadoc-plugin</artifactId> >> </plugin> >> <plugin> >> <groupId>org.codehaus.mojo</groupId> >> <artifactId>jxr-maven-plugin</artifactId> >> </plugin> >> </plugins> >> </reporting> >> ................. >> ................. >> >> Interestingly, instead of the above command, if i use 'mvn site-deploy' >> with >> >> <site> >> <id>my-site</id> >> <name>my-site</name> >> <url>file://c:/somedirectory</url> >> </site> >> >> in my pom, the apidocs are copied but the module and apidocs links do not >> exists. >> >> Is there a clean way of deploying a site on to the local machine?? >> >> >> >> >> >> >> > > -- View this message in context: http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7375485 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
