I'd actually go with (1), creating a branch for bugfixes on the old
one. (3) sounds good if there is expected to be a lot of changes
still needed for clover1.
On 29/11/2006, at 7:49 AM, Vincent Massol wrote:
Hi,
As you may have seen Clover2 is going to be out soon and I was
thinking
about how we would go about adding support for it. We already have
a Clover1
plugin. Although this is about Clover it's really a general
strategy that we
may want to have for all other tools.
I can see the following options:
* option 1: make the next version of the clover plugin use clover2. In
essence this means we won't support anymore clover1.
* option 2: add a flag to choose the clover version to use in the
plugin.
Possible but too messy I think.
* option 3: create a maven-clover2-plugin plugin for clover2.
Issue: need to
sort out duplicated code by creating a third module for common code.
WDYT? Are there other options?
Thanks
-Vincent
______________________________________________________________________
_____
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
questions !
Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
---------------------------------------------------------------------
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]
