You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Michael Waluk <mw...@gmail.com> on 2006/09/25 06:06:19 UTC
Clover fails during compile, but project compiles normally
Hi,
My Clover reports worked fine before I renamed some sub-modules. Now during
compilation for Clover it can't find the other sub-module that this project
depends upon. The normal compile and install works fine as the log snippet
shows, but when Clover compiles its version it can't see the dependency.
Can anyone guess why that might happen - why Clover doesn't see a dependency
but normal compile does?
Thanks for any help,
Michael
Here is where it goes bad....
[INFO] [install:install]
[INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
standalone-1.0-SNAPSHOT.jar to
C:\Documents and
Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-standalone\1.0-SNAPSHOT
\oba-standalone-1.0-SNAPSHOT.jar
[INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
standalone-1.0-SNAPSHOT-tests.j
ar to C:\Documents and
Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-standalone\1.0-SN
APSHOT\oba-standalone-1.0-SNAPSHOT-tests.jar
[INFO] Preparing clover:instrument
[WARNING] Removing: instrument from forked lifecycle, to prevent recursive
invocation.
[INFO] [clover:instrumentInternal]
Clover Version 1.3.12, built on February 08 2006
loaded from: C:\Documents and
Settings\michael.waluk\.m2\repository\com\cenqua\clover\clover\1.3.12\
clover-1.3.12.jar
Server License registered to Workscape
No coverage database
'C:\views\mw_oba_prj_lptp\oba\standalone\target/clover/clover.db' found.
Creati
ng a fresh one.
Processing files at 1.5 source level.
Instrumented 78 source files.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 78 source files to
C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\classes
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\src\com\workscape\oneforce\apps\builder\Scenar
ioFactory.java:[19,38] package com.workscape.oneforce.builder does not exist
RE: Clover fails during compile, but project compiles normally
Posted by Vincent Massol <vi...@massol.net>.
> -----Original Message-----
> From: Martin van den Bemt [mailto:mllist@mvdb.net]
> Sent: mardi 26 septembre 2006 20:43
> To: Maven Users List
> Subject: Re: Clover fails during compile, but project compiles normally
>
> Vincent Massol wrote:
> > Hi Martin,
> >
> >> -----Original Message-----
> >> From: Martin van den Bemt [mailto:mllist@mvdb.net]
> >> Sent: lundi 25 septembre 2006 20:34
> >> To: Maven Users List
> >> Subject: Re: Clover fails during compile, but project compiles normally
> >>
> >> Don't install and clover at the same time..
> >
> > I think it should work fine... Any bad experience? :-)
>
> The clover plugin is pretty solid :) Except some weird behaviour with
> instrumentation jars ending up
> in the local repository :)
> (Cobertura has this problem too I think)
If you have an issue with instrumented jars let me know and I'll have a
look. There was an issue with the plugin not using the latest of either the
non-instrumented jar or the instrumented one but I've fixed it in SVN some
time ago. Which reminds me that I should do a release soon.
Thanks
-Vincent
___________________________________________________________________________
D�couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/R�ponses pour partager vos connaissances, vos opinions et vos exp�riences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Clover fails during compile, but project compiles normally
Posted by Martin van den Bemt <ml...@mvdb.net>.
Vincent Massol wrote:
> Hi Martin,
>
>> -----Original Message-----
>> From: Martin van den Bemt [mailto:mllist@mvdb.net]
>> Sent: lundi 25 septembre 2006 20:34
>> To: Maven Users List
>> Subject: Re: Clover fails during compile, but project compiles normally
>>
>> Don't install and clover at the same time..
>
> I think it should work fine... Any bad experience? :-)
The clover plugin is pretty solid :) Except some weird behaviour with instrumentation jars ending up
in the local repository :)
(Cobertura has this problem too I think)
Mvgr,
Martin
>
> Thanks
> -Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Clover fails during compile, but project compiles normally
Posted by Vincent Massol <vi...@massol.net>.
Hi Martin,
> -----Original Message-----
> From: Martin van den Bemt [mailto:mllist@mvdb.net]
> Sent: lundi 25 septembre 2006 20:34
> To: Maven Users List
> Subject: Re: Clover fails during compile, but project compiles normally
>
> Don't install and clover at the same time..
I think it should work fine... Any bad experience? :-)
Thanks
-Vincent
> Michael Waluk wrote:
> > In case anyone searches for something similar and finds this...
> >
> > I don't understand it, but here is how I fixed this:
> >
> > In my local repository I found that next to
> > oba-standalone-1.0-SNAPSHOT.jarwas an older file
> > oba-standalone-1.0-SNAPSHOT-clover.jar. Once I deleted that it ran
> > fine. I
> > guess clover must have seen that old version and didn't create the new
> > snapshot to use as a dependency.
> >
> > Hope that helps someone out there.
> > - Michael
> >
> >
> > On 9/25/06, Michael Waluk <mw...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> My Clover reports worked fine before I renamed some sub-modules. Now
> >> during compilation for Clover it can't find the other sub-module that
> >> this
> >> project depends upon. The normal compile and install works fine as
> >> the log
> >> snippet shows, but when Clover compiles its version it can't see the
> >> dependency.
> >>
> >> Can anyone guess why that might happen - why Clover doesn't see a
> >> dependency but normal compile does?
> >>
> >> Thanks for any help,
> >> Michael
> >>
> >> Here is where it goes bad....
> >>
> >>
> >> [INFO] [install:install]
> >> [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
> >> standalone-1.0-SNAPSHOT.jar to
> >> C:\Documents and
> >> Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-
> standalone\1.0-SNAPSHOT
> >>
> >>
> >> \oba-standalone-1.0-SNAPSHOT.jar
> >> [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
> >> standalone-1.0-SNAPSHOT-tests.j
> >> ar to C:\Documents and
> >> Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-
> standalone\1.0-SN
> >>
> >>
> >> APSHOT\oba-standalone-1.0-SNAPSHOT-tests.jar
> >> [INFO] Preparing clover:instrument
> >> [WARNING] Removing: instrument from forked lifecycle, to prevent
> >> recursive
> >> invocation.
> >> [INFO] [clover:instrumentInternal]
> >> Clover Version 1.3.12, built on February 08 2006
> >> loaded from: C:\Documents and
> >> Settings\michael.waluk\.m2\repository\com\cenqua\clover\clover\1.3.12\
> >> clover-1.3.12.jar
> >> Server License registered to Workscape
> >> No coverage database
> >> 'C:\views\mw_oba_prj_lptp\oba\standalone\target/clover/clover.db'
> found.
> >> Creati
> >> ng a fresh one.
> >> Processing files at 1.5 source level.
> >> Instrumented 78 source files.
> >> [INFO] [resources:resources]
> >> [INFO] Using default encoding to copy filtered resources.
> >> [INFO] [compiler:compile]
> >> Compiling 78 source files to
> >> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\classes
> >> [INFO]
> >> -----------------------------------------------------------------------
> -
> >> [ERROR] BUILD FAILURE
> >> [INFO]
> >> -----------------------------------------------------------------------
> -
> >> [INFO] Compilation failure
> >>
> >>
> >>
> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\src\com\workscape\on
> eforce\apps\builder\Scenar
> >>
> >> ioFactory.java:[19,38] package com.workscape.oneforce.builder does not
> >> exist
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
___________________________________________________________________________
D�couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/R�ponses pour partager vos connaissances, vos opinions et vos exp�riences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Clover fails during compile, but project compiles normally
Posted by Martin van den Bemt <ml...@mvdb.net>.
Don't install and clover at the same time..
Mvgr,
Martin
Michael Waluk wrote:
> In case anyone searches for something similar and finds this...
>
> I don't understand it, but here is how I fixed this:
>
> In my local repository I found that next to
> oba-standalone-1.0-SNAPSHOT.jarwas an older file
> oba-standalone-1.0-SNAPSHOT-clover.jar. Once I deleted that it ran
> fine. I
> guess clover must have seen that old version and didn't create the new
> snapshot to use as a dependency.
>
> Hope that helps someone out there.
> - Michael
>
>
> On 9/25/06, Michael Waluk <mw...@gmail.com> wrote:
>>
>> Hi,
>>
>> My Clover reports worked fine before I renamed some sub-modules. Now
>> during compilation for Clover it can't find the other sub-module that
>> this
>> project depends upon. The normal compile and install works fine as
>> the log
>> snippet shows, but when Clover compiles its version it can't see the
>> dependency.
>>
>> Can anyone guess why that might happen - why Clover doesn't see a
>> dependency but normal compile does?
>>
>> Thanks for any help,
>> Michael
>>
>> Here is where it goes bad....
>>
>>
>> [INFO] [install:install]
>> [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
>> standalone-1.0-SNAPSHOT.jar to
>> C:\Documents and
>> Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-standalone\1.0-SNAPSHOT
>>
>>
>> \oba-standalone-1.0-SNAPSHOT.jar
>> [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
>> standalone-1.0-SNAPSHOT-tests.j
>> ar to C:\Documents and
>> Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-standalone\1.0-SN
>>
>>
>> APSHOT\oba-standalone-1.0-SNAPSHOT-tests.jar
>> [INFO] Preparing clover:instrument
>> [WARNING] Removing: instrument from forked lifecycle, to prevent
>> recursive
>> invocation.
>> [INFO] [clover:instrumentInternal]
>> Clover Version 1.3.12, built on February 08 2006
>> loaded from: C:\Documents and
>> Settings\michael.waluk\.m2\repository\com\cenqua\clover\clover\1.3.12\
>> clover-1.3.12.jar
>> Server License registered to Workscape
>> No coverage database
>> 'C:\views\mw_oba_prj_lptp\oba\standalone\target/clover/clover.db' found.
>> Creati
>> ng a fresh one.
>> Processing files at 1.5 source level.
>> Instrumented 78 source files.
>> [INFO] [resources:resources]
>> [INFO] Using default encoding to copy filtered resources.
>> [INFO] [compiler:compile]
>> Compiling 78 source files to
>> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\classes
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Compilation failure
>>
>>
>> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\src\com\workscape\oneforce\apps\builder\Scenar
>>
>> ioFactory.java:[19,38] package com.workscape.oneforce.builder does not
>> exist
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Clover fails during compile, but project compiles normally
Posted by Vincent Massol <vi...@massol.net>.
Hi Michael,
This is a known issue that I've fixed in v2.3 of the Clover plugin (see
http://jira.codehaus.org/browse/MCLOVER-51).
Thanks
-Vincent
> -----Original Message-----
> From: Michael Waluk [mailto:mwaluk@gmail.com]
> Sent: lundi 25 septembre 2006 17:36
> To: users@maven.apache.org
> Subject: Re: Clover fails during compile, but project compiles normally
>
> In case anyone searches for something similar and finds this...
>
> I don't understand it, but here is how I fixed this:
>
> In my local repository I found that next to
> oba-standalone-1.0-SNAPSHOT.jarwas an older file
> oba-standalone-1.0-SNAPSHOT-clover.jar. Once I deleted that it ran fine.
> I
> guess clover must have seen that old version and didn't create the new
> snapshot to use as a dependency.
>
> Hope that helps someone out there.
> - Michael
>
>
> On 9/25/06, Michael Waluk <mw...@gmail.com> wrote:
> >
> > Hi,
> >
> > My Clover reports worked fine before I renamed some sub-modules. Now
> > during compilation for Clover it can't find the other sub-module that
> this
> > project depends upon. The normal compile and install works fine as the
> log
> > snippet shows, but when Clover compiles its version it can't see the
> > dependency.
> >
> > Can anyone guess why that might happen - why Clover doesn't see a
> > dependency but normal compile does?
> >
> > Thanks for any help,
> > Michael
> >
> > Here is where it goes bad....
> >
> >
> > [INFO] [install:install]
> > [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
> > standalone-1.0-SNAPSHOT.jar to
> > C:\Documents and
> > Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-
> standalone\1.0-SNAPSHOT
> >
> > \oba-standalone-1.0-SNAPSHOT.jar
> > [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
> > standalone-1.0-SNAPSHOT-tests.j
> > ar to C:\Documents and
> > Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-
> standalone\1.0-SN
> >
> > APSHOT\oba-standalone-1.0-SNAPSHOT-tests.jar
> > [INFO] Preparing clover:instrument
> > [WARNING] Removing: instrument from forked lifecycle, to prevent
> recursive
> > invocation.
> > [INFO] [clover:instrumentInternal]
> > Clover Version 1.3.12, built on February 08 2006
> > loaded from: C:\Documents and
> > Settings\michael.waluk\.m2\repository\com\cenqua\clover\clover\1.3.12\
> > clover-1.3.12.jar
> > Server License registered to Workscape
> > No coverage database
> > 'C:\views\mw_oba_prj_lptp\oba\standalone\target/clover/clover.db' found.
> > Creati
> > ng a fresh one.
> > Processing files at 1.5 source level.
> > Instrumented 78 source files.
> > [INFO] [resources:resources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:compile]
> > Compiling 78 source files to
> > C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\classes
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Compilation failure
> >
> >
> >
> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\src\com\workscape\on
> eforce\apps\builder\Scenar
> > ioFactory.java:[19,38] package com.workscape.oneforce.builder does not
> > exist
> >
___________________________________________________________________________
D�couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/R�ponses pour partager vos connaissances, vos opinions et vos exp�riences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Clover fails during compile, but project compiles normally
Posted by Michael Waluk <mw...@gmail.com>.
In case anyone searches for something similar and finds this...
I don't understand it, but here is how I fixed this:
In my local repository I found that next to
oba-standalone-1.0-SNAPSHOT.jarwas an older file
oba-standalone-1.0-SNAPSHOT-clover.jar. Once I deleted that it ran fine. I
guess clover must have seen that old version and didn't create the new
snapshot to use as a dependency.
Hope that helps someone out there.
- Michael
On 9/25/06, Michael Waluk <mw...@gmail.com> wrote:
>
> Hi,
>
> My Clover reports worked fine before I renamed some sub-modules. Now
> during compilation for Clover it can't find the other sub-module that this
> project depends upon. The normal compile and install works fine as the log
> snippet shows, but when Clover compiles its version it can't see the
> dependency.
>
> Can anyone guess why that might happen - why Clover doesn't see a
> dependency but normal compile does?
>
> Thanks for any help,
> Michael
>
> Here is where it goes bad....
>
>
> [INFO] [install:install]
> [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
> standalone-1.0-SNAPSHOT.jar to
> C:\Documents and
> Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-standalone\1.0-SNAPSHOT
>
> \oba-standalone-1.0-SNAPSHOT.jar
> [INFO] Installing C:\views\mw_oba_prj_lptp\oba\standalone\target\oba-
> standalone-1.0-SNAPSHOT-tests.j
> ar to C:\Documents and
> Settings\michael.waluk\.m2\repository\com\workscape\oba\oba-standalone\1.0-SN
>
> APSHOT\oba-standalone-1.0-SNAPSHOT-tests.jar
> [INFO] Preparing clover:instrument
> [WARNING] Removing: instrument from forked lifecycle, to prevent recursive
> invocation.
> [INFO] [clover:instrumentInternal]
> Clover Version 1.3.12, built on February 08 2006
> loaded from: C:\Documents and
> Settings\michael.waluk\.m2\repository\com\cenqua\clover\clover\1.3.12\
> clover-1.3.12.jar
> Server License registered to Workscape
> No coverage database
> 'C:\views\mw_oba_prj_lptp\oba\standalone\target/clover/clover.db' found.
> Creati
> ng a fresh one.
> Processing files at 1.5 source level.
> Instrumented 78 source files.
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> Compiling 78 source files to
> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\classes
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
>
>
> C:\views\mw_oba_prj_lptp\oba\standalone\target\clover\src\com\workscape\oneforce\apps\builder\Scenar
> ioFactory.java:[19,38] package com.workscape.oneforce.builder does not
> exist
>