Within Eclipse, you can select a Java source file, select 'References ->
Project' and get a list of all of the other classes within your project
that reference that class (which would, obviously include the covering test
case).  I don't know, but I would assume, that similiar calibre IDE's
(e.g., NetBeans, IDEA, etc) would offer similiar functionality.  There are
a number of Maven plugins that offer finer grained coverage reports
including JCoverage[1], Clover[2] and Cobertura[3].

Con #2 is left as an exercise for the reader :)


Ian

[1] http://svn.mojo.codehaus.org/trunk/mojo/jcoverage-maven-plugin/
[2] http://maven.apache.org/plugins/maven-clover-plugin/
[3] http://mojo.codehaus.org/cobertura-maven-plugin/

It's better to be hated for who you are
than loved for who you are not

Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078


                                                                                
                                                       
                      Thorsten Heit                                             
                                                       
                      <[EMAIL PROTECTED]        To:       Maven Users List 
<[email protected]>                                     
                      ramind.com>              cc:                              
                                                       
                                               Subject:  Re: Maven directory 
structure                                                 
                      03/22/2006 07:42                                          
                                                       
                      AM                                                        
                                                       
                      Please respond to                                         
                                                       
                      "Maven Users                                              
                                                       
                      List"                                                     
                                                       
                                                                                
                                                       




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

> My project which is build in ant does'nt use maven standard directory
> structure
>
> src/main/java--------   java source files
> src/test/java ---------   java test files
>
> Now i want to migrate to maven
>
> Which way of directory structure is bettter?????

In our company we're actually also thinking about migrating from Ant to
Maven and have exactly the same problem. Personally I prefer Maven's
standard layout.

Pro:
* Allows to distinguish between normal sources and test classes
* Maven doesn't pack test classes into a release

Con:
* For (extremely) large source trees it can be difficult to see whether
there's a test for a certain component in the source tree.
* You have to convince your developers that they adopt that scheme ;-)


Regards

Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFEIUYcQvObkgCcDe0RAjXIAKCFUx1a3Bmj7kpn7rXU7rRlF0BniQCfUZ4i
9aSexS+oN7wHN2U/kvCIbiQ=
=A/WJ
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
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]

Reply via email to