Re: [M2] Site Generation
You need to deploy or stage the site to have links between modules working Siarhei On Sat, Apr 12, 2008 at 2:14 PM, sylsau [EMAIL PROTECTED] wrote: Hello, I am testing maven 2 and I saw that is was a possibility to generate a site who lists the project's documentation. My project has the following form : - pom.xml (super POM) - moduleA/ with a pom.xml - moduleB/ with a pom.xml The content of my the super POM is the following : [CODE] 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 groupIdfr.projet/groupId artifactIdprojet/artifactId packagingpom/packaging version0.1/version nameProjet !/name modules modulemoduleA/module modulemoduleB/module /modules dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId configuration minmemory128m/minmemory maxmemory512m/maxmemory /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jxr-plugin/artifactId /plugin plugin artifactIdmaven-clover-plugin/artifactId /plugin /plugins /reporting /project [/CODE] The pom's of the modules are almost the same and are like that : [CODE] 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 artifactIdmoduleA/artifactId packagingjar/packaging nameModule A/name parent groupIdfr.projet/groupId artifactIdprojet/artifactId version0.1/version relativePath../pom.xml/relativePath /parent /project [/CODE] When i use mvn site command, the site is well generated. The target directory is created in the same directory that the super POM, but there is also a directory target that is created in the modules' directories. When i display the site, in the modules part on the left menu, the list with my 2 modules is well displayed. However, there is a problem with the links of theses modules. The links don't redirect correctly to the modules' target. Their form is like that : ... maven/target/site/moduleB/index.html whereas the real path of this is the following : maven/moduleB/target/site/index.html . Do you know how I can do to generate the modules' target in the target of the super POM ? or in the other case how I can change the links ? Thanks for your help. Sylvain. -- View this message in context: http://www.nabble.com/-M2--Site-Generation-tp16648682s177p16648682.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]
Re: [M2] Site Generation
First, I use the command mvn site then I run the command mvn site:stage. The result is the same, the links are not good. So, perhars there are values to put in the tag url on the pom ? -- View this message in context: http://www.nabble.com/-M2--Site-Generation-tp16648682s177p16656455.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]
Re: [M2] Site Generation
depends on access capability to the urls especially the required plugins an example would be distributionManagement repository idapache-repo/id nameMaven Central Repository/name urlscpexe://people.apache.org//www/people.apache.org/repo/m2-ibiblio-rsync -repository/url /repository snapshotRepository idapache-snapshots/id nameApache Development Repository/name urlscpexe://people.apache.org//www/people.apache.org/repo/m2-snapshot-repo sitory/url /snapshotRepository /distributionManagement If you cant reach the urls using the indicated protocol scp/sftp/whatever protocol maybe the site is down? you can *try* pulling all your plugins locally to a localRepository but that will take a while Here is an localRepository example from settings.xml localRepositoryF:/maven-plugin/localRepository HTH M- - Original Message - From: sylsau [EMAIL PROTECTED] To: users@maven.apache.org Sent: Saturday, April 12, 2008 4:24 PM Subject: Re: [M2] Site Generation First, I use the command mvn site then I run the command mvn site:stage. The result is the same, the links are not good. So, perhars there are values to put in the tag url on the pom ? -- View this message in context: http://www.nabble.com/-M2--Site-Generation-tp16648682s177p16656455.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]
Re: [M2] Site Generation
On Sat, Apr 12, 2008 at 6:53 PM, Martin Gainty [EMAIL PROTECTED] wrote: depends on access capability to the urls especially the required plugins an example would be I don't see how this has anything to do with access. The generated URLs are just plain wrong, AFAICT. The only solution that I have been able to come up with is to run an Ant script (using maven-antrun-plugin) that generates some symbolic links so that the generated URLs work. It's ugly but at least the site works. I'd love to see a better solution especially since this was apparently fixed in maven-site-plugin-2.0-beta-5 (MSITE-44). According to MSITE-275, it was broken again in maven-site-plugin-2.0-beta-6. That seems to imply somebody got it working in 2.0-beta-5. :-) http://jira.codehaus.org/browse/MSITE-44 http://jira.codehaus.org/browse/MSITE-275 Cheers, Hilco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site generation - Custom file with left right and top banners.
Hi Arnaud, Thanks for letting me know that it works similar to the way it works in Maven1. That did the trick. Thanks for the link http://www.oqube.com/projects/oqube-skin/index.html. Informative and i am sure it is going to come handy after some time. Found this link too, can be useful too: http://coderoshi.blogspot.com/2007/02/generating-site-and-documentation-in.html Vijay Venkataraman Arnaud Bailly wrote: Vijay Venkataraman [EMAIL PROTECTED] writes: Hi, Hi Vijay, Problem When i click on the user guide / developer guide link, they open in the same window replacing the existing one. I want them to open in the right hand side, just as it happens for other standard reports, showing the top banner,showing links in the left side. Is there a specific format or extra setting that i have to do? Maven copy html files (and whatever is located in src/site/resources) verbatim (or maybe filtered ?) to your site's target dir. So your HTML files do not get decorated with the site' skin, which is the artifact that defines how the site is laid out. To have your documentation correctly formatted, if you already have HTML sources, you could use XDOC format which is nearly equivalent to HTML: just remove html/head tags and replace with document (http://maven.apache.org/maven-1.x/using/site.html). You then need to put your documents in xdoc format into a src/site/xdoc directory, give them xml extension and it should be ok. Here is a short tutorial I wrote on creating custom skins, there are other ones out there: http://www.oqube.com/projects/oqube-skin/index.html HTH
Re: [m2] site generation - Custom file with left right and top banners.
Vijay Venkataraman [EMAIL PROTECTED] writes: Found this link too, can be useful too: http://coderoshi.blogspot.com/2007/02/generating-site-and-documentation-in.html Great link, thank you. I have added it to my references. Glad you found my musing useful :-) regards, -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site generation - Custom file with left right and top banners.
Vijay Venkataraman [EMAIL PROTECTED] writes: Hi, Hi Vijay, Problem When i click on the user guide / developer guide link, they open in the same window replacing the existing one. I want them to open in the right hand side, just as it happens for other standard reports, showing the top banner,showing links in the left side. Is there a specific format or extra setting that i have to do? Maven copy html files (and whatever is located in src/site/resources) verbatim (or maybe filtered ?) to your site's target dir. So your HTML files do not get decorated with the site' skin, which is the artifact that defines how the site is laid out. To have your documentation correctly formatted, if you already have HTML sources, you could use XDOC format which is nearly equivalent to HTML: just remove html/head tags and replace with document (http://maven.apache.org/maven-1.x/using/site.html). You then need to put your documents in xdoc format into a src/site/xdoc directory, give them xml extension and it should be ok. Here is a short tutorial I wrote on creating custom skins, there are other ones out there: http://www.oqube.com/projects/oqube-skin/index.html HTH -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2: Site generation failed for multi-module projects
On 12/1/06, Kenny Cheang [EMAIL PROTECTED] wrote: Does anyone know what the problem might be? I mentioned that the mvn compile and mvn package works fine when I execute these commands in parent project directory. But if I execute them in module B directory, I will get the same error. Any help is appreciated! Maven is repository based. By using 'mvn compile' and 'mvn package' you are just building things under 'target', and never installing them in your local repository. You'll need to 'mvn install' to put them in your local repository (or 'mvn deploy' if you're working with others and using a remote repository). http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2: Site generation failed for multi-module projects
Thanks for your reply. I did 'mvn install' and 'mvn deploy' already. The dependency jar file has been installed in my local repository and internal repository. Any other ideas? Thanks! Kenny On 2006.12.02 08:36:10 -0700, Wendy Smoak wrote: On 12/1/06, Kenny Cheang [EMAIL PROTECTED] wrote: Does anyone know what the problem might be? I mentioned that the mvn compile and mvn package works fine when I execute these commands in parent project directory. But if I execute them in module B directory, I will get the same error. Any help is appreciated! Maven is repository based. By using 'mvn compile' and 'mvn package' you are just building things under 'target', and never installing them in your local repository. You'll need to 'mvn install' to put them in your local repository (or 'mvn deploy' if you're working with others and using a remote repository). http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] pgpJ4WaU7Tl63.pgp Description: signature
Re: M2: Site generation failed for multi-module projects
On 12/2/06, kcheang [EMAIL PROTECTED] wrote:
Thanks for your reply. I did 'mvn install' and 'mvn deploy' already. The
dependency jar file has been installed in my local repository and
internal repository. Any other ideas? Thanks!
Your original error message had:
1) com.kswiss.xi:xi-core:jar:${project-version}
Is that a property that you're setting? Or do you mean
${project.version} instead ?
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2: Site generation failed for multi-module projects
LOL. I followed an exmaple in the Maven book by Mergere. They had the
typo project-version instead of the project.version. Everything
works now. Thanks for your help!
Kenny
On 2006.12.02 14:46:22 -0700, Wendy Smoak wrote:
On 12/2/06, kcheang [EMAIL PROTECTED] wrote:
Thanks for your reply. I did 'mvn install' and 'mvn deploy' already. The
dependency jar file has been installed in my local repository and
internal repository. Any other ideas? Thanks!
Your original error message had:
1) com.kswiss.xi:xi-core:jar:${project-version}
Is that a property that you're setting? Or do you mean
${project.version} instead ?
--
Wendy
pgpdpTYAkunFU.pgp
Description: signature
Re: [M2] site generation - tests run twice
Might be related to: http://jira.codehaus.org/browse/MSUREFIREREP-6 Wayne On 5/9/06, Szczepan Faber [EMAIL PROTECTED] wrote: What's the easiest way to make 'mvn site' goal run tests just once? If cobertura is among reporting plugins, tests are run twice. Thanks, Szczepan - 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]
Re: [M2] site generation
After quick glance into the source code I noticed that (as you adviced) that I need name :/ Thanks --- Always feel stupid after posting dummy question on group On 4/30/06, Arik Kfir [EMAIL PROTECTED] wrote: Have you defined your project name (namemyProjectName/name) in your pom.xml file? On 4/30/06, Szczepan Faber [EMAIL PROTECTED] wrote: What's the easiest way to get rid of 'About Unnamed... project name' link on first page (left banner), after running mvn site? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] site generation
its ok - perhaps a FAQ is in order here...I'll create a patch for and submit it ;-) On 4/30/06, Szczepan Faber [EMAIL PROTECTED] wrote: After quick glance into the source code I noticed that (as you adviced) that I need name :/ Thanks --- Always feel stupid after posting dummy question on group On 4/30/06, Arik Kfir [EMAIL PROTECTED] wrote: Have you defined your project name (namemyProjectName/name) in your pom.xml file? On 4/30/06, Szczepan Faber [EMAIL PROTECTED] wrote: What's the easiest way to get rid of 'About Unnamed... project name' link on first page (left banner), after running mvn site? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org
Re: [M2] site generation
Have you defined your project name (namemyProjectName/name) in your pom.xml file? On 4/30/06, Szczepan Faber [EMAIL PROTECTED] wrote: What's the easiest way to get rid of 'About Unnamed... project name' link on first page (left banner), after running mvn site? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- __ Cheers, Arik Kfir [EMAIL PROTECTED] Linux user, number 415067 - http://counter.li.org/ http://corleon.dnsalias.org
RE: [m2] Site generation and info from xxx-mojos.xml
Hi However the maven-plugin-plugin overwrites the index.apt file that I had!!! Can't one have both? Hermod -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Thursday, March 16, 2006 8:40 AM To: Maven Users List Subject: Re: [m2] Site generation and info from xxx-mojos.xml take a look at the pom file of http://mojo.codehaus.org/changes-maven-plugin/announcement-mail-mojo.html and perhaps its parents to see how it is configure. -D On 3/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi That is what I have been running, but the thing is that is does not generate anything as far as documenting the properties etc of the mojo's. Thats the reason I asked if there is any special property (configuration) that is need for having the site plugin do that. I do not like the idea of having to maintain the documentation two places (on a page in the site and in the xxx-mojos.xml file). Hermod -Original Message- From: John Tolentino [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 10:15 AM To: Maven Users List Subject: Re: [m2] Site generation and info from xxx-mojos.xml Hi Hermond, Yes. It's maven-site-plugin. Try: mvn site:site http://maven.apache.org/plugins/maven-site-plugin/ http://maven.apache.org/guides/mini/guide-site.html Regards, John [EMAIL PROTECTED] wrote: Hi Is there any setting or plugin that will document the mojo for building the site, i.e the paramaters etc? I am thinking of having it generate something like this : http://mojo.codehaus.org/changes-maven-plugin/announcement-mail-mojo.html Hermod * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - 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] - 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]
Re: [m2] Site generation and info from xxx-mojos.xml
Hi Hermond, Yes. It's maven-site-plugin. Try: mvn site:site http://maven.apache.org/plugins/maven-site-plugin/ http://maven.apache.org/guides/mini/guide-site.html Regards, John [EMAIL PROTECTED] wrote: Hi Is there any setting or plugin that will document the mojo for building the site, i.e the paramaters etc? I am thinking of having it generate something like this : http://mojo.codehaus.org/changes-maven-plugin/announcement-mail-mojo.html Hermod * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - 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]
RE: [m2] Site generation and info from xxx-mojos.xml
Hi That is what I have been running, but the thing is that is does not generate anything as far as documenting the properties etc of the mojo's. Thats the reason I asked if there is any special property (configuration) that is need for having the site plugin do that. I do not like the idea of having to maintain the documentation two places (on a page in the site and in the xxx-mojos.xml file). Hermod -Original Message- From: John Tolentino [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 10:15 AM To: Maven Users List Subject: Re: [m2] Site generation and info from xxx-mojos.xml Hi Hermond, Yes. It's maven-site-plugin. Try: mvn site:site http://maven.apache.org/plugins/maven-site-plugin/ http://maven.apache.org/guides/mini/guide-site.html Regards, John [EMAIL PROTECTED] wrote: Hi Is there any setting or plugin that will document the mojo for building the site, i.e the paramaters etc? I am thinking of having it generate something like this : http://mojo.codehaus.org/changes-maven-plugin/announcement-mail-mojo.html Hermod * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Site generation and info from xxx-mojos.xml
take a look at the pom file of http://mojo.codehaus.org/changes-maven-plugin/announcement-mail-mojo.html and perhaps its parents to see how it is configure. -D On 3/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi That is what I have been running, but the thing is that is does not generate anything as far as documenting the properties etc of the mojo's. Thats the reason I asked if there is any special property (configuration) that is need for having the site plugin do that. I do not like the idea of having to maintain the documentation two places (on a page in the site and in the xxx-mojos.xml file). Hermod -Original Message- From: John Tolentino [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 10:15 AM To: Maven Users List Subject: Re: [m2] Site generation and info from xxx-mojos.xml Hi Hermond, Yes. It's maven-site-plugin. Try: mvn site:site http://maven.apache.org/plugins/maven-site-plugin/ http://maven.apache.org/guides/mini/guide-site.html Regards, John [EMAIL PROTECTED] wrote: Hi Is there any setting or plugin that will document the mojo for building the site, i.e the paramaters etc? I am thinking of having it generate something like this : http://mojo.codehaus.org/changes-maven-plugin/announcement-mail-mojo.html Hermod * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site generation and multiple modules
If I (by hand) make directories corresponding to the modules in /usr/local/tomcat/webapps/ROOT/docs/project then site-deploy at least completes without errors. distributionManagement site idwebsite/id urlfile:///usr/local/tomcat/webapps/ROOT/docs/project//url /site /distributionManagement However the main project site I'd have hoped would have links to the module sites :( but it doesn't, is there a way to make this happen? I tried adding a site.xml file as described in the docs just to see what would happen but it doesn't seem to have any affect. On 11/29/05, Xavier Toth [EMAIL PROTECTED] wrote: I'm trying to generate a site for a multiple module project. When I generate the site each modules gets its own target/site directory. However when I try and deploy the site it appears to be trying to copy all files from the root project target/site directory. Has anyone else worked thru this issue, if so how?
Re: [m2] site generation and multiple modules
See MNG-661 in JIRA. On 11/30/05, Xavier Toth [EMAIL PROTECTED] wrote: If I (by hand) make directories corresponding to the modules in /usr/local/tomcat/webapps/ROOT/docs/project then site-deploy at least completes without errors. distributionManagement site idwebsite/id urlfile:///usr/local/tomcat/webapps/ROOT/docs/project//url /site /distributionManagement However the main project site I'd have hoped would have links to the module sites :( but it doesn't, is there a way to make this happen? I tried adding a site.xml file as described in the docs just to see what would happen but it doesn't seem to have any affect. On 11/29/05, Xavier Toth [EMAIL PROTECTED] wrote: I'm trying to generate a site for a multiple module project. When I generate the site each modules gets its own target/site directory. However when I try and deploy the site it appears to be trying to copy all files from the root project target/site directory. Has anyone else worked thru this issue, if so how? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site generation problem
The mojo repository is the same as the main one, however this plugin has not been released. svn co https://svn.codehaus.org/mojo/trunk build the plugin from there using: m2 install -DupdateReleaseInfo=true and it should be fine. - Brett On 10/6/05, farid [EMAIL PROTECTED] wrote: Vincent Siveton a écrit : Hi Farid, I am not an expert of this plugin. But, instead of the jdepend itself, you should add the jdepend maven plugin: http://mojo.codehaus.org/jdepend-maven-plugin/howto.html Thanx for the info but I tried that and I think that I miss a repository here. Should I just add a repository in my POM or is there something else that I should do ? In short what is the URL of the mojo repository ? I think that I'm close to write a beginner beginner's guide :) Thanks, Farid - 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]
Re: [m2] site generation problem
It should generate the mailing lists and such. The default report registered is only the project info reports though. If you'd like other plugins, you must add them to the list of reporting plugins in your pom. - Brett On 10/6/05, farid [EMAIL PROTECTED] wrote: Hi everybody I'm new on the list and new at m2 as well. I was just wondering why m2 site:site doesn't generate a complete site with code analysis and all the project infos (like mailing list and such...) Thanks in advance, Farid - 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]
Re: [m2] site generation problem
Brett Porter a écrit : It should generate the mailing lists and such. The default report registered is only the project info reports though. If you'd like other plugins, you must add them to the list of reporting plugins in your pom. Thanks for the Info but I stumbled on an NPE while trying to add the jdepend plugin in my POM. Basically it went like this: reporting plugins plugin groupIdjdepend/groupId artifactIdjdepend/artifactId version2.7/version /plugin /plugins /reporting But after running m2 site:site I fell on this: (sorry for the length of the message) Any idea ? I tried to search for arelevant issue but found none... [INFO] Searching repository for plugin with prefix: 'site'. [INFO] [INFO] Building com.cnc.commandes:commandes:jar:1.0-SNAPSHOT [INFO]task-segment: [site:site] [INFO] --- constituent[0]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/commons-cli-1.0.jar constituent[1]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/doxia-sink-api-1.0-alpha-4.jar constituent[2]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/jline-0.9.1.jar constituent[3]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/jsch-0.1.21.jar constituent[4]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-artifact-2.0-beta-2.jar constituent[5]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-artifact-manager-2.0-beta-2.jar constituent[6]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-core-2.0-beta-2.jar constituent[7]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-model-2.0-beta-2.jar constituent[8]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-monitor-2.0-beta-2.jar constituent[9]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-plugin-api-2.0-beta-2.jar constituent[10]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-plugin-descriptor-2.0-beta-2.jar constituent[11]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-plugin-registry-2.0-beta-2.jar constituent[12]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-profile-2.0-beta-2.jar constituent[13]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-project-2.0-beta-2.jar constituent[14]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-reporting-api-2.0-beta-2.jar constituent[15]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-repository-metadata-2.0-beta-2.jar constituent[16]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-settings-2.0-beta-2.jar constituent[17]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/plexus-input-handler-1.0-alpha-2.jar constituent[18]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-file-1.0-alpha-4.jar constituent[19]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-http-lightweight-1.0-alpha-4.jar constituent[20]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-provider-api-1.0-alpha-4.jar constituent[21]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-ssh-1.0-alpha-4.jar --- java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:297) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:187) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultPluginManager.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:624) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:595) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:497) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:136) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:216) at org.apache.maven.cli.MavenCli.main(MavenCli.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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) - To
RE: [m2] site generation problem
Hi Farid, I am not an expert of this plugin. But, instead of the jdepend itself, you should add the jdepend maven plugin: http://mojo.codehaus.org/jdepend-maven-plugin/howto.html Cheers, Vincent -Original Message- From: farid [mailto:[EMAIL PROTECTED] Sent: Thursday, October 06, 2005 7:27 AM To: Maven Users List Subject: Re: [m2] site generation problem Brett Porter a écrit : It should generate the mailing lists and such. The default report registered is only the project info reports though. If you'd like other plugins, you must add them to the list of reporting plugins in your pom. Thanks for the Info but I stumbled on an NPE while trying to add the jdepend plugin in my POM. Basically it went like this: reporting plugins plugin groupIdjdepend/groupId artifactIdjdepend/artifactId version2.7/version /plugin /plugins /reporting But after running m2 site:site I fell on this: (sorry for the length of the message) Any idea ? I tried to search for arelevant issue but found none... [INFO] Searching repository for plugin with prefix: 'site'. [INFO] -- -- [INFO] Building com.cnc.commandes:commandes:jar:1.0-SNAPSHOT [INFO]task-segment: [site:site] [INFO] -- -- --- constituent[0]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/commons-cli-1.0.jar constituent[1]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/doxia-sink-api-1.0-alpha-4.jar constituent[2]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/jline-0.9.1.jar constituent[3]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/jsch-0.1.21.jar constituent[4]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-artifact-2.0-beta-2.jar constituent[5]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-artifact-manager-2.0- beta-2.jar constituent[6]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-core-2.0-beta-2.jar constituent[7]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-model-2.0-beta-2.jar constituent[8]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-monitor-2.0-beta-2.jar constituent[9]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-plugin-api-2.0-beta-2.jar constituent[10]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-plugin-descriptor-2.0- beta-2.jar constituent[11]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-plugin-registry-2.0-beta- 2.jar constituent[12]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-profile-2.0-beta-2.jar constituent[13]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-project-2.0-beta-2.jar constituent[14]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-reporting-api-2.0-beta- 2.jar constituent[15]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-repository-metadata-2.0- beta-2.jar constituent[16]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/maven-settings-2.0-beta-2.jar constituent[17]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/plexus-input-handler-1.0-alpha- 2.jar constituent[18]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-file-1.0-alpha-4.jar constituent[19]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-http-lightweight-1.0- alpha-4.jar constituent[20]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-provider-api-1.0-alpha- 4.jar constituent[21]: file:/c:/Softs/Outils/maven-2.0-beta-2/lib/wagon-ssh-1.0-alpha-4.jar --- java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManage r.java:297) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Default PluginManager.java:187) at org.apache.maven.plugin.DefaultPluginManager.verifyReportPlugin(DefaultPlu ginManager.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLife cycleExecutor.java:624) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLife cycleExecutor.java:595) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi fecycleExecutor.java:497) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal( DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLif ecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(De faultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecyc leExecutor.java:136) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:216) at org.apache.maven.cli.MavenCli.main(MavenCli.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke
Re: [m2] site generation problem
Vincent Siveton a écrit : Hi Farid, I am not an expert of this plugin. But, instead of the jdepend itself, you should add the jdepend maven plugin: http://mojo.codehaus.org/jdepend-maven-plugin/howto.html Thanx for the info but I tried that and I think that I miss a repository here. Should I just add a repository in my POM or is there something else that I should do ? In short what is the URL of the mojo repository ? I think that I'm close to write a beginner beginner's guide :) Thanks, Farid - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2 site generation problem
Do you have a site descriptor and some files in apt and xdoc directories? Emmanuel Rodrigo Paes wrote: Hi all, I’m having some troubles with site generation. It seams that no documents are being generated, except images and css. I have attached to this email 3 files: - tree.txt contains my project directory structure. - poms contains the pom.xml files that I’m using - log.txt contains the output generated when I try to run: m2 site:site What am I doing wrong? Rodrigo Paes PHD Student - Computer Science - PUC-Rio - [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Messenger - [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Web-page: http://www.teccomm.les.inf.puc-rio.br/rodrigo/ Só existem duas certezas na vida: a morte e os impostos \Imoveis\.classpath \Imoveis\.project \Imoveis\imoveis-app \Imoveis\imoveis-web \Imoveis\pom.xml \Imoveis\target \Imoveis\imoveis-app\pom.xml \Imoveis\imoveis-app\src \Imoveis\imoveis-app\target \Imoveis\imoveis-app\src\main \Imoveis\imoveis-app\src\site \Imoveis\imoveis-app\src\test \Imoveis\imoveis-app\src\main\java \Imoveis\imoveis-app\src\main\java\com \Imoveis\imoveis-app\src\main\java\com\mycompany \Imoveis\imoveis-app\src\main\java\com\mycompany\app \Imoveis\imoveis-app\src\main\java\com\mycompany\app\MyApp.java \Imoveis\imoveis-app\src\site\apt \Imoveis\imoveis-app\src\site\fml \Imoveis\imoveis-app\src\site\xdoc \Imoveis\imoveis-app\src\test\java \Imoveis\imoveis-app\src\test\java\com \Imoveis\imoveis-app\src\test\java\com\mycompany \Imoveis\imoveis-app\src\test\java\com\mycompany\app \Imoveis\imoveis-app\src\test\java\com\mycompany\app\AppTest.java \Imoveis\imoveis-web\pom.xml \Imoveis\imoveis-web\pom.xml.bak \Imoveis\imoveis-web\src \Imoveis\imoveis-web\target \Imoveis\imoveis-web\src\main \Imoveis\imoveis-web\src\main\resources \Imoveis\imoveis-web\src\main\webapp \Imoveis\imoveis-web\src\main\webapp\index.jsp \Imoveis\imoveis-web\src\main\webapp\WEB-INF \Imoveis\imoveis-web\src\main\webapp\WEB-INF\web.xml C:\dev\eclipse3.0\workspace\Imoveism2 site:site [INFO] - --- [INFO] Building rodrigopaes:imoveis:pom:1.0-SNAPSHOT [INFO] - --- [INFO] maven-site-plugin: resolved to version 2.0-alpha-2 from local repository [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus .velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] ** [INFO] Starting Jakarta Velocity v1.4 [INFO] RuntimeInstance initializing. [INFO] Default Properties File: org\apache\velocity\runtime\defaults\velocity.pr operties [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime. resource.ResourceManagerImpl) [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLo aderResourceLoader [INFO] ClasspathResourceLoader : initialization starting. [INFO] ClasspathResourceLoader : initialization complete. [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource. ResourceCacheImpl) [INFO] Default ResourceManager initialization complete. [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [INFO] Created: 20 parsers. [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org .apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'V M_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be glob al in scope if allowed. [INFO] Velocimacro : messages on : VM system will output logging messages [INFO] Velocimacro : autoload off : VM system will not automatically reload glo bal library macros [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [site:site] [INFO] - --- [INFO] BUILD SUCCESSFUL
