Hi Ronny, here i have enclosed my parent pom.xml and one submodules pom.xml. please check once what's the wrong in these xml's.
According to you suggestion i have done mvn help:effective-pom also. what ever mvn help created pom's also throwing distribution Management exception. Parent POM.xml ************************************************************************************ Effective POM for project 'citistreet.id.util:CitiStreetFramework:pom:14.0' ************************************************************************************ <?xml version="1.0" encoding="UTF-8"?><project> <modelVersion>4.0.0</modelVersion> <groupId>citistreet.id.util</groupId> <artifactId>CitiStreetFramework</artifactId> <packaging>pom</packaging> <name>CitiStreetFramework</name> <version>14.0</version> <url>http://maven.apache.org</url> <build> <sourceDirectory>E:\Maven-Site\src\main\java</sourceDirectory> <scriptSourceDirectory>src/main/scripts</scriptSourceDirectory> <testSourceDirectory>E:\Maven-Site\src\test\java</testSourceDirectory> <outputDirectory>E:\Maven-Site\target</outputDirectory> <testOutputDirectory>E:\Maven-Site\target\test-classes</testOutputDirectory> <resources> <resource> <directory>E:\Maven-Site\src\main\resources</directory> </resource> </resources> <testResources> <testResource> <directory>E:\Maven-Site\src\test\resources</directory> </testResource> </testResources> <directory>E:\Maven-Site\lib</directory> <finalName>CitiStreetFramework-14.0</finalName> <plugins> <plugin> <artifactId>maven-help-plugin</artifactId> <version>2.0.1</version> </plugin> </plugins> </build> <modules> <module>cs-struts-base</module> <module>cs-logging</module> <module>cs-logging-struts</module> <module>cs-common-services</module> <module>cs-services</module> <module>cs-proxy</module> <module>cs-dbutil</module> <module>cs-web-utils</module> <module>cs-factory</module> <module>cs-config</module> <module>cs-cache</module> <module>cs-util</module> <module>cs-collections</module> <module>cs-txmgr</module> </modules> <repositories> <repository> <snapshots> <enabled>false</enabled> </snapshots> <id>central</id> <name>Maven Repository Switchboard</name> <url>http://repo1.maven.org/maven2</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <releases> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> <id>central</id> <name>Maven Plugin Repository</name> <url>http://repo1.maven.org/maven2</url> </pluginRepository> </pluginRepositories> <reporting> <outputDirectory>target/site</outputDirectory> <plugins> <plugin> <artifactId>maven-site-plugin</artifactId> <version>2.0-beta-5</version> <configuration> <locales>en</locales> </configuration> </plugin> </plugins> </reporting> <distributionManagement> <site> <id>CitiStreetFramework</id> <url>file://localhost/c:/tmp/mysite</url> </site> </distributionManagement> </project> SUB-MODULE - pom.xml <?xml version="1.0"?><project> <modelVersion>4.0.0</modelVersion> <groupId>citistreet.id.util</groupId> <artifactId>cs-util</artifactId> <name>CS-Util</name> <version>14.0</version> <url>http://maven.apache.org</url> <build> <sourceDirectory>E:\Maven-Site\cs-util\src</sourceDirectory> <scriptSourceDirectory>src/main/scripts</scriptSourceDirectory> <testSourceDirectory>E:\Maven-Site\cs-util\test</testSourceDirectory> <outputDirectory>E:\Maven-Site\cs-util\classes</outputDirectory> <testOutputDirectory>E:\Maven-Site\cs-util\target\test-classes</testOutputDirectory> <resources> <resource> <directory>E:\Maven-Site\cs-util\src\main\resources</directory> </resource> </resources> <testResources> <testResource> <directory>E:\Maven-Site\cs-util\src\test\resources</directory> </testResource> </testResources> <directory>E:\Maven-Site\cs-util\target</directory> <finalName>cs-util-14.0</finalName> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> <plugin> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <addMavenDescriptor>false</addMavenDescriptor> </archive> </configuration> </plugin> <plugin> <artifactId>maven-antrun-plugin</artifactId> <executions> <execution> <phase>package</phase> <goals> <goal>run</goal> </goals> <configuration> <tasks> <mkdir dir="../lib"></mkdir> <copy todir="../lib"> <fileset includes="*.jar" dir="${project.build.directory}"></fileset> </copy> </tasks> </configuration> </execution> </executions> </plugin> <plugin> <artifactId>maven-surefire-plugin</artifactId> <configuration> <forkMode>pertest</forkMode> <testFailureIgnore>true</testFailureIgnore> </configuration> </plugin> </plugins> </build> <repositories> <repository> <snapshots> <enabled>false</enabled> </snapshots> <id>central</id> <name>Maven Repository Switchboard</name> <url>http://repo1.maven.org/maven2</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <releases> <updatePolicy>never</updatePolicy> </releases> <snapshots> <enabled>false</enabled> </snapshots> <id>central</id> <name>Maven Plugin Repository</name> <url>http://repo1.maven.org/maven2</url> </pluginRepository> </pluginRepositories> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>[3.8.1,)</version> <scope>test</scope> </dependency> <dependency> <groupId>jaxen</groupId> <artifactId>jaxen</artifactId> <version>1.0-FCS</version> </dependency> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.0</version> </dependency> <dependency> <groupId>saxpath</groupId> <artifactId>saxpath</artifactId> <version>1.0-FCS</version> </dependency> </dependencies> <reporting> <outputDirectory>${project.build.directory}/site</outputDirectory> <plugins> <plugin> <artifactId>maven-source-plugin</artifactId> </plugin> <plugin> <artifactId>maven-javadoc-plugin</artifactId> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>surefire-report-maven-plugin</artifactId> </plugin> <plugin> <artifactId>maven-project-info-reports-plugin</artifactId> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> </plugin> </plugins> </reporting> </project> Thanks in advance. Naess, Ronny wrote: > > Well, that exeption is thrown because it can not create a > DistributionManagement object. Is <distributionManagement> listed if you > run 'mvn help:effective-pom' (mine seems to be listed at the bottom)? > > 'mvn site' generates your site, but the links will not work because all > generated sites (parent and modules) must be deployed together. > > Undeployd (only 'mvn site') gives something like this (links not > working)): > > +-module1/ > +-target/ > +-site/ <- Module1 (M1) > +-module2/ > +-target/ > +-site/ <- Module2 (M2) > +-target/ > +-site/ <- This is the root/parent level (root) > +-css/ > +-dependencies.html > +-dependency-convergence.html > +-index.html > +-etc... > > > After deployment (mvn site-deploy) you will have something like this > (links is working): > > +-[website]/ <- root > +-css/ > +-dependencies.html > +-dependency-convergence.html > +-index.html > +-etc... > +-module1/ <- M1 > +-module2/ <- M2 > > > -Ronny > > -----Opprinnelig melding----- > Fra: tulasi [mailto:[EMAIL PROTECTED] > Sendt: 26. september 2006 06:18 > Til: users@maven.apache.org > Emne: Re: SV: SV: SV: SV: maven site not showing sub module links in > parent ht > > > Hi Ronny, > > Ya, I have checked. > > I have configured Distribution Management in parent pom.xml according to > your suggestion. > > mvn site is working fine(but its not creating links in parent > index.html), site-deploy throwing execption ( Missing Distribution > management). > > please suggest me how will handle this exception. > > Thanks in advance > > > > > Naess, Ronny wrote: >> >> It says that its missing distribution management information in the >> project >> >> You know, the >> >> >> -----Opprinnelig melding----- >> Fra: tulasi [mailto:[EMAIL PROTECTED] >> Sendt: 25. september 2006 15:02 >> Til: users@maven.apache.org >> Emne: Re: SV: SV: SV: maven site not showing sub module links in >> parent html >> >> >> Hi Rony.. >> >> Please check this error >> >> [INFO] [site:deploy] >> [INFO] >> ---------------------------------------------------------------------- >> -- >> [ERROR] BUILD ERROR >> [INFO] >> ---------------------------------------------------------------------- >> -- [INFO] Missing distribution management information in the project >> [INFO] >> ---------------------------------------------------------------------- >> -- >> [INFO] Trace >> org.apache.maven.lifecycle.LifecycleExecutionException: Missing >> distribution management information in the project >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau >> lt >> LifecycleExecutor.java:559) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif >> ec >> ycle(DefaultLifecycleExecutor.java:475) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul >> tL >> ifecycleExecutor.java:454) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand >> le >> Failures(DefaultLifecycleExecutor.java:306) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment >> s( >> DefaultLifecycleExecutor.java:273) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif >> ec >> ycleExecutor.java:140) >> at >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) >> at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j >> av >> a:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess >> or >> Impl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:585) >> at >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> Caused by: org.apache.maven.plugin.MojoExecutionException: Missing >> distribution management information in the project >> at >> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.ja >> va >> :98) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin >> Ma >> nager.java:412) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau >> lt >> LifecycleExecutor.java:534) >> ... 16 more >> [INFO] >> ---------------------------------------------------------------------- >> -- >> [INFO] Total time: 34 seconds >> [INFO] Finished at: Mon Sep 25 18:33:17 GMT+05:30 2006 [INFO] Final >> Memory: 19M/39M [INFO] >> ---------------------------------------------------------------------- >> -- >> >> >> >> >> >> Naess, Ronny wrote: >>> >>> Well, the sample assumed unix. >>> >>> Try file://localhost/c:/temp/mysite instead. >>> >>> Also you can use the -e switch like mvn says, maybe the problem >>> becomes visable (mvn site site-deploy -e) >>> >>> -Ronny >>> >>> >>> -----Opprinnelig melding----- >>> Fra: tulasi [mailto:[EMAIL PROTECTED] >>> Sendt: 25. september 2006 14:04 >>> Til: users@maven.apache.org >>> Emne: Re: SV: SV: maven site not showing sub module links in parent >>> html >>> >>> >>> Hi Rony >>> >>> How will i create a site deploy in my local pc. >>> >>> I did like this <url>file://localhost/tmp/mysite</url> . but its >>> raising error. please help me dear. >>> >>> [INFO] [site:deploy] >>> [INFO] >>> --------------------------------------------------------------------- >>> - >>> -- >>> [ERROR] BUILD ERROR >>> [INFO] >>> --------------------------------------------------------------------- >>> - >>> -- [INFO] Missing distribution management information in the project >>> [INFO] >>> --------------------------------------------------------------------- >>> - >>> -- [INFO] For more information, run Maven with the -e switch [INFO] >>> --------------------------------------------------------------------- >>> - >>> -- >>> [INFO] Total time: 32 seconds >>> [INFO] Finished at: Mon Sep 25 17:34:24 GMT+05:30 2006 [INFO] Final >>> Memory: 18M/36M [INFO] >>> --------------------------------------------------------------------- >>> - >>> -- >>> >>> >>> Thanks in advance >>> >>> >>> >>> >>> >>> Naess, Ronny wrote: >>>> >>>> Running only 'mvn site' will give you site files in artifact target >>>> directory, but they will not be correctly linked before you deploy >>>> them, or I suppose stage them. I do not have experience with stage >>>> but >>> >>>> I suppose that should work the same way as site-deploy. >>>> >>>> You do not need a site.xml for each sub-module, the one in parent is > >>>> enough. Anything else would not give meaning since site,xnk is a >>>> descriptor for the whole site. >>>> >>>> My parent pom must contains something simulare to this: >>>> >>>> <distributionManagement> >>>> <site> >>>> <id>website</id> >>>> <url>file://localhost/tmp/mysite</url> >>>> </site> >>>> </distributionManagement> >>>> >>>> When I run 'mvn site site-deploy' I will find my full site structure > >>>> in /tmp/mysite >>>> >>>> -Ronny >>>> >>>> -----Opprinnelig melding----- >>>> Fra: tulasi [mailto:[EMAIL PROTECTED] >>>> Sendt: 25. september 2006 12:22 >>>> Til: users@maven.apache.org >>>> Emne: Re: SV: maven site not showing sub module links in parent html >>>> >>>> >>>> Hi all, >>>> >>>> I have tried with mvn site and mvn site:stage >>>> -DstagingDirectory=C:\mysite4 commands. >>>> >>>> and also i have tried with configuration <menu ref="modules" /> and >>>> ${modules}. >>>> >>>> But its not creating links in parent html. is thr any solution. >>> please >>>> help me >>>> >>>> and a small doubt -- is it need to contain site.xml in each every >>>> sub-module?. >>>> >>>> >>>> Thanks in advance >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Naess, Ronny wrote: >>>>> >>>>> This works fine for me: >>>>> >>>>> <menu ref="parent" /> >>>>> <menu ref="modules" /> >>>>> <menu ref="reports" /> >>>>> >>>>> You could also try ${modules}, but it is basically the same. >>>>> >>>>> You also might want to narrow down your problem in your site.xml >>>>> file, >>>> >>>>> trying to only have what you really need as a minimum. >>>>> You have ofcourse build all artifacts/modules and they are in >>>>> parent >> >>>>> pom referenced with >>>>> >>>>> <modules> >>>>> <module>yourModule</module> >>>>> <module>yourOtherModule</module> >>>>> </modules> >>>>> >>>>> Also note, the generated site does not work under target dir, you >>>>> have >>>> >>>>> to deploy your site(s) somewhere or else the links will point to >>>>> the >> >>>>> wrong location. >>>>> >>>>> -Ronny >>>>> >>>>> -----Opprinnelig melding----- >>>>> Fra: news [mailto:[EMAIL PROTECTED] P? vegne av Geoffrey De Smet >>>>> Sendt: 19. september 2006 10:49 >>>>> Til: users@maven.apache.org >>>>> Emne: Re: maven site not showing sub module links in parent html >>>>> >>>>> No idea then, it works for us at spring-rich-c.sf.net, maybe you >>>>> can >> >>>>> try comparing the site.xml's etc. >>>>> >>>>> One thing I noticed is that you don't have an <url> element in your > >>>>> parent pom, which gives problems with site inheritance (I opened a >>>>> jira for it) >>>>> >>>>> tulasi wrote, On 2006-09-19 6:15 AM: >>>>>> >>>>>> >>>>>> I have tried these two also. But its not showing in parent html >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Geoffrey De Smet-2 wrote: >>>>>>> Try >>>>>>> >>>>>>> <menu ref="modules" /> >>>>>>> >>>>>>> <menu ref="reports" /> >>>>>>> >>>>>>> >>>>>>> tulasi wrote, On 2006-09-18 2:54 PM: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I have created my /src/site/site.xml and pom.xml like as >> follows. >>> >>>>>>>> But when i am trying create mvn site, its not creating sub >>>>>>>> modules >>> >>>>>>>> links in parent html. Here i have enclosed my site.xml and >>> pom.xml. >>>>>>>> what was wrong in these files?. >>>>>>>> >>>>>>>> Site.xml >>>>>>>> <?xml version="1.0" encoding="UTF-8"?> <project name="My >>>> Framework"> >>>>>>>> <bannerLeft> >>>>>>>> <name>My Framework</name> >>>>>>>> >>>> <src>http://maven.apache.org/images/apache-maven-project.png</src> >>>>>>>> <href>http://maven.apache.org/</href> >>>>>>>> </bannerLeft> >>>>>>>> <bannerRight> >>>>>>>> <src>http://maven.apache.org/images/maven-small.gif</src> >>>>>>>> </bannerRight> >>>>>>>> <skin> >>>>>>>> <groupId>org.apache.maven.skins</groupId> >>>>>>>> <artifactId>maven-default-skin</artifactId> >>>>>>>> <version>1.0</version> >>>>>>>> </skin> >>>>>>>> <body> >>>>>>>> <links> >>>>>>>> <item name="My Framework" >>>> href="../target/site/index.html"/> >>>>>>>> </links> >>>>>>>> ${modules} >>>>>>>> ${reports} >>>>>>>> </body> >>>>>>>> </project> >>>>>>>> >>>>>>>> >>>>>>>> Pom.xml >>>>>>>> >>>>>>>> <?xml version="1.0" encoding="UTF-8"?> <project> >>>>>>>> <modelVersion>4.0.0</modelVersion> >>>>>>>> <groupId>my.id.util</groupId> >>>>>>>> <version>${my_version_number}</version> >>>>>>>> <name>MyFramework</name> >>>>>>>> <artifactId>MyFramework</artifactId> >>>>>>>> <packaging>pom</packaging> >>>>>>>> <distributionManagement> >>>>>>>> <site> >>>>>>>> <id>MyFramework</id> >>>>>>>> <url>scpexe://MyProject/</url> >>>>>>>> </site> >>>>>>>> <snapshotRepository> >>>>>>>> <id>snapshots</id> >>>>>>>> <name>Maven Central Plugins Development > Repository</name> >>>>>>>> >>>>>>>> >>>> <url>scp://repo1.maven.org/home/projects/maven/repository-staging/sn >>>> a >>>> p >>>> sh >>>> ots/maven2</url> >>>>>>>> </snapshotRepository> >>>>>>>> </distributionManagement> >>>>>>>> <build> >>>>>>>> <directory>${lib.dir}</directory> >>>>>>>> <outputDirectory>target</outputDirectory> >>>>>>>> </build> >>>>>>>> <modules> >>>>>>>> <module>subA</module> >>>>>>>> <module>subB</module> >>>>>>>> <module>subC</module> >>>>>>>> <module>subD</module> >>>>>>>> <module>subE</module> >>>>>>>> <module>subF</module> >>>>>>>> </modules> >>>>>>>> <reporting> >>>>>>>> <plugins> >>>>>>>> <plugin> >>>>>>>> <groupId>org.apache.maven.plugins</groupId> >>>>>>>> <artifactId>maven-site-plugin</artifactId> >>>>>>>> <version>2.0-beta-5</version> >>>>>>>> <configuration> >>>>>>>> <locales>en</locales> >>>>>>>> </configuration> >>>>>>>> </plugin> >>>>>>>> </plugins> >>>>>>>> </reporting> >>>>>>>> </project> >>>>>>> -- >>>>>>> With kind regards, >>>>>>> Geoffrey De Smet >>>>>>> >>>>>>> >>>>>>> ----------------------------------------------------------------- >>>>>>> - >>>>>>> - >>>>>>> - >>>>>>> - To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> With kind regards, >>>>> Geoffrey De Smet >>>>> >>>>> >>>>> ------------------------------------------------------------------- >>>>> - >>>>> - 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] >>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/maven-site-not-showing-sub-module-links-in-par >>>> e >>>> n >>>> t- >>>> html-tf2291089.html#a6483743 >>>> 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] >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/maven-site-not-showing-sub-module-links-in-pare >>> n >>> t- >>> html-tf2291089.html#a6485081 >>> 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] >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/maven-site-not-showing-sub-module-links-in-paren >> t- >> html-tf2291089.html#a6485968 >> 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] >> >> >> > > -- > View this message in context: > http://www.nabble.com/maven-site-not-showing-sub-module-links-in-parent- > html-tf2291089.html#a6500143 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > !DSPAM:4518aa25206821300515357! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/maven-site-not-showing-sub-module-links-in-parent-html-tf2291089.html#a6504743 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]