To: 'Maven Developers List'
Subject: [Design issue] How can the clover plugin play nicely with plugins
doing source checks?
Hi,
I'm still struggling with this. As a reminder this is what happens:
* clover:instrument spawns a custom lifecycle which executes a maven build
ti
Ping. Any idea on this? I'd love to be able to fix this big issue...
Thanks
-Vincent
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: lundi 24 juillet 2006 12:04
> To: 'Maven Developers List'
> Subject: [Design issue] How can
Hi,
I'm still struggling with this. As a reminder this is what happens:
* clover:instrument spawns a custom lifecycle which executes a maven build
till the install phase. The clover:instrumentInternal goal is called by this
custom lifecycle to instrument sources and to redirect maven's configurat
On Sun, 14 May 2006, Jason van Zyl wrote:
>
> On 12 May 06, at 11:02 AM 12 May 06, Kenney Westerhof wrote:
>
> >
> > Hi,
> >
> > (none of this is committed)
> >
> > Jerome and I have added support for an 'implementation' parameter
> > to the @parameter tag, so that you can use interfaces as field-
On 12 May 06, at 11:02 AM 12 May 06, Kenney Westerhof wrote:
Hi,
(none of this is committed)
Jerome and I have added support for an 'implementation' parameter
to the @parameter tag, so that you can use interfaces as field-types.
So this will essentially work in the same way that component
Hi,
(none of this is committed)
Jerome and I have added support for an 'implementation' parameter
to the @parameter tag, so that you can use interfaces as field-types.
The plugin descriptors now have an extra tag next to
(which is currently unused, btw).
There's just a little problem in merg
As per my comment here:
http://jira.codehaus.org/browse/MNG-366#action_40689
This is what I think needs to be changed WRT the reporting to get them
properly configured and consistent with the build plugins. Please let me
know if you disagree or have any questions.
- if in the configuration a
