PMD includes and excludes in maven2
Hi All, I'm running PMD and I created several reports on different java packages. I used the section of the PMD configuration and it works fine ; however, the corresponding section doesn't seem to have any impact on the PMD execution. Is it something that still needs to be implemented in the maven2 plugin? Here is my PMD config : target/impl/site target/impl **/*Impl.java Thanks Guillaume - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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:
net.objectlab
maven-qalab-plugin
2.1
checkstyle-merge
verify
merge
net.objectlab.qalab.parser.CheckstyleStatMerge
${basedir}/target/checkstyle-
result.xml
pmd-merge
verify
merge
net.objectlab.qalab.parser.PMDStatMerge
${basedir}/target/site/pmd.xml
qalab-movers
verify
movers
480
qalab-chart
verify
chart
false
checkstyle,pmd
here is my comon/common-jar/pom.xml declaration:
net.objectlab
maven-qalab-plugin
.
net.objectlab
maven-qalab-plugin
2.1
report
.
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.DefaultLifecycl
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
>
>
>
> org.apache.maven.plugins
> maven-pmd-plugin
>
>
> pmd
> pre-site
>
> pmd
>
>
>
>
> true
> 1.5
> xml
>
>
>
> net.objectlab
> maven-qalab-plugin
> 2.1
>
>
> pmd-merge
> pre-site
>
> merge
>
>
> net.objectlab.qalab.parser.PMDStatMerge
>
> ${project.build.directory}/pmd.xml
>
>
>
>
> qalab-movers
> pre-site
>
> movers
>
>
> 480
>
>
>
> qalab-chart
> pre-site
>
> chart
>
>
> false
>
>
>
>
> pmd
>
>
>
>
>
>
>
> net.objectlab
> maven-qalab-plugin
> 2.1
>
>
> org.apache.maven.plugins
> maven-pmd-plugin
>
> true
> 1.5
> xml
>
>
>
>
-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)
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(
Re: Progress indicators for project management
Hi All, I'm also trying to put in place QLab (Great! BTW), I got it running with PMD (pretty much the same configuration as below). It generates the movers-report without any issue. However, during the execution of the "chart" goal, I see exceptions in the maven traces : [INFO] java.io.FileNotFoundException: D:\...\petStoreCommon\target\site\qalab\summary.png (Le chemin d'accÞs spÚcifiÚ est introuvable) Same errors for each file after the generation of the summary chart. Directory target/sote/qalab exists on my machine. It only contains all-packages, index, movers and overview-summary.html. Any idea? Has anyone encountered something similar? Thanks in advance Guillaume Tardif Christophe Deneux Mon, 25 Sep 2006 00:26:31 -0700 Hi all, I have quickly try maven-qalab-plugin this weekend and I have notice the following remarks/issues: - Unable to run maven-qalab-plugin with Findbugs (No XML report is generated by Findbugs) - I had the PMD, Checkstyle, ... configured in the section to have these report in the generated website. To have the QALab reports, I must duplicate the PMD, Checkstyle, ... configuration in the section - AS report by Donnchadh, the history is stored in an XML file. Is it not possible to have a maven-qalab-plugin as a report plugin, that: - parse existing XML files generated by Checkstyle, PMD, ... (each of them declared in the section as usually used) - merge statistics in a database through JDBC - generated graphs. Thanks, Christophe DENEUX -- Initial Header --- >From : "Benoit Xhenseval" [EMAIL PROTECTED] To : [EMAIL PROTECTED],"Maven Users List" users@maven.apache.org Cc : Date : Fri, 22 Sep 2006 05:44:03 -0700 (PDT) Subject : Re: Progress indicators for project management > Hi Donnchadh, > > First of all, thanks for trying the QALab plugin, he hope you'll find it > useful. > > The Maven2 plugin is really more of a beta and I am pleased that we are > resuming development on it shortly, your comments will be taken into account. I have launched QALab but was not involved in the Maven2 plugin. I have found Maven2 more complicated than expected when I looked at the way it does reports... i.e. no XML/XSL and using java to write some reports... > > You are right in saying that you question about "inherting" a pom setting is > more of a Maven2 question and I shall let the specialists answer you. > > The idea of qalab storing the data in an xml was to reduce the dependencies, > this XML can be put in different place; this is something that maven1 and ant users can do easily, we will ensure that it is the case for m2. > One should note that it is possible to define your own "exporter" and > therefore could decide to store the data in say a database for instance. If there is a demand, we may even provide a reference implementation for that? > > So, in summary: hang in there, give us a few weeks or so to sort it out and > we will release QALab v1.0 with a fully defined maven2 plugin. > > Best regards > > Benoit > - Original Message > From: Donnchadh Ó Donnabháin <[EMAIL PROTECTED]> > To: Maven Users List > Cc: [EMAIL PROTECTED] > Sent: Thursday, September 21, 2006 6:12:05 PM > Subject: Re: Progress indicators for project management > > I tried it quicly and came across a few issues (most of which are > easily dealt with). > > I took the example configuration on the maven2 QALab plugin page > ( http://qalab.sourceforge.net/maven2/faq.html > <http://qalab.sourceforge.net/maven2/faq.html> ) > and simplified it to just working with PMD. I came across the following > issues: > * By default PMD doesn't seem to produce an XML report > * When the PMD plugin is instructed to produce an XML report it puts > it in target and the QALab example QALab expects it to be in > target/pmd. > * By Default, the PMD plugin seems to run in the report phase and the > example runs in the verify phase > > I got it working in the end with the following configuration > > > > > org.apache.maven.plugins > maven-pmd-plugin > > > pmd > verify > > pmd > > > > > true > 1.5 > xml > > > > net.objectlab > maven-qalab-plugin > 2.1 > > > pmd-merge > verify > > merge > >
