You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Hilbert Schraal <w....@kpn.com> on 2004/10/28 10:15:19 UTC
JCoverage plugin troubles
All,
I'm not able to get the JCoverage maven plugin working. All reports I'm
generating give 0% coverage (while I have unit tests). I've fiddled
around with the properties, but none of the setting I made actually
worked.
You can reproduce this problem by checking out my project from
sourceforge:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/toolforge login
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/toolforge co
toolforge
Then go to the toolforge-core module, e.g. Run 'maven jcoverage' and
hopefully you'll have the same problem as I do. ;)
I'm using Maven 1.0 and JCoverage plugin v1.0.8, which are the latest
versions as far as I know.
Can you give me any clues about what I'm doing wrong here?
Thanks.
Kind regards,
Hilbert
--
Drs. Hilbert Schraal
Contrado Technologies B.V.
Telefoon: 06 53814582
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: JCoverage plugin troubles
Posted by Brett Porter <br...@gmail.com>.
You need to put sources and tests in different directories for
jcoverage to work.
http://marc.theaimsgroup.com/?l=turbine-maven-user&m=109747344304878&w=2
A little archive searching goes a long way.
Hilbert, a few items of netiquette to note for the future:
- don't contact the developers directly when there is a list to contact
- sign up to the list, don't just post. I moderated this message through.
- research before asking (I just went to the mail archive and search
for jcoverage and found the answer immediately)
Thanks,
Brett
On Thu, 28 Oct 2004 10:15:19 +0200, Hilbert Schraal
<w....@kpn.com> wrote:
> All,
>
> I'm not able to get the JCoverage maven plugin working. All reports I'm
> generating give 0% coverage (while I have unit tests). I've fiddled
> around with the properties, but none of the setting I made actually
> worked.
>
> You can reproduce this problem by checking out my project from
> sourceforge:
>
> cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/toolforge login
> cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/toolforge co
> toolforge
>
> Then go to the toolforge-core module, e.g. Run 'maven jcoverage' and
> hopefully you'll have the same problem as I do. ;)
>
> I'm using Maven 1.0 and JCoverage plugin v1.0.8, which are the latest
> versions as far as I know.
>
> Can you give me any clues about what I'm doing wrong here?
>
> Thanks.
> Kind regards,
> Hilbert
> --
> Drs. Hilbert Schraal
>
> Contrado Technologies B.V.
> Telefoon: 06 53814582
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: I am surprised that no one replied to the question I posted
yesterday!!
Posted by Sachin Bansal <sb...@adobe.com>.
Hi Serge,
Thanks for the post. I already apologized for the impatience.
Sachin
-----Original Message-----
From: Serge Huber [mailto:shuber2@jahia.com]
Sent: Thursday, October 28, 2004 9:09 AM
To: Maven Users List
Subject: Re: I am surprised that no one replied to the question I posted
yesterday!!
This is not a commercial support mailing list. No guarantees are given
as to response times, nor are any guarantees given to an actual
response. People that post in this mailing list do so mostly out of good
will.
Regards,
Serge Huber.
Sachin Bansal wrote:
>Guys,
>
> I posted this message yesterday and I have not heard from anyone. Does
that
>mean Maven DOES NOT have any solution to my *simple* problem?
>
>I have the following structure (my project is creating an eclipse plugin
for
>xml editor) :
>
>myProject
> com.abc.def.A
> com.abc.def.B
> com.abc.def.C
> com.abc.def.D
> com.abc.def.E
> com.abc.def.F
>
>There are interdependencies among the projects.
>They all produce jar files.
>
>A depends on B, C and D
>B depends on E
>
>consequently I would to first build E, then B, C and D. Finally I would
like
>Maven to build A
>
>
>The depenedency as declared in the project file of project A is as
>
> <dependency>
> <groupId>myProject</groupId>
> <artifactId>com.abc.def.B</artifactId>
> <version>1.0</version>
> </dependency>
>
> <dependency>
> <groupId>myProject</groupId>
> <artifactId>com.abc.def.C</artifactId>
> <version>1.0</version>
> </dependency>
>
> <dependency>
> <groupId>myProject</groupId>
> <artifactId>com.abc.def.D</artifactId>
> <version>1.0</version>
> </dependency>
>
>
>I DO NOT want maven to search for the com.abc.def.C-1.0.jar or
>com.abc.def.B-1.0.jar in the maven repository in order to build
>com.abc.def.A-1.0.jar.
>
>I want maven to first build project E, then B and then build project C, D
>and finally A.
>I want maven to figure this out dynamically, figuring it out from
dependency
>File that it should first build project B and for that it will have to
first
>build project E(just as Ant does, using depends target, or the sequence of
>execution)
>
>Adam Fisk suggested that calling multiproject:install does it
automatically,
>but it does not work. Everytime it looks for the *.B-1.0.jar or *.C-1.0.jar
>to be there in my repository and complains when it does not find those jar
>files.
>
>Please help.
>
>Sachin
>
>svbansal@yahoo.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: I am surprised that no one replied to the question I posted yesterday!!
Posted by Serge Huber <sh...@jahia.com>.
This is not a commercial support mailing list. No guarantees are given
as to response times, nor are any guarantees given to an actual
response. People that post in this mailing list do so mostly out of good
will.
Regards,
Serge Huber.
Sachin Bansal wrote:
>Guys,
>
> I posted this message yesterday and I have not heard from anyone. Does that
>mean Maven DOES NOT have any solution to my *simple* problem?
>
>I have the following structure (my project is creating an eclipse plugin for
>xml editor) :
>
>myProject
> com.abc.def.A
> com.abc.def.B
> com.abc.def.C
> com.abc.def.D
> com.abc.def.E
> com.abc.def.F
>
>There are interdependencies among the projects.
>They all produce jar files.
>
>A depends on B, C and D
>B depends on E
>
>consequently I would to first build E, then B, C and D. Finally I would like
>Maven to build A
>
>
>The depenedency as declared in the project file of project A is as
>
> <dependency>
> <groupId>myProject</groupId>
> <artifactId>com.abc.def.B</artifactId>
> <version>1.0</version>
> </dependency>
>
> <dependency>
> <groupId>myProject</groupId>
> <artifactId>com.abc.def.C</artifactId>
> <version>1.0</version>
> </dependency>
>
> <dependency>
> <groupId>myProject</groupId>
> <artifactId>com.abc.def.D</artifactId>
> <version>1.0</version>
> </dependency>
>
>
>I DO NOT want maven to search for the com.abc.def.C-1.0.jar or
>com.abc.def.B-1.0.jar in the maven repository in order to build
>com.abc.def.A-1.0.jar.
>
>I want maven to first build project E, then B and then build project C, D
>and finally A.
>I want maven to figure this out dynamically, figuring it out from dependency
>File that it should first build project B and for that it will have to first
>build project E(just as Ant does, using depends target, or the sequence of
>execution)
>
>Adam Fisk suggested that calling multiproject:install does it automatically,
>but it does not work. Everytime it looks for the *.B-1.0.jar or *.C-1.0.jar
>to be there in my repository and complains when it does not find those jar
>files.
>
>Please help.
>
>Sachin
>
>svbansal@yahoo.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
I am surprised that no one replied to the question I posted yesterday!!
Posted by Sachin Bansal <sb...@adobe.com>.
Guys,
I posted this message yesterday and I have not heard from anyone. Does that
mean Maven DOES NOT have any solution to my *simple* problem?
I have the following structure (my project is creating an eclipse plugin for
xml editor) :
myProject
com.abc.def.A
com.abc.def.B
com.abc.def.C
com.abc.def.D
com.abc.def.E
com.abc.def.F
There are interdependencies among the projects.
They all produce jar files.
A depends on B, C and D
B depends on E
consequently I would to first build E, then B, C and D. Finally I would like
Maven to build A
The depenedency as declared in the project file of project A is as
<dependency>
<groupId>myProject</groupId>
<artifactId>com.abc.def.B</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>myProject</groupId>
<artifactId>com.abc.def.C</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>myProject</groupId>
<artifactId>com.abc.def.D</artifactId>
<version>1.0</version>
</dependency>
I DO NOT want maven to search for the com.abc.def.C-1.0.jar or
com.abc.def.B-1.0.jar in the maven repository in order to build
com.abc.def.A-1.0.jar.
I want maven to first build project E, then B and then build project C, D
and finally A.
I want maven to figure this out dynamically, figuring it out from dependency
File that it should first build project B and for that it will have to first
build project E(just as Ant does, using depends target, or the sequence of
execution)
Adam Fisk suggested that calling multiproject:install does it automatically,
but it does not work. Everytime it looks for the *.B-1.0.jar or *.C-1.0.jar
to be there in my repository and complains when it does not find those jar
files.
Please help.
Sachin
svbansal@yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org