Re: Cobertura plugin doesn't generate XML

2008-09-29 Thread Nick Stolwijk
I can think of two things, that could go wrong:

1. Did you configure this under the reporting section or under the
build section of your pom file? It should be under the build section
afaik.

2. Otherwise, what version of the cobertura plugin are you using?

Hth,

Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl



On Mon, Sep 29, 2008 at 12:04 PM, Lewis, Eric [EMAIL PROTECTED] wrote:
 Hi

 I'm trying to generate an XML report using the Cobertura plugin (2.2
 apparently). I configured the plugin according to the documentation:

 plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdcobertura-maven-plugin/artifactId
  configuration
formats
  formatxml/format
/formats
  /configuration
 /plugin

 Then I start Maven (mvn clean install cobertura:cobertura), but the
 plugin generates the HTML reports under .../target/site/cobertura/
 (which I tell it not to do), but doesn't create any XML files.

 What am I doing wrong?

 Best regards,
 Eric

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



RE: Cobertura plugin doesn't generate XML

2008-09-29 Thread mac-systems
Hello,

may you can try the configuration in your reporting section 
of the POM.

- jens

Hi

I'm trying to generate an XML report using the Cobertura plugin (2.2
apparently). I configured the plugin according to the documentation:

plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdcobertura-maven-plugin/artifactId
  configuration
formats
  formatxml/format
/formats
  /configuration
/plugin

Then I start Maven (mvn clean install cobertura:cobertura), but the
plugin generates the HTML reports under .../target/site/cobertura/
(which I tell it not to do), but doesn't create any XML files.

What am I doing wrong?

Best regards,
Eric

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Cobertura plugin

2008-01-10 Thread Stephen Connolly
Danger! Will Robinson! Danger!

How will you know that instrumenting your tests is not causing them to pass?

Seriously, we had hand tweaked the pom to run the tests only once when they
were instrumented, and as the instrumentation was forcing synchronisation
(in order to track code path execution) it was eliminating a major
concurrency bug that our unit tests were trying to prove was not there...

IMHO, you _want_ to run the tests twice.

-Stephen

On Jan 10, 2008 12:26 PM, globulon [EMAIL PROTECTED] wrote:


 Houdy,

 I am newby to Maven 2.

 I have Introduced the Cobertura plugin in the reporting section of the
 pom.xml file of my main project as follows:

 reporting
 ...
plugins

!--
   - JUNIT test report activation
--
plugin
groupIdorg.apache.maven.plugins/groupId

  artifactIdmaven-surefire-report-plugin/artifactId
/plugin
!--
   - Cobertura Code coverage module
   --
plugin
groupIdorg.codehaus.mojo/groupId

  artifactIdcobertura-maven-plugin/artifactId
configuration
formats
formathtml/format
/formats
   instrumentation/
   check
   !-- should not stop in
 case of Cobertura reporting error --

 haltOnFailurefalse/haltOnFailure
   /check
/configuration
/plugin
/plugins
 ...
 /reporting

 It works fine. As I am also using the surefire reporting, it seems the
 test
 phase is run twice, one by
 surefire and once by cobertura.

 Is there any way to instrument code before surefire execution for the two
 plugin to share the same test sequence ?

 Thanx for your response ?
 --
 View this message in context:
 http://www.nabble.com/Cobertura-plugin-tp14731193s177p14731193.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: Cobertura plugin using version 1.7

2006-07-05 Thread tulasi

HI,

when i am mvn test for mvn site, getting Error. Here I have enclosed my
configuration and error.

  plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
  configuration
   
instrumentedDirectorytarget/cobertura/instrumented-classes/instrumentedDirectory
  outputDirectorytarget/cobertura/report/outputDirectory
  /configuration
executions
execution
  idinstrument/id
phasetest-compile/phase
goals
  goalinstrument/goal
/goals
  /execution
execution
goals
  goalclean/goal
/goals
/execution
  /executions
  /plugin


reporting
-
plugins
plugin
groupIdorg.codehaus.mojo/groupId
   
artifactIdsurefire-report-maven-plugin/artifactId
/plugin
 /plugins
 /reporting

Error


Compiling 24 source files to E:\latest-i401k\cs-cache\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [cobertura:instrument {execution: instrument}]
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Unable to prepare instrumentation directory.

Embedded error: Failed to copy full contents from
E:\latest-i401k\cs-cache\classes\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\citistreet\id\util\cache\CreateCacheObjectEvent$CreateType.class
to
E:\latest-i401k\cs-cache\classes\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\generated-classes\cobertura\citistreet\id\util\cache\CreateCacheObjectEvent$CreateType.class
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 7 seconds
[INFO] Finished at: Tue Jul 04 19:28:19 GMT+05:30 2006
[INFO] Final Memory: 5M/12M
[INFO]


I dont why its creates multiple folders in classes directory.

Please help me on this issue. 
-- 
View this message in context: 
http://www.nabble.com/Cobertura-plugin-using-version-1.7-tf1889535.html#a5178718
Sent from the Maven - Users forum at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Cobertura plugin using version 1.7

2006-07-05 Thread leahpar

hello,
I don't get the instrument goal but please find below a simple example
working here ... it's all help i can give.
cordialement


build
plugins
plugin

groupIdorg.codehaus.mojo/groupId

artifactIdcobertura-maven-plugin/artifactId
executions
execution
goals

goalclean/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
plugins
plugin

groupIdorg.codehaus.mojo/groupId

artifactIdcobertura-maven-plugin/artifactId
/plugin
-- 
View this message in context: 
http://www.nabble.com/Cobertura-plugin-using-version-1.7-tf1889535.html#a5182548
Sent from the Maven - Users forum at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Cobertura plugin using version 1.7

2006-07-05 Thread Janhavi Phirke

Hi,

Following is the simple example which is working at my end. Try it...

 build
   plugins
 plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
configuration
  check branchrate=80 linerate=70 haltonerror=true
totalbranchrate=80 totallinerate=70
 /check
   /configuration
   executions
 execution
   goals
   goalinstrument/goal
   goalclean/goal
   goalcheck/goal
  /goals
/execution
   /executions
 /plugin
   /plugins
 /build

 reporting
 plugins
 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdcobertura-maven-plugin/artifactId
 /plugin
 /plugins
 /reporting






On 7/5/06, leahpar [EMAIL PROTECTED] wrote:



hello,
I don't get the instrument goal but please find below a simple example
working here ... it's all help i can give.
cordialement


   build
   plugins
   plugin
   groupIdorg.codehaus.mojo
/groupId

artifactIdcobertura-maven-plugin/artifactId
   executions
   execution
   goals

goalclean/goal
   /goals
   /execution
   /executions
   /plugin
   /plugins
   /build
   reporting
   plugins
   plugin
   groupIdorg.codehaus.mojo
/groupId

artifactIdcobertura-maven-plugin/artifactId
   /plugin
--
View this message in context:
http://www.nabble.com/Cobertura-plugin-using-version-1.7-tf1889535.html#a5182548
Sent from the Maven - Users forum at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: cobertura plugin

2006-02-20 Thread Brett Porter
this problem was fixed in SVN (asm is no longer propogated to tests themselves)

On 2/20/06, javed mandary [EMAIL PROTECTED] wrote:
 Hi David,
  I solved the problem with the Cobertura plugin running
 hibernate junit tests by adding the following dependency in my POM:

 dependency
   groupIdasm/groupId
   artifactIdasm/artifactId
   version1.5.3/version
 /dependency


 It seems that Cobertura is looking for  asm-2.1 in its POM while hibernate
 requires asm-1.5.3.

 By setting the dependency asm-1.5.3 , this is placed in classpath and
 everything works fine , cobertura site report is generated successfully.

 regards,
   Javed



 On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  Maven 2 is what I am on about.  see the jira issue, but i am getting the
  same problem as you describe.  perhaps you'd like to vote on that issue and
  add your comments there.
 
  Kind regards,
  Dave Sag
 
 
 
 
 
 
  javed mandary [EMAIL PROTECTED] wrote on 17-02-2006 14:14:17:
 
   ok , what about the cobertura plugin for maven 2 ? In maven site I am
   getting a problem after cobertura runs the junit tests and try to create
  a
   report it crashes and fails the build.
  
   Has anyone got similar problems and any solutions to that?
  
   this is what i am using:
   plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdcobertura-maven-plugin/artifactId
   version2.0-SNAPSHOT/version
   executions
 execution
   goals
 goalclean/goal
   /goals
 /execution
   /executions
   /plugin
  
   regards,
 Javed
  
   On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
   
   
Hi Brett
   
I have files jira issue http://jira.codehaus.org/browse/MOJO-299 and
included an example project that displays the bug.
   
if you could put your repo manager code somewhere in a zip file I can
  try
it out here and see if I get the same problems.
   
Kind regards,
Dave Sag
   
   
   
   
   
   
Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006 13:33:08:
   
 Hi David,

 There might be a release coming up, but we haven't worked on your
  issue
and
 there are still some other issues outstanding that should be fixed
first.

 If you could confirm that cobertura fails for you on the repository
manager
 app (if SVN is a problem I can upload it somewhere), that would
  isolate
it
 to you environment over your particular project.

 Thanks,
 Brett

 On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  Sorry brett the last i heard from you was that you were working on
  the
  problem and there would be a release late this week.
 
  So I have been working on other things and waiting paitiently.
 
  But if you are now telling me I need to file a jira issue then
  that's
what
  i'll do.
 
  I'll have to put together a minimal project and reproduce the
  problem
in
  some code that is not the EPOs tho.  This probably won't happen
  today.
 
  Kind regards,
  Dave Sag
 
 
 
 
 
 
  Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006
  13:20:42:
 
   On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
   
   
Sorry are you talking about maven 1 or 2 plugin?
  
  
   They are talking about Maven 1.0
  
   I was told that 2.0-SNAPSHOT is the one to use for maven 2 but
  since
updating to maven 2.0.2 the reporting part of cobertura hasn't
worked.
  
  
   I can't reproduce it. If it never gets filed in JIRA, it'll
  never
get
   fixed... can you please do that at
http://jira.codehaus.org/browse/MOJO?
  
   Did you try the repository manager example I showed you last
  time
that
  is
   working for me?
  
   - Brett
 
   
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cobertura plugin

2006-02-20 Thread David Sag

I guess we are having different problems.
In a reply to my Jira issue Carlos Sanchez points out that my problem
lies in the fact that cobertura is trying to instrument the classes twice.
I am not sure why this is happening, nor am i sure why this is even
a problem, but clearly you are not getting this problem.

could you show me your pom.xml so i
can look for any obvious differences between what you are doing and what
I am doing.

Kind regards,
Dave Sag 




 

Brett Porter [EMAIL PROTECTED]
wrote on 20-02-2006 09:05:19:

 this problem was fixed in SVN (asm is no longer propogated to tests

 themselves)
 
 On 2/20/06, javed mandary [EMAIL PROTECTED] wrote:
  Hi David,
I solved the
problem with the Cobertura plugin running
  hibernate junit tests by adding the following dependency in my
POM:
 
dependency
 groupIdasm/groupId
 artifactIdasm/artifactId
 version1.5.3/version
/dependency
 
 
  It seems that Cobertura is looking for asm-2.1 in its POM
while hibernate
  requires asm-1.5.3.
 
  By setting the dependency asm-1.5.3 , this is placed in classpath
and
  everything works fine , cobertura site report is generated successfully.
 
  regards,
 Javed
 
 
 
  On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
  
  
   Maven 2 is what I am on about. see the jira issue,
but i am getting the
   same problem as you describe. perhaps you'd like to
vote on 
 that issue and
   add your comments there.
  
   Kind regards,
   Dave Sag
  
  
  
  
  
  
   javed mandary [EMAIL PROTECTED] wrote
on 17-02-2006 14:14:17:
  
ok , what about the cobertura plugin for maven 2 ?
In maven site I am
getting a problem after cobertura runs the junit tests
and tryto create
   a
report it crashes and fails the build.
   
Has anyone got similar problems and any solutions to
that?
   
this is what i am using:
plugin
   
groupIdorg.codehaus.mojo/groupId
   
artifactIdcobertura-maven-plugin/artifactId
   
version2.0-SNAPSHOT/version
   
executions
   
 execution
   
  goals
   
   goalclean/goal
   
  /goals
   
 /execution
   
/executions
  /plugin
   
regards,
   Javed
   
On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Hi Brett

 I have files jira issue http://jira.codehaus.org/browse/MOJO-299
and
 included an example project that displays the
bug.

 if you could put your repo manager code somewhere
in a zip file I can
   try
 it out here and see if I get the same problems.

 Kind regards,
 Dave Sag






 Brett Porter [EMAIL PROTECTED] wrote
on 17-02-2006 13:33:08:

  Hi David,
 
  There might be a release coming up, but we
haven't worked on your
   issue
 and
  there are still some other issues outstanding
that should be fixed
 first.
 
  If you could confirm that cobertura fails
for you on the repository
 manager
  app (if SVN is a problem I can upload it
somewhere), that would
   isolate
 it
  to you environment over your particular project.
 
  Thanks,
  Brett
 
  On 2/17/06, David Sag [EMAIL PROTECTED]
wrote:
  
  
   Sorry brett the last i heard from you
was that you were working on
   the
   problem and there would be a release
late this week.
  
   So I have been working on other things
and waiting paitiently.
  
   But if you are now telling me I need
to file a jira issue then
   that's
 what
   i'll do.
  
   I'll have to put together a minimal
project and reproduce the
   problem
 in
   some code that is not the EPOs tho.
This probably won't happen
   today.
  
   Kind regards,
   Dave Sag
  
  
  
  
  
  
   Brett Porter [EMAIL PROTECTED]
wrote on 17-02-2006
   13:20:42:
  
On 2/17/06, David Sag [EMAIL PROTECTED]
wrote:


 Sorry are you talking about
maven 1 or 2 plugin?
   
   
They are talking about Maven 1.0
   
I was told that 2.0-SNAPSHOT is
the one to use for maven 2 but
   since
 updating to maven 2.0.2 the
reporting part of cobertura hasn't
 worked.
   
   
I can't reproduce it. If it never
gets filed in JIRA, it'll
   never
 get
fixed... can you please do that
at
 http://jira.codehaus.org/browse/MOJO?
   
Did you try the repository manager
example I showed you last
   time
 that
   is
working for me?
   
- Brett
  

  
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


Re: cobertura plugin

2006-02-20 Thread javed mandary
Am running maven site with cobertura report generation:

?xml version=1.0 encoding=UTF-8?
project
[.]
build
resources
  resource
directorysrc/main/resources/directory
includes
  include*.xls/include
  include**/*.xml/include
  include*.properties/include
/includes
  /resource
/resources
   plugins
plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdsurefire-report-maven-plugin/artifactId
   version2.0-beta-1/version
   configuration
  testFailureIgnoretrue/testFailureIgnore
   /configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0-SNAPSHOT/version
   /plugin
  /plugins
  /build
  reporting
  plugins
  plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdsurefire-report-maven-plugin/artifactId
   version2.0-beta-1/version
 /plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0-SNAPSHOT/version
  /plugin
  /plugins
/reporting

dependencies
dependency
  groupIdasm/groupId
  artifactIdasm/artifactId
  version1.5.3/version
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring-mock/artifactId
version1.2.6/version
scopetest/scope
exclusions
exclusion
artifactIdjta/artifactId
groupIdjavax.transaction/groupId
/exclusion
exclusion
artifactIdjdbc-stdext/artifactId
groupIdjavax.sql/groupId
/exclusion
exclusion
artifactIdjsf-api/artifactId
groupIdjavax.faces/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring-remoting/artifactId
version1.2.6/version
/dependency
dependency
groupIdorg.springframework/groupId
artifactIdspring-core/artifactId
version1.2.6/version
/dependency
dependency
groupIdaxis/groupId
artifactIdaxis/artifactId
version1.2.1/version
exclusions
exclusion
artifactIdactivation/artifactId
groupIdjavax.activation/groupId
/exclusion
exclusion
artifactIdmail/artifactId
groupIdjavax.mail/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdaxis/groupId
artifactIdaxis-jaxrpc/artifactId
version1.2.1/version
/dependency
dependency
groupIdaxis/groupId
artifactIdaxis-saaj/artifactId
version1.2.1/version
/dependency

/dependencies
/project

On 2/20/06, David Sag [EMAIL PROTECTED] wrote:


 I guess we are having different problems.  In a reply to my Jira issue
 Carlos Sanchez points out that my problem lies in the fact that cobertura is
 trying to instrument the classes twice.  I am not sure why this is
 happening, nor am i sure why this is even a problem, but clearly you are not
 getting this problem.

 could you show me your pom.xml so i can look for any obvious differences
 between what you are doing and what I am doing.

 Kind regards,
 Dave Sag






 Brett Porter [EMAIL PROTECTED] wrote on 20-02-2006 09:05:19:

  this problem was fixed in SVN (asm is no longer propogated to tests
  themselves)
 
  On 2/20/06, javed mandary [EMAIL PROTECTED] wrote:
   Hi David,
I solved the problem with the Cobertura plugin running
   hibernate junit tests by adding the following dependency in my POM:
  
   dependency
 groupIdasm/groupId
 artifactIdasm/artifactId
 version1.5.3/version
   /dependency
  
  
   It seems that Cobertura is looking for  asm-2.1 in its POM while
 hibernate
   requires asm-1.5.3.
  
   By setting the dependency asm-1.5.3 , this is placed in classpath and
   everything works fine , cobertura site report is generated
 successfully.
  
   regards,
 Javed
  
  
  
   On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
   
   
Maven 2 is what I am on about.  see the jira issue, but i am getting
 the

Re: cobertura plugin

2006-02-20 Thread David Sag

Interesting

the main difference between the way
you do it and the way I am doing is that I specify the goal and execution
phase in my build declarations thusly:

  plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0-SNAPSHOT/version
executions
 execution
 
idinstrument-classes/id
 
phaseprocess-classes/phase
 
goals
 
 goalinstrument/goal
 
/goals
 /execution
/executions
   /plugin

could this be causing my problem? i
doubt it.

Also I explicitly tell surefire where
the instrumented classes are:

   !-- run
the unit tests on the cobertura instrumented classes --
   plugin
artifactIdmaven-surefire-plugin/artifactId
version2.0/version
configuration

classesDirectory${project.build.directory}/classes-instrumented/classesDirectory
/configuration
   /plugin

otherwise we are doing pretty much
the same thing.

I can't see in your pom.xml how your
tests know to run the instrumented classes, nor is it obvious in what phase
you are instrumenting your classes. what sort of coverage reports
are you getting?

Kind regards,
Dave Sag 




 

javed mandary [EMAIL PROTECTED]
wrote on 20-02-2006 13:57:41:

 Am running maven site with cobertura report generation:
 
 ?xml version=1.0 encoding=UTF-8?
 project
 [.]
   build
   resources
resource
 directorysrc/main/resources/directory
 includes
  include*.xls/include
  include**/*.xml/include
  include*.properties/include
 /includes
/resource
   /resources
plugins
  
plugin
  
 groupIdorg.codehaus.mojo/groupId
  
 artifactIdsurefire-report-maven-plugin/artifactId
  
 version2.0-beta-1/version
  
 configuration
  
   testFailureIgnoretrue/testFailureIgnore
  
 /configuration
  
/plugin
  
plugin
  
groupIdorg.codehaus.mojo/groupId
  
artifactIdcobertura-maven-plugin/artifactId
  
version2.0-SNAPSHOT/version
  /plugin
/plugins
/build
reporting
plugins
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdsurefire-report-maven-plugin/artifactId
  version2.0-beta-1/version
 /plugin
 plugin
  
groupIdorg.codehaus.mojo/groupId
  
artifactIdcobertura-maven-plugin/artifactId
  
version2.0-SNAPSHOT/version
  /plugin
/plugins
   /reporting
 
   dependencies
   dependency
groupIdasm/groupId
artifactIdasm/artifactId
version1.5.3/version
   /dependency
 dependency
   groupIdorg.springframework/groupId
   artifactIdspring-mock/artifactId
   version1.2.6/version
   scopetest/scope
   exclusions
 exclusion
  
artifactIdjta/artifactId
  
groupIdjavax.transaction/groupId
 /exclusion
 exclusion
  
artifactIdjdbc-stdext/artifactId
  
groupIdjavax.sql/groupId
 /exclusion
 exclusion
  
artifactIdjsf-api/artifactId
  
groupIdjavax.faces/groupId
 /exclusion
   /exclusions
 /dependency
 dependency
   groupIdorg.springframework/groupId
   artifactIdspring-remoting/artifactId
   version1.2.6/version
 /dependency
 dependency
   groupIdorg.springframework/groupId
   artifactIdspring-core/artifactId
   version1.2.6/version
 /dependency
 dependency
   groupIdaxis/groupId
   artifactIdaxis/artifactId
   version1.2.1/version
   exclusions
 exclusion
  
artifactIdactivation/artifactId
  
groupIdjavax.activation/groupId
 /exclusion
 exclusion
  
artifactIdmail/artifactId
  
groupIdjavax.mail/groupId
 /exclusion
   /exclusions
 /dependency
 dependency
   groupIdaxis/groupId
   artifactIdaxis-jaxrpc/artifactId
   version1.2.1/version
 /dependency
 dependency
   groupIdaxis/groupId
   artifactIdaxis-saaj/artifactId
   version1.2.1/version
 /dependency
 
   /dependencies
 /project
 
 On 2/20/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  I guess we are having different problems. In a reply to
my Jira issue
  Carlos Sanchez points out that my problem lies in the fact that
cobertura is
  trying to instrument the classes twice. I am not sure why
this is
  happening, nor am i sure why this is even a problem, but clearly
you are not
  getting this problem.
 
  could you show me your pom.xml so i can look for any obvious
differences
  between what you are doing and what I am doing.
 
  Kind regards,
  Dave Sag
 
 
 
 
 
 
  Brett Porter [EMAIL PROTECTED] wrote
on 20-02-2006 09:05:19:
 
   this problem was fixed in SVN (asm is no longer propogated
to tests
   themselves)
  
   On 2/20/06, javed mandary [EMAIL PROTECTED] wrote:
Hi David,
  I solved
the problem with the Cobertura plugin running
hibernate 

RE: cobertura plugin

2006-02-20 Thread Mike Perham
David, you are way overcomplicating the cobertura setup.  Remove your
executions and the surefire config.  There's no need - all this is
handled internally when the plugin executes with 'cobertura:cobertura'.

  _  

From: David Sag [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 20, 2006 7:20 AM
To: Maven Users List
Subject: Re: cobertura plugin



Interesting 

the main difference between the way you do it and the way I am doing is
that I specify the goal and execution phase in my build declarations
thusly: 

 plugin 
groupIdorg.codehaus.mojo/groupId 
artifactIdcobertura-maven-plugin/artifactId 
version2.0-SNAPSHOT/version 
executions 
  execution 
idinstrument-classes/id 
phaseprocess-classes/phase 
goals 
  goalinstrument/goal 
/goals 
  /execution 
/executions 
  /plugin

could this be causing my problem?  i doubt it. 

Also I explicitly tell surefire where the instrumented classes are: 

  !-- run the unit tests on the cobertura instrumented classes -- 
  plugin 
artifactIdmaven-surefire-plugin/artifactId 
version2.0/version 
configuration 
 
classesDirectory${project.build.directory}/classes-instrumented/class
esDirectory 
/configuration 
  /plugin 

otherwise we are doing pretty much the same thing. 

I can't see in your pom.xml how your tests know to run the instrumented
classes, nor is it obvious in what phase you are instrumenting your
classes.  what sort of coverage reports are you getting? 

Kind regards,
Dave Sag 




  

javed mandary [EMAIL PROTECTED] wrote on 20-02-2006 13:57:41:

 Am running maven site with cobertura report generation:
 
 ?xml version=1.0 encoding=UTF-8?
 project
 [.]
 build
 resources
   resource
 directorysrc/main/resources/directory
 includes
   include*.xls/include
   include**/*.xml/include
   include*.properties/include
 /includes
   /resource
 /resources
plugins
 plugin
groupIdorg.codehaus.mojo/groupId

artifactIdsurefire-report-maven-plugin/artifactId
version2.0-beta-1/version
configuration
   testFailureIgnoretrue/testFailureIgnore
/configuration
 /plugin
 plugin
 groupIdorg.codehaus.mojo/groupId

artifactIdcobertura-maven-plugin/artifactId
 version2.0-SNAPSHOT/version
/plugin
   /plugins
   /build
   reporting
   plugins
   plugin
groupIdorg.codehaus.mojo/groupId

artifactIdsurefire-report-maven-plugin/artifactId
version2.0-beta-1/version
  /plugin
 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdcobertura-maven-plugin/artifactId
 version2.0-SNAPSHOT/version
   /plugin
   /plugins
 /reporting
 
 dependencies
 dependency
   groupIdasm/groupId
   artifactIdasm/artifactId
   version1.5.3/version
 /dependency
 dependency
 groupIdorg.springframework/groupId
 artifactIdspring-mock/artifactId
 version1.2.6/version
 scopetest/scope
 exclusions
 exclusion
 artifactIdjta/artifactId
 groupIdjavax.transaction/groupId
 /exclusion
 exclusion
 artifactIdjdbc-stdext/artifactId
 groupIdjavax.sql/groupId
 /exclusion
 exclusion
 artifactIdjsf-api/artifactId
 groupIdjavax.faces/groupId
 /exclusion
 /exclusions
 /dependency
 dependency
 groupIdorg.springframework/groupId
 artifactIdspring-remoting/artifactId
 version1.2.6/version
 /dependency
 dependency
 groupIdorg.springframework/groupId
 artifactIdspring-core/artifactId
 version1.2.6/version
 /dependency
 dependency
 groupIdaxis/groupId
 artifactIdaxis/artifactId
 version1.2.1/version
 exclusions
 exclusion
 artifactIdactivation/artifactId
 groupIdjavax.activation/groupId
 /exclusion
 exclusion
 artifactIdmail/artifactId
 groupIdjavax.mail/groupId
 /exclusion
 /exclusions
 /dependency
 dependency
 groupIdaxis/groupId

RE: cobertura plugin

2006-02-20 Thread David Sag

You are so right. Removing the extra
configuration solved all of my cobertura problems.

Kind regards,
Dave Sag 




 

Mike Perham [EMAIL PROTECTED]
wrote on 20-02-2006 15:44:17:

 David, you are way overcomplicating the cobertura setup. Remove
your
 executions and the surefire config. There's no need - all this
is
 handled internally when the plugin executes with 'cobertura:cobertura'.
 
  _ 
 
 From: David Sag [mailto:[EMAIL PROTECTED] 
 Sent: Monday, February 20, 2006 7:20 AM
 To: Maven Users List
 Subject: Re: cobertura plugin
 
 
 
 Interesting 
 
 the main difference between the way you do it and the way I am doing
is
 that I specify the goal and execution phase in my build declarations
 thusly: 
 
   plugin 
 groupIdorg.codehaus.mojo/groupId

 artifactIdcobertura-maven-plugin/artifactId

 version2.0-SNAPSHOT/version

 executions 
  execution 
   idinstrument-classes/id

   phaseprocess-classes/phase

   goals 
goalinstrument/goal

   /goals 
  /execution 
 /executions 
/plugin
 
 could this be causing my problem? i doubt it. 
 
 Also I explicitly tell surefire where the instrumented classes are:

 
!-- run the unit tests on the cobertura instrumented
classes -- 
plugin 
 artifactIdmaven-surefire-plugin/artifactId

 version2.0/version 
 configuration 
 
 classesDirectory${project.build.directory}/classes-instrumented/class
 esDirectory 
 /configuration 
/plugin 
 
 otherwise we are doing pretty much the same thing. 
 
 I can't see in your pom.xml how your tests know to run the instrumented
 classes, nor is it obvious in what phase you are instrumenting your
 classes. what sort of coverage reports are you getting? 
 
 Kind regards,
 Dave Sag 
 
 
 
 
  
 
 javed mandary [EMAIL PROTECTED] wrote on 20-02-2006
13:57:41:
 
  Am running maven site with cobertura report generation:
  
  ?xml version=1.0 encoding=UTF-8?
  project
  [.]
build
resources
 resource
  directorysrc/main/resources/directory
  includes
  
include*.xls/include
  
include**/*.xml/include
  
include*.properties/include
  /includes
 /resource
/resources
 plugins
  
 plugin
  
  groupIdorg.codehaus.mojo/groupId
 
 artifactIdsurefire-report-maven-plugin/artifactId
  
  version2.0-beta-1/version
  
  configuration
  
testFailureIgnoretrue/testFailureIgnore
  
  /configuration
  
 /plugin
  
 plugin
  
 groupIdorg.codehaus.mojo/groupId
 
 artifactIdcobertura-maven-plugin/artifactId
  
 version2.0-SNAPSHOT/version
  
/plugin
 /plugins
 /build
 reporting
 plugins
   plugin
  
groupIdorg.codehaus.mojo/groupId
 
 artifactIdsurefire-report-maven-plugin/artifactId
  
version2.0-beta-1/version
  /plugin
  plugin
  
 groupIdorg.codehaus.mojo/groupId
  
 artifactIdcobertura-maven-plugin/artifactId
  
 version2.0-SNAPSHOT/version
   /plugin
 /plugins
/reporting
  
dependencies
dependency
 groupIdasm/groupId
 artifactIdasm/artifactId
 version1.5.3/version
/dependency
  dependency
groupIdorg.springframework/groupId
artifactIdspring-mock/artifactId
version1.2.6/version
scopetest/scope
exclusions
  exclusion
  
 artifactIdjta/artifactId
  
 groupIdjavax.transaction/groupId
  /exclusion
  exclusion
  
 artifactIdjdbc-stdext/artifactId
  
 groupIdjavax.sql/groupId
  /exclusion
  exclusion
  
 artifactIdjsf-api/artifactId
  
 groupIdjavax.faces/groupId
  /exclusion
/exclusions
  /dependency
  dependency
groupIdorg.springframework/groupId
artifactIdspring-remoting/artifactId
version1.2.6/version
  /dependency
  dependency
groupIdorg.springframework/groupId
artifactIdspring-core/artifactId
version1.2.6/version
  /dependency
  dependency
groupIdaxis/groupId
artifactIdaxis/artifactId
version1.2.1/version
exclusions
  exclusion
  
 artifactIdactivation/artifactId
  
 groupIdjavax.activation/groupId
  /exclusion
  exclusion
  
 artifactIdmail/artifactId
  
 groupIdjavax.mail/groupId
  /exclusion
/exclusions
  /dependency
  dependency
groupIdaxis/groupId
artifactIdaxis-jaxrpc/artifactId
version1.2.1/version
  /dependency
  dependency
groupIdaxis/groupId
artifactIdaxis-saaj/artifactId
version1.2.1/version
  /dependency
  
/dependencies
  /project
  
  On 2/20/06, David Sag [EMAIL PROTECTED] wrote:
  
  
   I guess we are having different problems. In a reply
to my Jira
 issue
   Carlos

Re: cobertura plugin

2006-02-19 Thread javed mandary
Hi David,
 I solved the problem with the Cobertura plugin running
hibernate junit tests by adding the following dependency in my POM:

dependency
  groupIdasm/groupId
  artifactIdasm/artifactId
  version1.5.3/version
/dependency


It seems that Cobertura is looking for  asm-2.1 in its POM while hibernate
requires asm-1.5.3.

By setting the dependency asm-1.5.3 , this is placed in classpath and
everything works fine , cobertura site report is generated successfully.

regards,
  Javed



On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Maven 2 is what I am on about.  see the jira issue, but i am getting the
 same problem as you describe.  perhaps you'd like to vote on that issue and
 add your comments there.

 Kind regards,
 Dave Sag






 javed mandary [EMAIL PROTECTED] wrote on 17-02-2006 14:14:17:

  ok , what about the cobertura plugin for maven 2 ? In maven site I am
  getting a problem after cobertura runs the junit tests and try to create
 a
  report it crashes and fails the build.
 
  Has anyone got similar problems and any solutions to that?
 
  this is what i am using:
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdcobertura-maven-plugin/artifactId
  version2.0-SNAPSHOT/version
  executions
execution
  goals
goalclean/goal
  /goals
/execution
  /executions
  /plugin
 
  regards,
Javed
 
  On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
  
  
   Hi Brett
  
   I have files jira issue http://jira.codehaus.org/browse/MOJO-299 and
   included an example project that displays the bug.
  
   if you could put your repo manager code somewhere in a zip file I can
 try
   it out here and see if I get the same problems.
  
   Kind regards,
   Dave Sag
  
  
  
  
  
  
   Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006 13:33:08:
  
Hi David,
   
There might be a release coming up, but we haven't worked on your
 issue
   and
there are still some other issues outstanding that should be fixed
   first.
   
If you could confirm that cobertura fails for you on the repository
   manager
app (if SVN is a problem I can upload it somewhere), that would
 isolate
   it
to you environment over your particular project.
   
Thanks,
Brett
   
On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Sorry brett the last i heard from you was that you were working on
 the
 problem and there would be a release late this week.

 So I have been working on other things and waiting paitiently.

 But if you are now telling me I need to file a jira issue then
 that's
   what
 i'll do.

 I'll have to put together a minimal project and reproduce the
 problem
   in
 some code that is not the EPOs tho.  This probably won't happen
 today.

 Kind regards,
 Dave Sag






 Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006
 13:20:42:

  On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
  
  
   Sorry are you talking about maven 1 or 2 plugin?
 
 
  They are talking about Maven 1.0
 
  I was told that 2.0-SNAPSHOT is the one to use for maven 2 but
 since
   updating to maven 2.0.2 the reporting part of cobertura hasn't
   worked.
 
 
  I can't reproduce it. If it never gets filed in JIRA, it'll
 never
   get
  fixed... can you please do that at
   http://jira.codehaus.org/browse/MOJO?
 
  Did you try the repository manager example I showed you last
 time
   that
 is
  working for me?
 
  - Brett

  



Re: cobertura plugin

2006-02-17 Thread David Sag

Please - that would be nice.

Kind regards,
Dave Sag 




 

Arnaud HERITIER [EMAIL PROTECTED] wrote
on 16-02-2006 16:24:10:

 Isn't it possible to release it ?
 
 Arnaud
 
 On 2/16/06, Mike Perham [EMAIL PROTECTED] wrote:
  The plugin code in SVN already uses 1.7. It's never been
released so
  you must be using an old version you compiled. Update svn
and recompile
  it.
 
  -Original Message-
  From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
  Sent: Thursday, February 16, 2006 8:36 AM
  To: Maven Users List
  Subject: cobertura plugin
 
 
  Is there any plan to upgrade cobertura plugin to use cobertura
1.7 ?
 
  I'm using AspectJ and JiBX that both operate on bytecode and
are not
  compatible with cobertura 1.6 instrumentation (plugin fails)
 
  Upgrading dependency to 1.7 solves this problem
 
  I've created
  http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
  d=61626atid=497853
  for this.
 
  Nico.
 
  This message contains information that may be privileged or confidential
  and is the property of the Capgemini Group. It is intended only
for the
  person to whom it is addressed. If you are not the intended recipient,
  you are not authorized to read, print, retain, copy, disseminate,
  distribute, or use this message or any part thereof. If you receive
this
  message in error, please notify the sender immediately and delete
all
  copies of this message.
 
 
  -
  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]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


Re: cobertura plugin

2006-02-17 Thread Nicolas De Loof


1.2-SNAPSHOT works fine for me.

Thanks !

Nicolas De Loof a écrit :

I'm using maven-cobertura-plugin from [EMAIL PROTECTED]
As this site uses CVS, this seems you've in mind another cobertura 
plugin. Where to find it ?


Mike Perham a écrit :


The plugin code in SVN already uses 1.7.  It's never been released so
you must be using an old version you compiled.  Update svn and recompile
it.

-Original Message-
From: Nicolas De Loof [mailto:[EMAIL PROTECTED] Sent: 
Thursday, February 16, 2006 8:36 AM

To: Maven Users List
Subject: cobertura plugin


Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

I'm using AspectJ and JiBX that both operate on bytecode and are not
compatible with cobertura 1.6 instrumentation (plugin fails)

Upgrading dependency to 1.7 solves this problem

I've created
http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
d=61626atid=497853
for this.

Nico.

This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.


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


 





This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cobertura plugin

2006-02-17 Thread javed mandary
Is the 1.2-SNAPSHOT for maven 1 or for maven 2 ?

On 2/17/06, Nicolas De Loof [EMAIL PROTECTED] wrote:


 1.2-SNAPSHOT works fine for me.

 Thanks !

 Nicolas De Loof a écrit :
  I'm using maven-cobertura-plugin from [EMAIL PROTECTED]
  As this site uses CVS, this seems you've in mind another cobertura
  plugin. Where to find it ?
 
  Mike Perham a écrit :
 
  The plugin code in SVN already uses 1.7.  It's never been released so
  you must be using an old version you compiled.  Update svn and
 recompile
  it.
 
  -Original Message-
  From: Nicolas De Loof [mailto:[EMAIL PROTECTED] Sent:
  Thursday, February 16, 2006 8:36 AM
  To: Maven Users List
  Subject: cobertura plugin
 
 
  Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?
 
  I'm using AspectJ and JiBX that both operate on bytecode and are not
  compatible with cobertura 1.6 instrumentation (plugin fails)
 
  Upgrading dependency to 1.7 solves this problem
 
  I've created
 
 http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
  d=61626atid=497853
  for this.
 
  Nico.
 
  This message contains information that may be privileged or
 confidential
  and is the property of the Capgemini Group. It is intended only for the
  person to whom it is addressed. If you are not the intended recipient,
  you are not authorized to read, print, retain, copy, disseminate,
  distribute, or use this message or any part thereof. If you receive
 this
  message in error, please notify the sender immediately and delete all
  copies of this message.
 
 
  -
  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]
 
 
 
 
 

 This message contains information that may be privileged or confidential
 and is the property of the Capgemini Group. It is intended only for the
 person to whom it is addressed. If you are not the intended recipient,  you
 are not authorized to read, print, retain, copy, disseminate,  distribute,
 or use this message or any part thereof. If you receive this  message in
 error, please notify the sender immediately and delete all  copies of this
 message.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: cobertura plugin

2006-02-17 Thread Arnaud HERITIER
maven 1

Arnaud

On 2/17/06, javed mandary [EMAIL PROTECTED] wrote:
 Is the 1.2-SNAPSHOT for maven 1 or for maven 2 ?

 On 2/17/06, Nicolas De Loof [EMAIL PROTECTED] wrote:
 
 
  1.2-SNAPSHOT works fine for me.
 
  Thanks !
 
  Nicolas De Loof a écrit :
   I'm using maven-cobertura-plugin from [EMAIL PROTECTED]
   As this site uses CVS, this seems you've in mind another cobertura
   plugin. Where to find it ?
  
   Mike Perham a écrit :
  
   The plugin code in SVN already uses 1.7.  It's never been released so
   you must be using an old version you compiled.  Update svn and
  recompile
   it.
  
   -Original Message-
   From: Nicolas De Loof [mailto:[EMAIL PROTECTED] Sent:
   Thursday, February 16, 2006 8:36 AM
   To: Maven Users List
   Subject: cobertura plugin
  
  
   Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?
  
   I'm using AspectJ and JiBX that both operate on bytecode and are not
   compatible with cobertura 1.6 instrumentation (plugin fails)
  
   Upgrading dependency to 1.7 solves this problem
  
   I've created
  
  http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
   d=61626atid=497853
   for this.
  
   Nico.
  
   This message contains information that may be privileged or
  confidential
   and is the property of the Capgemini Group. It is intended only for the
   person to whom it is addressed. If you are not the intended recipient,
   you are not authorized to read, print, retain, copy, disseminate,
   distribute, or use this message or any part thereof. If you receive
  this
   message in error, please notify the sender immediately and delete all
   copies of this message.
  
  
   -
   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]
  
  
  
  
  
 
  This message contains information that may be privileged or confidential
  and is the property of the Capgemini Group. It is intended only for the
  person to whom it is addressed. If you are not the intended recipient,  you
  are not authorized to read, print, retain, copy, disseminate,  distribute,
  or use this message or any part thereof. If you receive this  message in
  error, please notify the sender immediately and delete all  copies of this
  message.
 
 
  -
  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]



Re: cobertura plugin

2006-02-17 Thread David Sag

Sorry are you talking about maven 1
or 2 plugin?

I was told that 2.0-SNAPSHOT is the
one to use for maven 2 but since updating to maven 2.0.2 the reporting
part of cobertura hasn't worked.

Kind regards,
Dave Sag 




 

Nicolas De Loof [EMAIL PROTECTED]
wrote on 17-02-2006 11:12:27:

 
 1.2-SNAPSHOT works fine for me.
 
 Thanks !
 
 Nicolas De Loof a écrit :
  I'm using maven-cobertura-plugin from [EMAIL PROTECTED]
  As this site uses CVS, this seems you've in mind another cobertura

  plugin. Where to find it ?
 
  Mike Perham a écrit :
 
  The plugin code in SVN already uses 1.7. It's never
been released so
  you must be using an old version you compiled. Update
svn and recompile
  it.
 
  -Original Message-
  From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
Sent: 
  Thursday, February 16, 2006 8:36 AM
  To: Maven Users List
  Subject: cobertura plugin
 
 
  Is there any plan to upgrade cobertura plugin to use cobertura
1.7 ?
 
  I'm using AspectJ and JiBX that both operate on bytecode
and are not
  compatible with cobertura 1.6 instrumentation (plugin fails)
 
  Upgrading dependency to 1.7 solves this problem
 
  I've created
  http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
  d=61626atid=497853
  for this.
 
  Nico.
 
  This message contains information that may be privileged
or confidential
  and is the property of the Capgemini Group. It is intended
only for the
  person to whom it is addressed. If you are not the intended
recipient,
  you are not authorized to read, print, retain, copy, disseminate,
  distribute, or use this message or any part thereof. If you
receive this
  message in error, please notify the sender immediately and
delete all
  copies of this message.
 
 
  -
  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]
 
 
  
 
 
 
 This message contains information that may be privileged or 
 confidential and is the property of the Capgemini Group. It is 
 intended only for the person to whom it is addressed. If you are not
 the intended recipient, you are not authorized to read, print,

 retain, copy, disseminate, distribute, or use this message or
any 
 part thereof. If you receive this message in error, please notify

 the sender immediately and delete all copies of this message.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


Re: cobertura plugin

2006-02-17 Thread Brett Porter
On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Sorry are you talking about maven 1 or 2 plugin?


They are talking about Maven 1.0

I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since
 updating to maven 2.0.2 the reporting part of cobertura hasn't worked.


I can't reproduce it. If it never gets filed in JIRA, it'll never get
fixed... can you please do that at http://jira.codehaus.org/browse/MOJO?

Did you try the repository manager example I showed you last time that is
working for me?

- Brett


Re: cobertura plugin

2006-02-17 Thread David Sag

Sorry brett the last i heard from you
was that you were working on the problem and there would be a release late
this week.

So I have been working on other things
and waiting paitiently.

But if you are now telling me I need
to file a jira issue then that's what i'll do. 

I'll have to put together a minimal
project and reproduce the problem in some code that is not the EPOs tho.
This probably won't happen today.

Kind regards,
Dave Sag 




 

Brett Porter [EMAIL PROTECTED] wrote
on 17-02-2006 13:20:42:

 On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  Sorry are you talking about maven 1 or 2 plugin?
 
 
 They are talking about Maven 1.0
 
 I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since
  updating to maven 2.0.2 the reporting part of cobertura hasn't
worked.
 
 
 I can't reproduce it. If it never gets filed in JIRA, it'll never
get
 fixed... can you please do that at http://jira.codehaus.org/browse/MOJO?
 
 Did you try the repository manager example I showed you last time
that is
 working for me?
 
 - Brett


Re: cobertura plugin

2006-02-17 Thread Brett Porter
Hi David,

There might be a release coming up, but we haven't worked on your issue and
there are still some other issues outstanding that should be fixed first.

If you could confirm that cobertura fails for you on the repository manager
app (if SVN is a problem I can upload it somewhere), that would isolate it
to you environment over your particular project.

Thanks,
Brett

On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Sorry brett the last i heard from you was that you were working on the
 problem and there would be a release late this week.

 So I have been working on other things and waiting paitiently.

 But if you are now telling me I need to file a jira issue then that's what
 i'll do.

 I'll have to put together a minimal project and reproduce the problem in
 some code that is not the EPOs tho.  This probably won't happen today.

 Kind regards,
 Dave Sag






 Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006 13:20:42:

  On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
  
  
   Sorry are you talking about maven 1 or 2 plugin?
 
 
  They are talking about Maven 1.0
 
  I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since
   updating to maven 2.0.2 the reporting part of cobertura hasn't worked.
 
 
  I can't reproduce it. If it never gets filed in JIRA, it'll never get
  fixed... can you please do that at http://jira.codehaus.org/browse/MOJO?
 
  Did you try the repository manager example I showed you last time that
 is
  working for me?
 
  - Brett



Re: cobertura plugin

2006-02-17 Thread David Sag

Hi Brett

I have files jira issue http://jira.codehaus.org/browse/MOJO-299
and included an example project that displays the bug.

if you could put your repo manager code
somewhere in a zip file I can try it out here and see if I get the same
problems.

Kind regards,
Dave Sag 




 

Brett Porter [EMAIL PROTECTED] wrote
on 17-02-2006 13:33:08:

 Hi David,
 
 There might be a release coming up, but we haven't worked on your
issue and
 there are still some other issues outstanding that should be fixed
first.
 
 If you could confirm that cobertura fails for you on the repository
manager
 app (if SVN is a problem I can upload it somewhere), that would isolate
it
 to you environment over your particular project.
 
 Thanks,
 Brett
 
 On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  Sorry brett the last i heard from you was that you were working
on the
  problem and there would be a release late this week.
 
  So I have been working on other things and waiting paitiently.
 
  But if you are now telling me I need to file a jira issue then
that's what
  i'll do.
 
  I'll have to put together a minimal project and reproduce the
problem in
  some code that is not the EPOs tho. This probably won't
happen today.
 
  Kind regards,
  Dave Sag
 
 
 
 
 
 
  Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006
13:20:42:
 
   On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
   
   
Sorry are you talking about maven 1 or 2 plugin?
  
  
   They are talking about Maven 1.0
  
   I was told that 2.0-SNAPSHOT is the one to use for maven
2 but since
updating to maven 2.0.2 the reporting part of cobertura
hasn't worked.
  
  
   I can't reproduce it. If it never gets filed in JIRA, it'll
never get
   fixed... can you please do that at http://jira.codehaus.org/browse/MOJO?
  
   Did you try the repository manager example I showed you
last time that
  is
   working for me?
  
   - Brett
 


Re: cobertura plugin

2006-02-17 Thread javed mandary
ok , what about the cobertura plugin for maven 2 ? In maven site I am
getting a problem after cobertura runs the junit tests and try to create a
report it crashes and fails the build.

Has anyone got similar problems and any solutions to that?

this is what i am using:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.0-SNAPSHOT/version
executions
  execution
goals
  goalclean/goal
/goals
  /execution
/executions
/plugin

regards,
  Javed

On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Hi Brett

 I have files jira issue http://jira.codehaus.org/browse/MOJO-299 and
 included an example project that displays the bug.

 if you could put your repo manager code somewhere in a zip file I can try
 it out here and see if I get the same problems.

 Kind regards,
 Dave Sag






 Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006 13:33:08:

  Hi David,
 
  There might be a release coming up, but we haven't worked on your issue
 and
  there are still some other issues outstanding that should be fixed
 first.
 
  If you could confirm that cobertura fails for you on the repository
 manager
  app (if SVN is a problem I can upload it somewhere), that would isolate
 it
  to you environment over your particular project.
 
  Thanks,
  Brett
 
  On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
  
  
   Sorry brett the last i heard from you was that you were working on the
   problem and there would be a release late this week.
  
   So I have been working on other things and waiting paitiently.
  
   But if you are now telling me I need to file a jira issue then that's
 what
   i'll do.
  
   I'll have to put together a minimal project and reproduce the problem
 in
   some code that is not the EPOs tho.  This probably won't happen today.
  
   Kind regards,
   Dave Sag
  
  
  
  
  
  
   Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006 13:20:42:
  
On 2/17/06, David Sag [EMAIL PROTECTED] wrote:


 Sorry are you talking about maven 1 or 2 plugin?
   
   
They are talking about Maven 1.0
   
I was told that 2.0-SNAPSHOT is the one to use for maven 2 but since
 updating to maven 2.0.2 the reporting part of cobertura hasn't
 worked.
   
   
I can't reproduce it. If it never gets filed in JIRA, it'll never
 get
fixed... can you please do that at
 http://jira.codehaus.org/browse/MOJO?
   
Did you try the repository manager example I showed you last time
 that
   is
working for me?
   
- Brett
  



Re: cobertura plugin

2006-02-17 Thread David Sag

Maven 2 is what I am on about. see
the jira issue, but i am getting the same problem as you describe. perhaps
you'd like to vote on that issue and add your comments there.

Kind regards,
Dave Sag 




 

javed mandary [EMAIL PROTECTED]
wrote on 17-02-2006 14:14:17:

 ok , what about the cobertura plugin for maven 2 ? In maven site I
am
 getting a problem after cobertura runs the junit tests and try to
create a
 report it crashes and fails the build.
 
 Has anyone got similar problems and any solutions to that?
 
 this is what i am using:
 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdcobertura-maven-plugin/artifactId
 version2.0-SNAPSHOT/version
 executions
  execution
  
goals
  
 goalclean/goal
  
/goals
  /execution
 /executions
   /plugin
 
 regards,
Javed
 
 On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  Hi Brett
 
  I have files jira issue http://jira.codehaus.org/browse/MOJO-299
and
  included an example project that displays the bug.
 
  if you could put your repo manager code somewhere in a zip file
I can try
  it out here and see if I get the same problems.
 
  Kind regards,
  Dave Sag
 
 
 
 
 
 
  Brett Porter [EMAIL PROTECTED] wrote on 17-02-2006
13:33:08:
 
   Hi David,
  
   There might be a release coming up, but we haven't worked
on your issue
  and
   there are still some other issues outstanding that should
be fixed
  first.
  
   If you could confirm that cobertura fails for you on the
repository
  manager
   app (if SVN is a problem I can upload it somewhere), that
would isolate
  it
   to you environment over your particular project.
  
   Thanks,
   Brett
  
   On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
   
   
Sorry brett the last i heard from you was that you
were working on the
problem and there would be a release late this week.
   
So I have been working on other things and waiting
paitiently.
   
But if you are now telling me I need to file a jira
issue then that's
  what
i'll do.
   
I'll have to put together a minimal project and reproduce
the problem
  in
some code that is not the EPOs tho. This probably
won't happen today.
   
Kind regards,
Dave Sag
   
   
   
   
   
   
Brett Porter [EMAIL PROTECTED] wrote on
17-02-2006 13:20:42:
   
 On 2/17/06, David Sag [EMAIL PROTECTED] wrote:
 
 
  Sorry are you talking about maven 1 or 2
plugin?


 They are talking about Maven 1.0

 I was told that 2.0-SNAPSHOT is the one to use
for maven 2 but since
  updating to maven 2.0.2 the reporting part
of cobertura hasn't
  worked.


 I can't reproduce it. If it never gets filed in
JIRA, it'll never
  get
 fixed... can you please do that at
  http://jira.codehaus.org/browse/MOJO?

 Did you try the repository manager example I showed
you last time
  that
is
 working for me?

 - Brett
   
 


Re: cobertura plugin

2006-02-16 Thread Arnaud HERITIER
I'm not a developer on mavenn plugins @ sf and I don't if there's lot
of activity.
If nobody can do it, I'll ask to add me to the dev team to do it.

Arnaud

On 2/16/06, Nicolas De Loof [EMAIL PROTECTED] wrote:

 Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

 I'm using AspectJ and JiBX that both operate on bytecode and are not
 compatible with cobertura 1.6 instrumentation (plugin fails)

 Upgrading dependency to 1.7 solves this problem

 I've created
 http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_id=61626atid=497853
 for this.

 Nico.

 This message contains information that may be privileged or confidential and 
 is the property of the Capgemini Group. It is intended only for the person to 
 whom it is addressed. If you are not the intended recipient,  you are not 
 authorized to read, print, retain, copy, disseminate,  distribute, or use 
 this message or any part thereof. If you receive this  message in error, 
 please notify the sender immediately and delete all  copies of this message.


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



RE: cobertura plugin

2006-02-16 Thread Mike Perham
The plugin code in SVN already uses 1.7.  It's never been released so
you must be using an old version you compiled.  Update svn and recompile
it.

-Original Message-
From: Nicolas De Loof [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 16, 2006 8:36 AM
To: Maven Users List
Subject: cobertura plugin


Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

I'm using AspectJ and JiBX that both operate on bytecode and are not
compatible with cobertura 1.6 instrumentation (plugin fails)

Upgrading dependency to 1.7 solves this problem

I've created
http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
d=61626atid=497853
for this.

Nico.

This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.


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



Re: cobertura plugin

2006-02-16 Thread Arnaud HERITIER
Isn't it possible to release it ?

Arnaud

On 2/16/06, Mike Perham [EMAIL PROTECTED] wrote:
 The plugin code in SVN already uses 1.7.  It's never been released so
 you must be using an old version you compiled.  Update svn and recompile
 it.

 -Original Message-
 From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 16, 2006 8:36 AM
 To: Maven Users List
 Subject: cobertura plugin


 Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

 I'm using AspectJ and JiBX that both operate on bytecode and are not
 compatible with cobertura 1.6 instrumentation (plugin fails)

 Upgrading dependency to 1.7 solves this problem

 I've created
 http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
 d=61626atid=497853
 for this.

 Nico.

 This message contains information that may be privileged or confidential
 and is the property of the Capgemini Group. It is intended only for the
 person to whom it is addressed. If you are not the intended recipient,
 you are not authorized to read, print, retain, copy, disseminate,
 distribute, or use this message or any part thereof. If you receive this
 message in error, please notify the sender immediately and delete all
 copies of this message.


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



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cobertura plugin

2006-02-16 Thread Nicolas De Loof


I'm using maven-cobertura-plugin from [EMAIL PROTECTED]
As this site uses CVS, this seems you've in mind another cobertura 
plugin. Where to find it ?


Mike Perham a écrit :


The plugin code in SVN already uses 1.7.  It's never been released so
you must be using an old version you compiled.  Update svn and recompile
it.

-Original Message-
From: Nicolas De Loof [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 16, 2006 8:36 AM

To: Maven Users List
Subject: cobertura plugin


Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

I'm using AspectJ and JiBX that both operate on bytecode and are not
compatible with cobertura 1.6 instrumentation (plugin fails)

Upgrading dependency to 1.7 solves this problem

I've created
http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_i
d=61626atid=497853
for this.

Nico.

This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.


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


 



This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: cobertura plugin

2006-02-16 Thread Mike Perham
It's still in the mojo sandbox.  Brett and I were working on it a week
or two ago.  Personally I think it's ready to promote out of the sandbox
to a top level plugin and an initial alpha release. 

-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 16, 2006 9:24 AM
To: Maven Users List
Subject: Re: cobertura plugin

Isn't it possible to release it ?

Arnaud

On 2/16/06, Mike Perham [EMAIL PROTECTED] wrote:
 The plugin code in SVN already uses 1.7.  It's never been released so 
 you must be using an old version you compiled.  Update svn and 
 recompile it.

 -Original Message-
 From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
 Sent: Thursday, February 16, 2006 8:36 AM
 To: Maven Users List
 Subject: cobertura plugin


 Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

 I'm using AspectJ and JiBX that both operate on bytecode and are not 
 compatible with cobertura 1.6 instrumentation (plugin fails)

 Upgrading dependency to 1.7 solves this problem

 I've created
 http://sourceforge.net/tracker/index.php?func=detailaid=1432911group
 _i
 d=61626atid=497853
 for this.

 Nico.

 This message contains information that may be privileged or 
 confidential and is the property of the Capgemini Group. It is 
 intended only for the person to whom it is addressed. If you are not 
 the intended recipient, you are not authorized to read, print, retain,

 copy, disseminate, distribute, or use this message or any part 
 thereof. If you receive this message in error, please notify the 
 sender immediately and delete all copies of this message.


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



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



RE: cobertura plugin

2006-02-16 Thread Mike Perham
You are referring to the M1 plugin.  I'm referring to the M2 plugin.  Sorry for 
the mixup. 

-Original Message-
From: Nicolas De Loof [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 16, 2006 9:26 AM
To: Maven Users List
Subject: Re: cobertura plugin


I'm using maven-cobertura-plugin from [EMAIL PROTECTED] As this site uses CVS, 
this seems you've in mind another cobertura plugin. Where to find it ?

Mike Perham a écrit :

The plugin code in SVN already uses 1.7.  It's never been released so 
you must be using an old version you compiled.  Update svn and 
recompile it.

-Original Message-
From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 16, 2006 8:36 AM
To: Maven Users List
Subject: cobertura plugin


Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

I'm using AspectJ and JiBX that both operate on bytecode and are not 
compatible with cobertura 1.6 instrumentation (plugin fails)

Upgrading dependency to 1.7 solves this problem

I've created
http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_
i
d=61626atid=497853
for this.

Nico.

This message contains information that may be privileged or 
confidential and is the property of the Capgemini Group. It is intended 
only for the person to whom it is addressed. If you are not the 
intended recipient, you are not authorized to read, print, retain, 
copy, disseminate, distribute, or use this message or any part thereof. 
If you receive this message in error, please notify the sender 
immediately and delete all copies of this message.


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


  


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


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



Re: cobertura plugin

2006-02-16 Thread Carlos Sanchez
A snapshot has been deployed at
http://maven-plugins.sourceforge.net/snapshot-repository/maven-plugins/plugins/

Please test it and we can make a new release

On 2/16/06, Nicolas De Loof [EMAIL PROTECTED] wrote:

 Is there any plan to upgrade cobertura plugin to use cobertura 1.7 ?

 I'm using AspectJ and JiBX that both operate on bytecode and are not
 compatible with cobertura 1.6 instrumentation (plugin fails)

 Upgrading dependency to 1.7 solves this problem

 I've created
 http://sourceforge.net/tracker/index.php?func=detailaid=1432911group_id=61626atid=497853
 for this.

 Nico.

 This message contains information that may be privileged or confidential and 
 is the property of the Capgemini Group. It is intended only for the person to 
 whom it is addressed. If you are not the intended recipient,  you are not 
 authorized to read, print, retain, copy, disseminate,  distribute, or use 
 this message or any part thereof. If you receive this  message in error, 
 please notify the sender immediately and delete all  copies of this message.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
 -- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: cobertura plugin breaks with maven 2.02 - wors fine with 2.0

2006-01-26 Thread Nigel Magnay
You need to svn-update the cobertura mojo and rebuild it - the bug has been
fixed for 2.0.2.,..


On 26/01/06, David Sag [EMAIL PROTECTED] wrote:


 I have just updated my maven 2 to 2.0.2 and now the instrumentation of my
 classes fails when using the cobertura plugin.

 I get NoClassDefFoundError: org/apache/maven/wagon/util/FileUtils

 any clues as to what changed between 2.0 and 2.0.2 that would lead to this
 error?

 most frustrating

 Kind regards,
 Dave Sag







Re: cobertura plugin breaks with maven 2.02 - wors fine with 2.0

2006-01-26 Thread Jason van Zyl

Nigel Magnay wrote:

You need to svn-update the cobertura mojo and rebuild it - the bug has been
fixed for 2.0.2.,..


I'll ping the current fellow working on the plugin and see if he can do 
a release.




On 26/01/06, David Sag [EMAIL PROTECTED] wrote:


I have just updated my maven 2 to 2.0.2 and now the instrumentation of my
classes fails when using the cobertura plugin.

I get NoClassDefFoundError: org/apache/maven/wagon/util/FileUtils

any clues as to what changed between 2.0 and 2.0.2 that would lead to this
error?

most frustrating

Kind regards,
Dave Sag










--

jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole

 -- Christopher Alexander

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]