Re: reports inheritance - parent can disinherit, can child refuse to inherit?
no, the child can override, that's all see MNG-2807 for the same about CI management, or MNG-3124 for mailing lists there is an inheritance configuration pattern to find then apply on many elements of the pom. If you have an idea about something easyto understand from a user perspective... Regards, Hervé Le samedi 10 septembre 2011, sebb a écrit : [This mainly applies to the project-info-reports plugin] The reporting/plugins/plugin entries support the inherited element; if set to false, child projects don't inherit the plugin settings, i.e. the parent can disinherit the child. Is the reverse also possible, i.e. given a parent pom, can a child reporting plugin refuse to inherit from its parent? For example, if the parent and most children need the same set of reports, but one child does not need some of the reports. This does not appear to be possible except by defining the required set of reports in each project, parent included. The parent config has to disinherit the children, otherwise they will all get the full set of reports. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: reports inheritance - parent can disinherit, can child refuse to inherit?
On 10 September 2011 15:39, Hervé BOUTEMY herve.bout...@free.fr wrote: no, the child can override, that's all Don't understand what you mean by that. see MNG-2807 for the same about CI management, or MNG-3124 for mailing lists there is an inheritance configuration pattern to find then apply on many elements of the pom. If you have an idea about something easyto understand from a user perspective... The parent can currently do the following to prevent all inheritance reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId inheritedfalse/inherited reportSets However, that does not allow some reports to apply to the parent only; it is all or nothing. Although the inherited element is also allowed within a reportSet, that does not seem to prevent the reports from being generated in Maven 2.2.1. [seems to work in M303, provided that the id is omiitted or has the value default (which is the default) ] There ought to be a way for the parent to specify its own private reports separately from the reports that should be inherited. If the reportSet/inherited element worked properly, that would solve the issue for the parent. Being able to configure the parent to pass on some reports but not others would be helpful in many cases, but equally, its children should be able to refuse reports specified by the parent. Perhaps the combine.children/combine.self configuration attribute could be extended to reportSet? S P.S. Unfortunately, the word inherited is ambiguous; in this case it means will it be inherited, rather than the usual spoken meaning as in the child inherited from its parent. It would perhaps have been clearer if the element was called inheritable; the child version could then be called inherit. But I think that would be too confusing now. Regards, Hervé Le samedi 10 septembre 2011, sebb a écrit : [This mainly applies to the project-info-reports plugin] The reporting/plugins/plugin entries support the inherited element; if set to false, child projects don't inherit the plugin settings, i.e. the parent can disinherit the child. Is the reverse also possible, i.e. given a parent pom, can a child reporting plugin refuse to inherit from its parent? For example, if the parent and most children need the same set of reports, but one child does not need some of the reports. This does not appear to be possible except by defining the required set of reports in each project, parent included. The parent config has to disinherit the children, otherwise they will all get the full set of reports. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Reports: Where are the docs?
Several things: 1) This page: http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html has an example of using the surefire report. Their example gives the version number with SNAPSHOT on the end. That doesn't work. Your example, without a version number, works to generate the junit report 2) There only seems to be a JUnit report on the parent project. I just put the reporting stuff in the parent project's POM. The children don't have it. The children generate reports with all the default text but the children don't seem to generate the JUnit report. Does the one thing inherit and the other not? 3) Your example has the plugins tag duplicated. It should look like this: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting 4) How do I tell it my checkstyle xml configuration file's name so it checks the right stuff. 5) Finally, and its really my fault for asking several questions at once, how do I get it to fill in interesting values for. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository There are currently only defaults in the generated reports. thanks. -- Lee Meador On 12/22/05, Allan Ramirez [EMAIL PROTECTED] wrote: Hi Lee, Have a look in http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F just replace the value in artifactId element to the report plugin you want to generate i.e. reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting junit test report was renamed to surefire report plugin and currently hosted at mojo codehaus plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin /plugins You may also refer to this page for more plugins at codehaus http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Whereistheotherplugin%3F -allan Lee Meador wrote: I want to generate interesting reports. All I have been able to find says that you can get some reports by adding this reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting to the POM. I did that and got a dummy report with nothing interesting in it. Here are the main topics that look like you put some info somewhere to make it appear in the site docs. Maybe someone will fill in some doc links or mention where they go. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository How do I get things (that I remember from a previous project with Maven 1) like: javadoc checkstyle report junit test results lists of recent changes in the source repository Finally, I am generating an EAR with a WAR (or two) and some EJBs and some other JAR files in it. All told there are about 10 parts each with its own POM and a parent pom for building the whole thing. It builds and the report stuff seems to get built for each of the subprojects. Is the parent going to have stuff consolidated from the children or are there going to be links in there somewhere? I'm not sure what I'm going to end up with. Really, I have searched the archives of this list and almost all I can find is folks complaining about the surefire report plugin not working. But I can't even get it to find that plugin in the central repository. And the docs seem to be missing something that I can't seem to see. I have site docs but nothing is in them. -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.3/209 - Release Date: 12/21/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
Re: Reports: Where are the docs?
I'm replying to my own email. Duh? On 12/27/05, Lee Meador [EMAIL PROTECTED] wrote: Several things: 1) This page: http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html has an example of using the surefire report. Their example gives the version number with SNAPSHOT on the end. That doesn't work. Your example, without a version number, works to generate the junit report 2) There only seems to be a JUnit report on the parent project. I just put the reporting stuff in the parent project's POM. The children don't have it. The children generate reports with all the default text but the children don't seem to generate the JUnit report. Does the one thing inherit and the other not? The JUnit report only gets generated if there are JUnit tests in the child project. That makes sense. I was looking for an empty report in a project with no tests yet. Oh well. 3) Your example has the plugins tag duplicated. It should look like this: reporting plugins plugin groupId org.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting 4) How do I tell it my checkstyle xml configuration file's name so it checks the right stuff. 5) Finally, and its really my fault for asking several questions at once, how do I get it to fill in interesting values for. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository There are currently only defaults in the generated reports. One correction, the dependencies section does have lists of any of my projects upon which the project depends and any 3rd party libraries on which it depends--stuff like Spring and commons-logging. thanks. -- Lee Meador And one other thing--is there a way to tie the reports together in some way so you can click around and get to all the related projects or see them in a unified report or something? On 12/22/05, Allan Ramirez [EMAIL PROTECTED] wrote: Hi Lee, Have a look in http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F just replace the value in artifactId element to the report plugin you want to generate i.e. reporting plugins plugin groupId org.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting junit test report was renamed to surefire report plugin and currently hosted at mojo codehaus plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin /plugins You may also refer to this page for more plugins at codehaus http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Whereistheotherplugin%3F -allan Lee Meador wrote: I want to generate interesting reports. All I have been able to find says that you can get some reports by adding this reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting to the POM. I did that and got a dummy report with nothing interesting in it. Here are the main topics that look like you put some info somewhere to make it appear in the site docs. Maybe someone will fill in some doc links or mention where they go. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository How do I get things (that I remember from a previous project with Maven 1) like: javadoc checkstyle report junit test results lists of recent changes in the source repository Finally, I am generating an EAR with a WAR (or two) and some EJBs and some other JAR files in it. All told there are about 10 parts each with its own POM and a parent pom for building the whole thing. It builds and the report stuff seems to get built for each of the subprojects. Is the parent going to have stuff consolidated from the children or are there going to be links in there somewhere? I'm not sure what I'm going to end up with. Really, I have searched the archives of this list and almost all I can find is folks complaining about the surefire report plugin not working. But I
Re: Reports: Where are the docs?
To answer the question about filling in the default informational bits with more interesting stuff, I found this in the source code. I looked in POM.xmlin the root folder of the source. Evidently you put these tags in your parent POM to cause things to get filled in in the docs. I copied some from one POM and some from another but the examples should help. (You can get more information on the tags here - http://maven.apache.org/maven-model/maven.html - search for issueManagement or license to find the part of that page that matters. This page confused me at first. The top part of the page shows all the XML tags that there can be and those tags have links down to the bottom part where there are explanations of what the tags do.) mailingLists mailingList nameDevelopment List/name subscribe[EMAIL PROTECTED]/subscribe unsubscribe[EMAIL PROTECTED]/unsubscribe postdev@mojo.codehaus.org/post archivehttp://archive.mojo.codehaus.org/dev//archive /mailingList /mailingLists issueManagement systemjira/system urlhttp://jira.codehaus.org/browse/MOJO/url /issueManagement scm connectionscm:svn:svn://svn.codehaus.org/mojo/scm/trunk/mojo/connection developerConnectionscm:svn:https://svn.codehaus.org/mojo/trunk/mojo/developerConnection urlhttp://svn.mojo.codehaus.org/trunk/mojo/url /scm ciManagement systemcontinuum/system notifiers notifier configuration addresscommits@maven.apache.org/address /configuration /notifier /notifiers /ciManagement developers developer idjvanzyl/id nameJason van Zyl/name email[EMAIL PROTECTED]/email organizationASF/organization roles rolePMC Chair/role /roles timezone-5/timezone /developer /developers licenses license nameThe Apache Software License, Version 2.0/name urlhttp://www.apache.org/licenses/LICENSE-2.0.txt/url distributionrepo/distribution /license /licenses organization nameApache Software Foundation/name urlhttp://www.apache.org//url /organization On 12/27/05, Lee Meador [EMAIL PROTECTED] wrote: I'm replying to my own email. Duh? On 12/27/05, Lee Meador [EMAIL PROTECTED] wrote: Several things: 1) This page: http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html has an example of using the surefire report. Their example gives the version number with SNAPSHOT on the end. That doesn't work. Your example, without a version number, works to generate the junit report 2) There only seems to be a JUnit report on the parent project. I just put the reporting stuff in the parent project's POM. The children don't have it. The children generate reports with all the default text but the children don't seem to generate the JUnit report. Does the one thing inherit and the other not? The JUnit report only gets generated if there are JUnit tests in the child project. That makes sense. I was looking for an empty report in a project with no tests yet. Oh well. 3) Your example has the plugins tag duplicated. It should look like this: reporting plugins plugin groupId org.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupId org.apache.maven.plugins /groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting 4) How do I tell it my checkstyle xml configuration file's name so it checks the right stuff. 5) Finally, and its really my fault for asking several questions at once, how do I get it to fill in interesting values for. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository There are currently only defaults in the generated reports. One correction, the dependencies section does have lists of any of my projects upon which the project depends and any 3rd party libraries on which it depends--stuff like Spring and commons-logging. thanks. -- Lee Meador And one other thing--is there a way to tie the reports together in some way so you can click around and get to all the related projects or see them in a unified report or something? On 12/22/05, Allan Ramirez [EMAIL PROTECTED] wrote: Hi Lee, Have a look in http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F just replace the value in artifactId element to the report plugin you want to generate i.e. reporting plugins plugin groupId org.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins plugins plugin
Re: Reports: Where are the docs?
I did notice the generated docs seem to assume an HTTPS connection to Subversion for developers. Is there a way to change that text? Or am I making a mistake using svn:// for our developers since it's all on the intranet? (That is sort of off topic though.) On 12/27/05, Lee Meador [EMAIL PROTECTED] wrote: To answer the question about filling in the default informational bits with more interesting stuff, I found this in the source code. I looked in POM.xml in the root folder of the source. Evidently you put these tags in your parent POM to cause things to get filled in in the docs. I copied some from one POM and some from another but the examples should help. (You can get more information on the tags here - http://maven.apache.org/maven-model/maven.html - search for issueManagement or license to find the part of that page that matters. This page confused me at first. The top part of the page shows all the XML tags that there can be and those tags have links down to the bottom part where there are explanations of what the tags do.) mailingLists mailingList nameDevelopment List/name subscribe[EMAIL PROTECTED]/subscribe unsubscribe [EMAIL PROTECTED]/unsubscribe postdev@mojo.codehaus.org/post archive http://archive.mojo.codehaus.org/dev//archive /mailingList /mailingLists issueManagement systemjira/system url http://jira.codehaus.org/browse/MOJO/url /issueManagement scm connectionscm:svn:svn://svn.codehaus.org/mojo/scm/trunk/mojo /connection developerConnectionscm:svn:https://svn.codehaus.org/mojo/trunk/mojo/developerConnection url http://svn.mojo.codehaus.org/trunk/mojo/url /scm ciManagement systemcontinuum/system notifiers notifier configuration addresscommits@maven.apache.org/address /configuration /notifier /notifiers /ciManagement developers developer idjvanzyl/id nameJason van Zyl/name email [EMAIL PROTECTED]/email organizationASF/organization roles rolePMC Chair/role /roles timezone-5/timezone /developer /developers licenses license nameThe Apache Software License, Version 2.0/name url http://www.apache.org/licenses/LICENSE-2.0.txt/url distributionrepo/distribution /license /licenses organization nameApache Software Foundation/name urlhttp://www.apache.org//url /organization On 12/27/05, Lee Meador [EMAIL PROTECTED] wrote: I'm replying to my own email. Duh? On 12/27/05, Lee Meador [EMAIL PROTECTED] wrote: Several things: 1) This page: http://mojo.codehaus.org/surefire-report-maven-plugin/howto.html has an example of using the surefire report. Their example gives the version number with SNAPSHOT on the end. That doesn't work. Your example, without a version number, works to generate the junit report 2) There only seems to be a JUnit report on the parent project. I just put the reporting stuff in the parent project's POM. The children don't have it. The children generate reports with all the default text but the children don't seem to generate the JUnit report. Does the one thing inherit and the other not? The JUnit report only gets generated if there are JUnit tests in the child project. That makes sense. I was looking for an empty report in a project with no tests yet. Oh well. 3) Your example has the plugins tag duplicated. It should look like this: reporting plugins plugin groupId org.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin plugin groupId org.apache.maven.plugins /groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting 4) How do I tell it my checkstyle xml configuration file's name so it checks the right stuff. 5) Finally, and its really my fault for asking several questions at once, how do I get it to fill in interesting values for. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository There are currently only defaults in the generated reports. One correction, the dependencies section does have lists of any of my projects upon which the project depends and any 3rd party libraries on which it depends--stuff like Spring and commons-logging. thanks. -- Lee Meador And one other thing--is there a way to tie the reports together in some way so you can click around and get to all the related projects or see them in a unified report or something? On 12/22/05, Allan Ramirez [EMAIL PROTECTED] wrote: Hi Lee, Have a look in
Re: Reports: Where are the docs?
This is an M2 question. On 12/22/05, Lee Meador [EMAIL PROTECTED] wrote: I want to generate interesting reports. All I have been able to find says that you can get some reports by adding this reporting plugins plugin groupId org.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting to the POM. I did that and got a dummy report with nothing interesting in it. Here are the main topics that look like you put some info somewhere to make it appear in the site docs. Maybe someone will fill in some doc links or mention where they go. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository How do I get things (that I remember from a previous project with Maven 1) like: javadoc checkstyle report junit test results lists of recent changes in the source repository Finally, I am generating an EAR with a WAR (or two) and some EJBs and some other JAR files in it. All told there are about 10 parts each with its own POM and a parent pom for building the whole thing. It builds and the report stuff seems to get built for each of the subprojects. Is the parent going to have stuff consolidated from the children or are there going to be links in there somewhere? I'm not sure what I'm going to end up with. Really, I have searched the archives of this list and almost all I can find is folks complaining about the surefire report plugin not working. But I can't even get it to find that plugin in the central repository. And the docs seem to be missing something that I can't seem to see. I have site docs but nothing is in them. -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
Re: Reports: Where are the docs?
Hi Lee, Have a look in http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Creports%3EfromMaven1toMaven2%3F just replace the value in artifactId element to the report plugin you want to generate i.e. reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin /plugins /reporting junit test report was renamed to surefire report plugin and currently hosted at mojo codehaus plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin /plugins You may also refer to this page for more plugins at codehaus http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Whereistheotherplugin%3F -allan Lee Meador wrote: I want to generate interesting reports. All I have been able to find says that you can get some reports by adding this reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin /plugins /reporting to the POM. I did that and got a dummy report with nothing interesting in it. Here are the main topics that look like you put some info somewhere to make it appear in the site docs. Maybe someone will fill in some doc links or mention where they go. Document Description Continuous Integration Dependencies Issue Tracking Mailing Lists Project License Project Team Source Repository How do I get things (that I remember from a previous project with Maven 1) like: javadoc checkstyle report junit test results lists of recent changes in the source repository Finally, I am generating an EAR with a WAR (or two) and some EJBs and some other JAR files in it. All told there are about 10 parts each with its own POM and a parent pom for building the whole thing. It builds and the report stuff seems to get built for each of the subprojects. Is the parent going to have stuff consolidated from the children or are there going to be links in there somewhere? I'm not sure what I'm going to end up with. Really, I have searched the archives of this list and almost all I can find is folks complaining about the surefire report plugin not working. But I can't even get it to find that plugin in the central repository. And the docs seem to be missing something that I can't seem to see. I have site docs but nothing is in them. -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.3/209 - Release Date: 12/21/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reports not working?
2005/7/27, Brett Porter [EMAIL PROTECTED]: Are the 3 reports the ones in your parent pom? In the parent pom there's only 1 report: reports reportmaven-license-plugin/report /reports And that one is working. The others should be present in the subdirectories of each project. Yup, each pom in the modules/MyModule dir has its own set of reports defined. If that is still not working, check if it works when you run site:site on the individual project. Running 'maven site:site' inside 1 of the modules gives me a 'Goal site:site does not exist' error, but running 'maven site' builds sucessfully -- however, it still only gives me those 3 reports, even though i defined 11 reports in the pom. I've tried removing the 'extend' tag present in the modules' pom, but still gives me the same thing. Damn :/ Any ideas anyone? Cheers, J.V. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reports not working?
seems odd. watch the goals going past, in particular register and deregister. That might shed some light. Check maven.xml (including an inherited one) for calls to those goals, as well as any plugins you might be using. HTH, Brett On 7/28/05, Joao Victor [EMAIL PROTECTED] wrote: 2005/7/27, Brett Porter [EMAIL PROTECTED]: Are the 3 reports the ones in your parent pom? In the parent pom there's only 1 report: reports reportmaven-license-plugin/report /reports And that one is working. The others should be present in the subdirectories of each project. Yup, each pom in the modules/MyModule dir has its own set of reports defined. If that is still not working, check if it works when you run site:site on the individual project. Running 'maven site:site' inside 1 of the modules gives me a 'Goal site:site does not exist' error, but running 'maven site' builds sucessfully -- however, it still only gives me those 3 reports, even though i defined 11 reports in the pom. I've tried removing the 'extend' tag present in the modules' pom, but still gives me the same thing. Damn :/ Any ideas anyone? Cheers, J.V. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reports not working?
Are the 3 reports the ones in your parent pom? In the top level, only those will be present. The others should be present in the subdirectories of each project. If that is still not working, check if it works when you run site:site on the individual project. Cheers, Brett On 7/28/05, Joao Victor [EMAIL PROTECTED] wrote: Hello, I've been trying to get some reports working, with no sucess; so i'm sending this email in the hopes someone can point me some solution. I'm using a multiproject:site target, i've got 5 modules under the main the project. For each of these modules, i'd like to get some reports. So i just put in their project.xml: -- reports reportmaven-pmd-plugin/report reportmaven-simian-plugin/report reportmaven-junit-report-plugin/report reportmaven-jcoverage-plugin/report reportmaven-checkstyle-plugin/report reportmaven-jdepend-plugin/report reportmaven-statcvs-plugin/report reportmaven-file-activity-plugin/report reportmaven-developer-activity-plugin/report reportmaven-jxr-plugin/report reportmaven-javadoc-plugin/report /reports -- And run 'maven multiproject:site'. It takes a while, and then i take a look at the html... only 3 reports are there: file-activity, statcvs, and developer-activity. I've got no idea why the other reports weren't made. The command 'maven multiproject:site' is finished sucessfully, there's no error message. Any ideas? Thanks, J.V. - 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: Reports are empty running under Maven
I'm running jcoverage reports for our projects, and haven't seen anything like this. I see a jcoverage.ser file in the root of every project, but that's it. Do any of your tests change the current directory or do anything else with the file system? -Original Message- From: Nelson, Jim [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 9:21 PM To: 'users@maven.apache.org' Subject: Reports are empty running under Maven Running jcoverage from Maven, generates reports with 0 hits. Interstingly, two jcoverage.ser files are generated, one in the root directory of the project and one alongside the test classes. It appears that the one in the root directory gets created when the classes are instrumented, and then it never gets updated again. The one in the test classes appears to be updated as junit is running the unit tests on the instrumented classes. Any ideas? - 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: Reports
Try: reportmaven-junit-report-plugin/report -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 16 July 2004 12:45 To: [EMAIL PROTECTED] Subject: Reports I want to set up my projects to only run a sub-set of the default reports when doing the site goal. I'm having a bit of trouble working out what values to specify in the POM though. e.g. reports reportmaven-javadoc-plugin/report !-- Works -- reportmaven-test-plugin/report !-- Doesn't Work -- /reports All I can find in the docs is the assertion that the middle section should match the plugin, but in the case of the report for the Junit tests this doesn't seem to hold true. Can somebody enlighten me. ta vm James -- -- For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. -- -- - 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]
