Hi Vincent,
The architecture is quite clear now, but there remains some questions:
- I understand that when calling clover:instrument in any phase, this
triggers a custom lifecycle (clover LC) that runs instrumentInternal
and then runs the tests so that clover DB gets populated. This
lifecycle
-Original Message-
From: Arnaud Bailly [mailto:[EMAIL PROTECTED]
Sent: mardi 7 novembre 2006 09:04
To: Maven Users List
Subject: Re: We need some explanation ...
Hi Vincent,
The architecture is quite clear now, but there remains some questions:
- I understand that when calling
Thanks for the (quick :-)) answer.
I agree that generated sources are usually
tested and do not need specific tests, so instrumenting them may not
be very useful as far as branch/line coverage is concerned. I can
think however of a use case where you would need coverage of generated
code.
-Original Message-
From: Arnaud Bailly [mailto:[EMAIL PROTECTED]
Sent: mardi 7 novembre 2006 11:03
To: Maven Users List
Subject: Re: We need some explanation ...
Thanks for the (quick :-)) answer.
I agree that generated sources are usually
tested and do not need specific
Vincent Massol [EMAIL PROTECTED] writes:
As I said I agree that there are valid use cases. Do you need this feature
for your build? If so, please create a jira issue on the Clover plugin. You
could also provide a patch if you need it. It should be quite easy I think:
we'll need to create 2
Good day to you, Arnaud,
Ah, yes :-) Thank you for that example :-) the maven-clover-plugin's (see
[1]) instrumentInternal goal is bound to the process-sources phase. Not sure
though how it works :-)
[1] http://maven.apache.org/plugins/maven-clover-plugin/
Arnaud Bailly-3 wrote:
franz see
franz see [EMAIL PROTECTED] writes:
Good day to you, Arnaud,
Ah, yes :-) Thank you for that example :-) the maven-clover-plugin's (see
[1]) instrumentInternal goal is bound to the process-sources phase. Not sure
though how it works :-)
Good day to you too,
Unfortunately, the example is
Good day to you, Arnaud,
Thanks for the correction :-) my eyes must be playing tricks on me :-P
hehehe :-D
Anyway, I'm not sure though if another goal would be bound to the same phase
as instrumentInternal. Though I haven't really disected the code to its very
core, the architecture provided in
franz see [EMAIL PROTECTED] writes:
Anyway, I'm not sure though if another goal would be bound to the same phase
as instrumentInternal. Though I haven't really disected the code to its very
core, the architecture provided in [1] seems to indicate that it is forked
to its own lifecycle (clover
and republish them.
Thanks
-Vincent
-Original Message-
From: Arnaud Bailly [mailto:[EMAIL PROTECTED]
Sent: lundi 6 novembre 2006 10:36
To: Maven Users List
Subject: Re: We need some explanation ...
franz see [EMAIL PROTECTED] writes:
Anyway, I'm not sure though if another goal would
Franz:
Yes, recipes or prescriptions for doing various types of projects.
David
On 11/5/06, franz see [EMAIL PROTECTED] wrote:
Good day to you, David,
Hhmmm...I'm not sure I understand your message. What do you mean by
neutral
to maven or any specific plugin ?
Regading the more specific
]
Sent: lundi 6 novembre 2006 10:36
To: Maven Users List
Subject: Re: We need some explanation ...
franz see [EMAIL PROTECTED] writes:
Anyway, I'm not sure though if another goal would be bound to the
same phase
as instrumentInternal. Though I haven't really disected the code to
its very
Vincent Massol [EMAIL PROTECTED] writes:
Hi Arnaud,
Hi Vincent,
Thanks a lot for this information. I will devote some time to
understand it :-) I have in my work queue a new coverage tool
implementation and this my give some insight into issues for these
matters.
Regards,
--
OQube
Good day to you, David,
The generate-sources, phase is used for auto code generation. An example for
this would be the maven-modello-plugin (see [1]) which allows the creation
of Xpp3 Readers, Writers and the corresponding models. Running an XDoclet
maven goal would most probably be bound here
Franz:
This is excellent discussion. This was what I was looking for. I had seen
the intro to the lifecycle link before but that seems out there somewhat for
most folks. I'm looking to put together more documentation that is neutral
to maven or any specific plugin and try to focus on e.g.
Good day to you, David,
Hhmmm...I'm not sure I understand your message. What do you mean by neutral
to maven or any specific plugin ?
Regading the more specific builds, im guessing you want to create a
cookbook. If so, then you can may want to contribute your recipes in the
wiki (see [1]) or
franz see [EMAIL PROTECTED] writes:
Good day to you, David,
The generate-sources, phase is used for auto code generation. An example for
this would be the maven-modello-plugin (see [1]) which allows the creation
of Xpp3 Readers, Writers and the corresponding models. Running an XDoclet
maven
17 matches
Mail list logo
