If it's a matter of sharing information maybe the ability to store data in a
sort of temporary HashMap sort of session? Ie clover could do something
like:
session.store("CLOVER_INSTRUMENTED_SOURCE_DIR",
"target/src/clover-generated");
And the next guy that needs it could pick it up...Probably not easy to do
though since it's likely that mvn will be invoked multiple times.
On 7/11/06, John Allen <[EMAIL PROTECTED]> wrote:
I have found this aspect of clover a great frustration and would welcome
any
attempt to separate such 'instrument and compile' tasks from the main
project build activities.
John
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 11 July 2006 06:20
To: Maven Developers List
Subject: Re: General issue with clover plugin requiring creative
thinking...
On 11/07/2006 3:14 PM, Vincent Massol wrote:
> One solution would be to create a profile for the main lifecycle and
another
> one for the clover lifecycle but that's not very handy for end users I
> think. I'll try experimenting with this later on but I think it would
only
> be a hack and not a proper solution. Is there anything better I could
do?
Not that I can think of that doesn't involve core changes (ie, 2.1).
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
