"John Allen" <[EMAIL PROTECTED]> writes:
> database accessible via Wagon. Someone mentioned something about using RDP
> about 6 months ago...
>
Hello,
I was the one who talked about this 6 months ago :-)
I am still interested in it, and willing to share my ideas and part of
my workforce. One re
o
do so one needs this kind of system.
John
-Original Message-
From: Fabrice Bellingard [mailto:[EMAIL PROTECTED]
Sent: 31 January 2007 17:06
To: Maven Developers List
Subject: Re: [PROPOSAL] Standard Reporting
Joakim is definitely right: the dashboard plugin would only be one consumer.
What'
Hi Joakim,
2007/1/31, Joakim Erdfelt <[EMAIL PROTECTED]>:
The dashboard plugin is definitely within the scope of this proposal,
but is still just 1 consumer of the datapoint data. The dashboard
plugin would be definitely be affected dramatically by this concept, it
would no longer need to know
Or in the Maven sandbox, that'd be a more appropriate place :-)
(I'm only talking about the "standardized report" framework that Joakim
introduced, of course)
On 1/31/07, Garvin LeClaire <[EMAIL PROTECTED]> wrote:
Let me fix my over zealeous typing ;-o)
Why don't we put the code in the Plugin
Let me fix my over zealeous typing ;-o)
Why don't we put the code in the Plugin sandbox at Codehaus?
This will give us and others time to "test drive" it and move on from
there.
I think I need to use the dashboard plugin a little more before we do
merging.
I could get some of my current users to
Why don't we put the code in the Plugin sandbox at Codehaus?
This will give us and other to "test drive" it and move on from there.
I think i need to use the dashboard plugin a little more before we do
merging.
I could get some of my current users to give feedback.
--
Regards,
Garvin LeClaire
Joakim is definitely right: the dashboard plugin would only be one consumer.
What's more, Maven can generate only static pages while the application I'm
talking about is a dynamical web application, with far more possibilities
than just generated web pages.
As for creating a new maven top level p
The dashboard plugin is definitely within the scope of this proposal,
but is still just 1 consumer of the datapoint data. The dashboard
plugin would be definitely be affected dramatically by this concept, it
would no longer need to know what the other reports are, how they are
formatted, etc.
Sho
ossible.
>> > The needs of JDepend is different than PMD or even Cobertura. Heck, a
>> > standard report format might just be a pipe dream, but the rest of the
>> > datapoint proposal should still have merit.
>> >
>> > If this is a good idea, I think we should encourage the appropriate
>>
Hi guys,
it seems that this proposal arrives right on time! :-) I've just been hired
by a company that has developed, for its own needs, an application that can
store code metrics, consolidate them and show them in various ways. I
haven't had the time to look more into it yet, but it looks very p
Joakim,
I think that is a good idea. I have thought about this also when I was
working on the Findbugs plug-in.
I think this would faciliate a more effective way to do dashboard type
reports. I was thinking about developing a Doxia JDBCWriter for Plugins to
use. I would like to have the ability
There are many reports and plugins now that generate reports against the
code.
I'd like to see an entire framework built around the concept of
Standardized Reporting.
The components of this framework...
maven-reporting-datapoint
This would provide an API that various reporting plugins (checks
12 matches
Mail list logo
