-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
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
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
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
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
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
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
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
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
