porting-api? Where would I add the component
>>> definition
>>>> for it?
>>>>
>>>> Mauro
>>>>
>>>
-----
>>> To unsubscribe, e
er for any plug-in to use the MetricRegistry, would it
>>>> have
>>> to
>>>> be declared in the reporting-api? Where would I add the component
>>> definition
>>>> for it?
>>>>
>>>> Mauro
>>>>
>>>
Sorry for the late reply.
The default is to be a singleton, but I think it only lives as long as
it's ref count is > 0. So you probably want to set it to the true
singleton. I remember seeing someone note this recently for something
else, but I don't know if it exists in the current version of Mav
I created a new library like you suggested, and modified both the checkstyle
an pmd plugins to use it by adding the new library as a dependency. When I
run them individually everything works fine and I see their metrics being
reported, but when I try to run both in the same build, I only see the
me
It would just need to be a common dependency. reporting-api definitely
is, but you could easily create a new library for it (and that probably
makes more sense).
The component definition goes in the same JAR as the class.
- Brett
Mauro Botelho wrote:
> Brett, in order for any plug-in to use the
Brett, in order for any plug-in to use the MetricRegistry, would it have to
be declared in the reporting-api? Where would I add the component definition
for it?
Mauro
On 1/24/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> This looks good to me at first blush. Please make sure this gets
> captu
This looks good to me at first blush. Please make sure this gets
captured in the wiki.
As far as the matric registry goes, if you use a singleton component
then you will guarantee each gets the same. Is that what you needed?
/** @component */
private MetricRegistry registry;
This is going to nee
I'd like to propose a solution for this. Here's an attempt to describe
what I was able to put together, but I'd like the opinion of the
community before I get too deep :)
First of all, I'm following the approach that has been documented in the
wiki so far. The main difference is that instead o
Sorry for the delayed response. It's that time of year :)
Mauro Botelho wrote:
> Is the idea to capture detailed information for each plug in or just
> high level statistics like the old dashboard used to do?
I'd like each plugin to be able to have its own stats so they can easily
do some form of
Is the idea to capture detailed information for each plug in or just
high level statistics like the old dashboard used to do?
What I have in place today, is a simple class that has the project id
(from the pom), stat id (defined by the parser), value (I'm using Number
here to allow for flexib
Mauro Botelho wrote:
> Did anybody put any more work on this?
No, not yet. I'm thinking of spending some time on it soon.
>
> I started to look at Brett's suggestions, but could not link the names
> to the classes.
>
> Looking at some of the plugins (Surefire, checkstyle and pmd) I think
> that
:27
To: Maven Developers List
Subject: Re: [M2] Dashboard Plugin Plans
Thanks for the response I will enter my requests
for
features in Jira. If nobody has started working
on
such plugin, I may go ahead. I just wanted to
make
sure I was not duplicating
bmit
>patches as I move along?
>
>Regards,
>
>David Le Strat.
>
>--- Vincent Massol <[EMAIL PROTECTED]> wrote:
>
>
>
>>Hi David,
>>
>>
>>
>>>-Original Message-
>>>From: David Le Strat [mailto:[EMAIL
> -Original Message-
> From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
> Sent: mercredi 28 septembre 2005 17:34
> To: Maven Developers List
> Subject: RE: [M2] Dashboard Plugin Plans
>
> On Tue, 2005-09-27 at 22:07 +0200, Vincent Massol wrote:
> > Hi David
On Wed, 2005-09-28 at 17:33 +0200, Trygve Laugstøl wrote:
> On Tue, 2005-09-27 at 22:07 +0200, Vincent Massol wrote:
> > Hi David,
> >
> > I would recommend getting architectural/design help from Brett/Jason/other
> > m2 committers as I believe this dashboard thing is something that we want to
> >
On Tue, 2005-09-27 at 22:07 +0200, Vincent Massol wrote:
> Hi David,
>
> I would recommend getting architectural/design help from Brett/Jason/other
> m2 committers as I believe this dashboard thing is something that we want to
> tackle in M2.
>
> However, everyone most m2 developers are currentl
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: mardi 27 septembre 2005 22:16
> To: Maven Developers List
> Subject: RE: [M2] Dashboard Plugin Plans
>
> On Tue, 2005-09-27 at 22:07 +0200, Vincent Massol wrote:
> > Hi David,
> &
future.
Then I definitely think the wiki would be an ideal place to get this
going. Or is it already in the wiki? I didn't look :-)
> Thanks
> -Vincent
>
> > -Original Message-
> > From: David Le Strat [mailto:[EMAIL PROTECTED]
> > Sent: mardi 27 se
t; From: David Le Strat [mailto:[EMAIL PROTECTED]
> Sent: mardi 27 septembre 2005 05:53
> To: Maven Developers List
> Subject: RE: [M2] Dashboard Plugin Plans
>
> Vincent,
>
> Thanks for the diagram. I started experimenting a
> little bit. I need some time to come up with a s
o create a
"database sink".
Mauro
Vincent Massol wrote:
Hi David,
-Original Message-
From: David Le Strat [mailto:[EMAIL PROTECTED]
Sent: lundi 26 septembre 2005 04:27
To: Maven Developers List
Subject: Re: [M2] Dashboard Plugin Plans
Thanks for the response I will enter my r
> Hi David,
>
> > -Original Message-
> > From: David Le Strat [mailto:[EMAIL PROTECTED]
> > Sent: lundi 26 septembre 2005 04:27
> > To: Maven Developers List
> > Subject: Re: [M2] Dashboard Plugin Plans
> >
> > Thanks for the response I will enter my requests
Hi David,
> -Original Message-
> From: David Le Strat [mailto:[EMAIL PROTECTED]
> Sent: lundi 26 septembre 2005 04:27
> To: Maven Developers List
> Subject: Re: [M2] Dashboard Plugin Plans
>
> Thanks for the response I will enter my requests for
> features
That's nice to hear. ^_^
Btw, I think you've seen the plugin matrix wiki page... if you want to
start on the dashboard plugin, please update the wiki and put your name
as the m2 author... this way, we'll know who's working on which plugin.
Thanks.
David Le Strat wrote:
Thanks for the res
Thanks for the response I will enter my requests for
features in Jira. If nobody has started working on
such plugin, I may go ahead. I just wanted to make
sure I was not duplicating any work.
Does anyone have any strong opinion on how different
they want the design for the new plugin to be from
Hi, David.
I doubt if anyone is working on the Dashboard plugin... right now, we
are focusing on higher priority plugins towards the lesser ones. We'll
soon get there ^_^
But still, anyone can contribute and start on the Dashboard plugin, it
they want. We do appreciate volunteers. :D
I s
All,
I am not sure what the plans are for the dashboard
plugin for M2. According to the WIKI, it may need to
be significantly rewritten. Is anyone currently
working on the plugin for M2?
What are the requirements for the M2 dashboard plugin?
In addition to the what the M1 plugin provides:
- A
26 matches
Mail list logo
