Re: qalab.xml does not exist.
That worked great. But now, there are no png images being created for the
graph
Any ideas why?
On 10/14/06, Guillaume Tardif [EMAIL PROTECTED] wrote:
To avoid any dependancy between the build phases
(compile/test/verify/install) and site generation, link your qlab execution
to phase pre-site instead of verify
Guillaume
-Message d'origine-
De: Mick Knutson [mailto:[EMAIL PROTECTED]
Envoyé: samedi 14 octobre 2006 01:49
À: maven
Objet: Re: qalab.xml does not exist.
Seems I am getting further, but still issues with QALab
I have all my artifacts in sub-modules. So I find that to allow this to
work
correctly, I have to:
1. Create a dependancyManagement plugin declaration for qalab.
2. Add a plugin declaration into each module's pom.xml I want to run
QALab for
3. run mvn site so that my checkstyle-report.xml and pmd.xml exist
4. run mvn install to compile my code again.
It seems that if I run mvn clean install -e I get an issue with the
checkstyle-report.xml and pmd.xml files not being found. So why must I
have
these files present just to run an install?
here is my super pom.xml declaration:
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
!-- Checkstyle Merge --
executions
execution
idcheckstyle-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${basedir}/target/checkstyle-
result.xml/inputFile
/configuration
/execution
!-- findBugs Merge --
!--execution
idfindbugs-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.FindBugsStatMerge/handler
inputFile${basedir}/target/site/findbugs.xml/inputFile
/configuration
/execution--
!-- PMD Merge --
execution
idpmd-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.PMDStatMerge/handler
inputFile${basedir}/target/site/pmd.xml/inputFile
!--inputFile${project.build.directory
}/pmd/pmd.xml/inputFile--
/configuration
/execution
!-- Additional executions --
execution
idqalab-movers/id
phaseverify/phase
goals
goalmovers/goal
/goals
configuration
startTimeHoursOffset480/startTimeHoursOffset
/configuration
/execution
execution
idqalab-chart/id
phaseverify/phase
goals
goalchart/goal
/goals
configuration
summaryOnlyfalse/summaryOnly
/configuration
/execution
/executions
configuration
!--typescheckstyle,findbugs,pmd/types--
typescheckstyle,pmd/types
/configuration
/plugin
here is my comon/common-jar/pom.xml declaration:
build
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
/plugin
.
reporting
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
reportSets
reportSet
reports
reportreport/report
/reports
/reportSet
/reportSets
/plugin
.
On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote:
Is there something
Re: qalab.xml does not exist.
Another twist... Results : [surefire] Tests run: 196, Failures: 0, Errors: 0 [INFO] [site:site] [WARNING] Error loading report org.apache.maven.plugin.jxr.JxrReport - AbstractMethodError: canGenerateReport() [INFO] Generate QALab Main Report report. [INFO] Generate QALab Movers Report report. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\common\common-jar\target\qalab\qalab- movers.xml does not exis t. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.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.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) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation I moved the movers back to verify: execution idqalab-movers/id phaseverify/phase goals goalmovers/goal /goals configuration startTimeHoursOffset480/startTimeHoursOffset /configuration /execution and the files should be located at target\qalab\qalab-movers.xml but does not seem to be generated first before the verification. So when should this execution happen as I have tried pre-site and verify as the phase and they give the same error...??? On 10/16/06, Mick Knutson [EMAIL PROTECTED] wrote: That worked great. But now, there are no png images being created for the graph Any ideas why? On 10/14/06, Guillaume Tardif [EMAIL PROTECTED] wrote: To avoid any dependancy between the build phases (compile/test/verify/install) and site generation, link your qlab execution to phase pre-site instead of verify Guillaume -Message d'origine- De: Mick Knutson [mailto:[EMAIL PROTECTED] Envoyé: samedi 14 octobre 2006 01:49 À: maven Objet: Re: qalab.xml does not exist. Seems I am getting further, but still issues with QALab I have all my artifacts in sub-modules. So I find that to allow this to work correctly, I have to: 1. Create a dependancyManagement plugin declaration for qalab. 2. Add a plugin declaration into each module's pom.xml I want to run QALab for 3. run mvn site so that my checkstyle-report.xml and pmd.xml exist 4. run mvn install to compile my code again. It seems that if I run mvn clean install -e I get an issue with the checkstyle-report.xml and pmd.xml files not being found. So why must I have these files present just to run an install? here is my super pom.xml declaration: plugin groupIdnet.objectlab/groupId artifactIdmaven-qalab-plugin/artifactId version 2.1/version !-- Checkstyle Merge -- executions execution idcheckstyle-merge/id phaseverify/phase goals goalmerge/goal /goals configuration handler net.objectlab.qalab.parser.CheckstyleStatMerge/handler
RE: qalab.xml does not exist.
Hi,
This happens typically if you add QLab reports without adding qlab in your
build/plugin section, associated to phase pre-site for exemple
Note that you also need to add pmd execution there, since qlab uses the pmd xml
file.
If you have not added qlab to your build section, take a look at the following
example
Regards
Guillaume
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
executions
execution
idpmd/id
phasepre-site/phase
goals
goalpmd/goal
/goals
/execution
/executions
configuration
linkXreftrue/linkXref
targetJdk1.5/targetJdk
formatxml/format
/configuration
/plugin
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
executions
execution
idpmd-merge/id
phasepre-site/phase
goals
goalmerge/goal
/goals
configuration
handlernet.objectlab.qalab.parser.PMDStatMerge/handler
inputFile
${project.build.directory}/pmd.xml
/inputFile
/configuration
/execution
execution
idqalab-movers/id
phasepre-site/phase
goals
goalmovers/goal
/goals
configuration
startTimeHoursOffset480/startTimeHoursOffset
/configuration
/execution
execution
idqalab-chart/id
phasepre-site/phase
goals
goalchart/goal
/goals
configuration
summaryOnlyfalse/summaryOnly
/configuration
/execution
/executions
configuration
typespmd/types
/configuration
/plugin
/plugins
/build
reporting
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
configuration
linkXreftrue/linkXref
targetJdk1.5/targetJdk
formatxml/format
/configuration
/plugin
/plugins
/reporting
-Message d'origine-
De : Mick Knutson [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 13 octobre 2006 19:56
À : maven
Objet : qalab.xml does not exist.
[INFO] Generate Dependencies report.
[INFO] Generate Dependency Convergence report.
[INFO] Generate Mailing Lists report.
[INFO] Generate About report.
[INFO] Generate Project Summary report.
[INFO] Generate Project Team report.
[INFO] Generate Source Xref report.
[INFO] Generate QALab Main Report report.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report:
C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.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.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)
RE: qalab.xml does not exist.
To avoid any dependancy between the build phases (compile/test/verify/install)
and site generation, link your qlab execution to phase pre-site instead of
verify
Guillaume
-Message d'origine-
De : Mick Knutson [mailto:[EMAIL PROTECTED]
Envoyé : samedi 14 octobre 2006 01:49
À : maven
Objet : Re: qalab.xml does not exist.
Seems I am getting further, but still issues with QALab
I have all my artifacts in sub-modules. So I find that to allow this to work
correctly, I have to:
1. Create a dependancyManagement plugin declaration for qalab.
2. Add a plugin declaration into each module's pom.xml I want to run
QALab for
3. run mvn site so that my checkstyle-report.xml and pmd.xml exist
4. run mvn install to compile my code again.
It seems that if I run mvn clean install -e I get an issue with the
checkstyle-report.xml and pmd.xml files not being found. So why must I have
these files present just to run an install?
here is my super pom.xml declaration:
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
!-- Checkstyle Merge --
executions
execution
idcheckstyle-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${basedir}/target/checkstyle-
result.xml/inputFile
/configuration
/execution
!-- findBugs Merge --
!--execution
idfindbugs-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.FindBugsStatMerge/handler
inputFile${basedir}/target/site/findbugs.xml/inputFile
/configuration
/execution--
!-- PMD Merge --
execution
idpmd-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.PMDStatMerge/handler
inputFile${basedir}/target/site/pmd.xml/inputFile
!--inputFile${project.build.directory
}/pmd/pmd.xml/inputFile--
/configuration
/execution
!-- Additional executions --
execution
idqalab-movers/id
phaseverify/phase
goals
goalmovers/goal
/goals
configuration
startTimeHoursOffset480/startTimeHoursOffset
/configuration
/execution
execution
idqalab-chart/id
phaseverify/phase
goals
goalchart/goal
/goals
configuration
summaryOnlyfalse/summaryOnly
/configuration
/execution
/executions
configuration
!--typescheckstyle,findbugs,pmd/types--
typescheckstyle,pmd/types
/configuration
/plugin
here is my comon/common-jar/pom.xml declaration:
build
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
/plugin
.
reporting
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
reportSets
reportSet
reports
reportreport/report
/reports
/reportSet
/reportSets
/plugin
.
On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote:
Is there something I am missing with:
There are 3 Mojos provided for your use.
1. BuildStatMergeMojo - Handles the merge of statistics into
qalab.xml
2
Re: qalab.xml does not exist.
I'm not using QALab currently but I've seen things like this before... I'd suspect you've simply added QALab to your Reporting section without adding a corresponding section to Build/plugins. And so your QALab report is looking for the XML file (generated by the build-time plugin) but it doesn't exist, so it fails. Can someone who is using QALab please contribute their pom.xml file for Mick's reference? Wayne On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote: [INFO] Generate Dependencies report. [INFO] Generate Dependency Convergence report. [INFO] Generate Mailing Lists report. [INFO] Generate About report. [INFO] Generate Project Summary report. [INFO] Generate Project Team report. [INFO] Generate Source Xref report. [INFO] Generate QALab Main Report report. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.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.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) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml d oes not exist. at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument( ReportDocumentRenderer.java:71) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render( DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java :124) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) ... 18 more Caused by: org.apache.maven.reporting.MavenReportException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.report.MainReport.validate(MainReport.java :217) at net.objectlab.qalab.m2.report.MainReport.executeReport( MainReport.java:107) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:98) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument( ReportDocumentRenderer.java:67) ... 22 more Caused by: java.io.FileNotFoundException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.util.Utils.checkFile(Utils.java:39) at net.objectlab.qalab.m2.report.MainReport.validate(MainReport.java :214) ... 25 more [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Fri Oct 13 10:52:28 PDT 2006 [INFO] Final Memory: 22M/43M [INFO] -- Thanks DJ MICK http://www.djmick.com
Re: qalab.xml does not exist.
Is there something I am missing with: There are 3 Mojos provided for your use. 1. BuildStatMergeMojo - Handles the merge of statistics into qalab.xml 2. BuildStatChartMojo - Generates the QALab BuildStat chart 3. BuildStatMoversMojo - Creates the mover XML file given the correct parameters. The movers report shows what has changed over the last x hours. What is a Mojo and how is it called to build qalab.xml ? On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote: [INFO] Generate Dependencies report. [INFO] Generate Dependency Convergence report. [INFO] Generate Mailing Lists report. [INFO] Generate About report. [INFO] Generate Project Summary report. [INFO] Generate Project Team report. [INFO] Generate Source Xref report. [INFO] Generate QALab Main Report report. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals ( DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments ( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.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.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) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute (SiteMojo.java :97) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java :534) ... 16 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml d oes not exist. at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument ( ReportDocumentRenderer.java:71) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render( DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale( SiteMojo.java:124) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java :92) ... 18 more Caused by: org.apache.maven.reporting.MavenReportException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.report.MainReport.validate( MainReport.java:217) at net.objectlab.qalab.m2.report.MainReport.executeReport( MainReport.java:107) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:98) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument ( ReportDocumentRenderer.java:67) ... 22 more Caused by: java.io.FileNotFoundException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.util.Utils.checkFile (Utils.java:39) at net.objectlab.qalab.m2.report.MainReport.validate( MainReport.java:214) ... 25 more [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Fri Oct 13 10:52:28 PDT 2006 [INFO] Final Memory: 22M/43M [INFO]
Re: qalab.xml does not exist.
isn't faster if you ask qalab folks directly? On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote: Is there something I am missing with: There are 3 Mojos provided for your use. 1. BuildStatMergeMojo - Handles the merge of statistics into qalab.xml 2. BuildStatChartMojo - Generates the QALab BuildStat chart 3. BuildStatMoversMojo - Creates the mover XML file given the correct parameters. The movers report shows what has changed over the last x hours. What is a Mojo and how is it called to build qalab.xml ? On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote: [INFO] Generate Dependencies report. [INFO] Generate Dependency Convergence report. [INFO] Generate Mailing Lists report. [INFO] Generate About report. [INFO] Generate Project Summary report. [INFO] Generate Project Team report. [INFO] Generate Source Xref report. [INFO] Generate QALab Main Report report. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals ( DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.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.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) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute (SiteMojo.java :97) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java :534) ... 16 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml d oes not exist. at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument ( ReportDocumentRenderer.java:71) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render( DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale( SiteMojo.java:124) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java :92) ... 18 more Caused by: org.apache.maven.reporting.MavenReportException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.report.MainReport.validate( MainReport.java:217) at net.objectlab.qalab.m2.report.MainReport.executeReport( MainReport.java:107) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:98) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument ( ReportDocumentRenderer.java:67) ... 22 more Caused by: java.io.FileNotFoundException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.util.Utils.checkFile (Utils.java:39) at net.objectlab.qalab.m2.report.MainReport.validate( MainReport.java:214) ... 25 more [INFO]
Re: qalab.xml does not exist.
Seems I am getting further, but still issues with QALab
I have all my artifacts in sub-modules. So I find that to allow this to work
correctly, I have to:
1. Create a dependancyManagement plugin declaration for qalab.
2. Add a plugin declaration into each module's pom.xml I want to run
QALab for
3. run mvn site so that my checkstyle-report.xml and pmd.xml exist
4. run mvn install to compile my code again.
It seems that if I run mvn clean install -e I get an issue with the
checkstyle-report.xml and pmd.xml files not being found. So why must I have
these files present just to run an install?
here is my super pom.xml declaration:
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
!-- Checkstyle Merge --
executions
execution
idcheckstyle-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.CheckstyleStatMerge/handler
inputFile${basedir}/target/checkstyle-
result.xml/inputFile
/configuration
/execution
!-- findBugs Merge --
!--execution
idfindbugs-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.FindBugsStatMerge/handler
inputFile${basedir}/target/site/findbugs.xml/inputFile
/configuration
/execution--
!-- PMD Merge --
execution
idpmd-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handler
net.objectlab.qalab.parser.PMDStatMerge/handler
inputFile${basedir}/target/site/pmd.xml/inputFile
!--inputFile${project.build.directory
}/pmd/pmd.xml/inputFile--
/configuration
/execution
!-- Additional executions --
execution
idqalab-movers/id
phaseverify/phase
goals
goalmovers/goal
/goals
configuration
startTimeHoursOffset480/startTimeHoursOffset
/configuration
/execution
execution
idqalab-chart/id
phaseverify/phase
goals
goalchart/goal
/goals
configuration
summaryOnlyfalse/summaryOnly
/configuration
/execution
/executions
configuration
!--typescheckstyle,findbugs,pmd/types--
typescheckstyle,pmd/types
/configuration
/plugin
here is my comon/common-jar/pom.xml declaration:
build
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
/plugin
.
reporting
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
reportSets
reportSet
reports
reportreport/report
/reports
/reportSet
/reportSets
/plugin
.
On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote:
Is there something I am missing with:
There are 3 Mojos provided for your use.
1. BuildStatMergeMojo - Handles the merge of statistics into
qalab.xml
2. BuildStatChartMojo - Generates the QALab BuildStat chart
3. BuildStatMoversMojo - Creates the mover XML file given the
correct parameters. The movers report shows what has changed over the last
x hours.
What is a Mojo and how is it called to build qalab.xml ?
On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote:
[INFO] Generate Dependencies report.
[INFO] Generate Dependency Convergence report.
[INFO]
Re: qalab.xml does not exist.
Yes it would, if the question was specifically about the functionality of qlab. But my issue seems to be about how to implement qlab in Maven using multiple modules. There just seems to be some nuances with using certain plugins in a project that realies heavily on modules like mine. On 10/13/06, Dan Tran [EMAIL PROTECTED] wrote: isn't faster if you ask qalab folks directly? On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote: Is there something I am missing with: There are 3 Mojos provided for your use. 1. BuildStatMergeMojo - Handles the merge of statistics into qalab.xml 2. BuildStatChartMojo - Generates the QALab BuildStat chart 3. BuildStatMoversMojo - Creates the mover XML file given the correct parameters. The movers report shows what has changed over the last x hours. What is a Mojo and how is it called to build qalab.xml ? On 10/13/06, Mick Knutson [EMAIL PROTECTED] wrote: [INFO] Generate Dependencies report. [INFO] Generate Dependency Convergence report. [INFO] Generate Mailing Lists report. [INFO] Generate About report. [INFO] Generate Project Summary report. [INFO] Generate Project Team report. [INFO] Generate Source Xref report. [INFO] Generate QALab Main Report report. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during page generation at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals ( DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute ( DefaultLifecycleExecutor.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.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) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute ( SiteMojo.java :97) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java :534) ... 16 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml d oes not exist. at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument ( ReportDocumentRenderer.java:71) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule( DefaultSiteRenderer.java:239) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render( DefaultSiteRenderer.java:115) at org.apache.maven.plugins.site.SiteMojo.renderLocale( SiteMojo.java:124) at org.apache.maven.plugins.site.SiteMojo.execute( SiteMojo.java :92) ... 18 more Caused by: org.apache.maven.reporting.MavenReportException: C:\viewstore\npi_tactical_dev\NPI_Provider\qalab.xml does not exist. at net.objectlab.qalab.m2.report.MainReport.validate( MainReport.java:217) at net.objectlab.qalab.m2.report.MainReport.executeReport( MainReport.java:107) at org.apache.maven.reporting.AbstractMavenReport.generate( AbstractMavenReport.java:98) at
