[jira] Commented: (MSUREFIRE-64) Old syntax for specifying system properties should still be supported

[ http://jira.codehaus.org/browse/MSUREFIRE-64?page=comments#action_59880 ] Vincent Massol commented on MSUREFIRE-64: - Actually I don't think we any other choice to move to a new syntax. We need a deprecation period when the 2 syntaxes are

[jira] Created: (MSUREFIRE-63) Surefire temporary files should be put in target rather than in the main project directory

Surefire temporary files should be put in target rather than in the main project directory -- Key: MSUREFIRE-63 URL: http://jira.codehaus.org/browse/MSUREFIRE-63 Project: Maven 2.x

[jira] Updated: (MSUREFIRE-63) Surefire temporary files should be put in target rather than in the main project directory

[ http://jira.codehaus.org/browse/MSUREFIRE-63?page=all ] Vincent Massol updated MSUREFIRE-63: Priority: Minor (was: Major) Surefire temporary files should be put in target rather than in the main project directory

[jira] Created: (MSUREFIRE-64) Old syntax for specifying system properties should still be supported

Old syntax for specifying system properties should still be supported - Key: MSUREFIRE-64 URL: http://jira.codehaus.org/browse/MSUREFIRE-64 Project: Maven 2.x Surefire Plugin Type: Bug

[jira] Commented: (MSUREFIRE-64) Old syntax for specifying system properties should still be supported

[ http://jira.codehaus.org/browse/MSUREFIRE-64?page=comments#action_59866 ] Vincent Massol commented on MSUREFIRE-64: - Dan, as I mentioned in the description of this issue, have you kept the new way of defining properties? I think it's much better

[jira] Commented: (MSUREFIRE-35) Improved errors in console

[ http://jira.codehaus.org/browse/MSUREFIRE-35?page=comments#action_58719 ] Vincent Massol commented on MSUREFIRE-35: - Just tried again today on a different project and got: {code} C:\dev\m2book\code\j2ee\daytrader\functional-testsmvn clean install

[jira] Updated: (MNG-2035) Add transitive dependencies with test scope when depending on a test-jar type dependency

[ http://jira.codehaus.org/browse/MNG-2035?page=all ] Vincent Massol updated MNG-2035: Comment: was deleted Add transitive dependencies with test scope when depending on a test-jar type dependency

[jira] Commented: (MCHECKSTYLE-27) checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency

[ http://jira.codehaus.org/browse/MCHECKSTYLE-27?page=comments#action_57564 ] Vincent Massol commented on MCHECKSTYLE-27: --- I just wanted to say that I have tried it again with checkstyle plugin v2.0 and it's not working any better

[jira] Updated: (MCHECKSTYLE-27) checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency

[ http://jira.codehaus.org/browse/MCHECKSTYLE-27?page=all ] Vincent Massol updated MCHECKSTYLE-27: -- Description: Here's the config I have: {code:xml} build plugins plugin artifactIdmaven-checkstyle-plugin/artifactId

[jira] Updated: (MCHECKSTYLE-27) checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency

[ http://jira.codehaus.org/browse/MCHECKSTYLE-27?page=all ] Vincent Massol updated MCHECKSTYLE-27: -- Description: Here's the config I have: {code:xml} build plugins plugin artifactIdmaven-checkstyle-plugin/artifactId

[jira] Commented: (MPCLOVER-53) Use new clover license as the old one is exiring on 30th of Jan 2006

[ http://jira.codehaus.org/browse/MPCLOVER-53?page=comments#action_57308 ] Vincent Massol commented on MPCLOVER-53: It's not released. You can build it from SVN or wait till it is released. If the only thing you need is the license, I remind you

[jira] Created: (MSUREFIRE-50) Create new surefire:integration-test mojo for IT

Create new surefire:integration-test mojo for IT Key: MSUREFIRE-50 URL: http://jira.codehaus.org/browse/MSUREFIRE-50 Project: Maven 2.x Surefire Plugin Type: Task Versions: 2.1.1 Reporter: Vincent Massol

[jira] Created: (MNG-2009) Add new integrationTestSourceDirectory element in the POM model

Add new integrationTestSourceDirectory element in the POM model - Key: MNG-2009 URL: http://jira.codehaus.org/browse/MNG-2009 Project: Maven 2 Type: Task Components: POM Reporter: Vincent

[jira] Created: (MNG-2010) Add new lifecycle phases for IT

Add new lifecycle phases for IT --- Key: MNG-2010 URL: http://jira.codehaus.org/browse/MNG-2010 Project: Maven 2 Type: Task Components: Plugins and Lifecycle, integration tests Reporter: Vincent Massol Namely: *

[jira] Created: (MNG-2011) Add new integration-test scope for dependencies

Add new integration-test scope for dependencies --- Key: MNG-2011 URL: http://jira.codehaus.org/browse/MNG-2011 Project: Maven 2 Type: Task Components: Plugins and Lifecycle, integration tests Reporter: Vincent

[jira] Commented: (MCLOVER-19) Document clover build integration

[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56459 ] Vincent Massol commented on MCLOVER-19: --- I'm not sure what you mean does not perform the install process. Do you mean that the install phase is not called? That would be normal

[jira] Commented: (MCLOVER-19) Document clover build integration

[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56465 ] Vincent Massol commented on MCLOVER-19: --- It seems like CloverReportMojo could be broken into two goals, one being a really simple goal to use an existing database and a second

[jira] Updated: (MCLOVER-19) Separate report generation database generation

[ http://jira.codehaus.org/browse/MCLOVER-19?page=all ] Vincent Massol updated MCLOVER-19: -- Assign To: Vincent Massol (was: Mike Perham) Summary: Separate report generation database generation (was: Enable clover build integration) Separate

[jira] Commented: (MCLOVER-19) Separate report generation database generation

[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56472 ] Vincent Massol commented on MCLOVER-19: --- oh ok. I misunderstood. I didn't realize you wanted to implement it! That's cool with me :-) Separate report generation database

[jira] Commented: (MCLOVER-19) Separate report generation database generation

[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56478 ] Vincent Massol commented on MCLOVER-19: --- Mike, I'm now watching but I don't have too much time right now. I'll try to help you over the week end but I'm awfully busy with other

[jira] Created: (MPA-41) Setup sync with objectweb m1 and m2 repositories

Setup sync with objectweb m1 and m2 repositories Key: MPA-41 URL: http://jira.codehaus.org/browse/MPA-41 Project: Maven Project Administration Type: Task Components: repository management Reporter: Vincent

[jira] Commented: (MPA-41) Setup sync with objectweb m1 and m2 repositories

[ http://jira.codehaus.org/browse/MPA-41?page=comments#action_56501 ] Vincent Massol commented on MPA-41: --- Note that their m1 repo has changed location (see the description) above. Setup sync with objectweb m1 and m2 repositories

[jira] Commented: (MCLOVER-16) Using Clover with projects that require class post-processing

[ http://jira.codehaus.org/browse/MCLOVER-16?page=comments#action_56216 ] Vincent Massol commented on MCLOVER-16: --- Mike, it seems this was caused by a bug elsewhere (see MNG-1927). Could you please try it again with Maven 2.0.2 or later and tell me if

[jira] Closed: (MCLOVER-16) Using Clover with projects that require class post-processing

[ http://jira.codehaus.org/browse/MCLOVER-16?page=all ] Vincent Massol closed MCLOVER-16: - Resolution: Won't Fix This was not a bug in the Clover plugin but a bug in Maven, see MNG-1927. Using Clover with projects that require class

[jira] Commented: (MNG-1922) Rename maven-it-plugin plugin as its name implies it is for performing integration tests in general

[ http://jira.codehaus.org/browse/MNG-1922?page=comments#action_55852 ] Vincent Massol commented on MNG-1922: - Hi Kenney, Apologies if I'm wrong but I thought the it plugin's goal was to execute Maven2 projects and I can't think of a use case different

[jira] Created: (MNG-1952) Give equal footing to all m2 plugins and add Cargo plugin to the list

Give equal footing to all m2 plugins and add Cargo plugin to the list - Key: MNG-1952 URL: http://jira.codehaus.org/browse/MNG-1952 Project: Maven 2 Type: Improvement Components: documentation -

[jira] Updated: (MNG-1952) Give equal footing to all m2 plugins and add Cargo plugin to the list

[ http://jira.codehaus.org/browse/MNG-1952?page=all ] Vincent Massol updated MNG-1952: Attachment: (was: siteplugin.patch) Give equal footing to all m2 plugins and add Cargo plugin to the list

[jira] Updated: (MNG-1952) Give equal footing to all m2 plugins and add Cargo plugin to the list

[ http://jira.codehaus.org/browse/MNG-1952?page=all ] Vincent Massol updated MNG-1952: Attachment: siteplugin2.patch Give equal footing to all m2 plugins and add Cargo plugin to the list

[jira] Commented: (MCLOVER-16) Using Clover with projects that require class post-processing

[ http://jira.codehaus.org/browse/MCLOVER-16?page=comments#action_55221 ] Vincent Massol commented on MCLOVER-16: --- Hi Mike, I think I know what's the problem... Clover does not instrument classes. It generates source classes in target/clover/src and

[jira] Created: (MNG-1945) project.getBuild().setSourceDirectory() should modify the compile source roots automatically

project.getBuild().setSourceDirectory() should modify the compile source roots automatically Key: MNG-1945 URL: http://jira.codehaus.org/browse/MNG-1945 Project: Maven 2

[jira] Commented: (MNG-1945) project.getBuild().setSourceDirectory() should modify the compile source roots automatically

[ http://jira.codehaus.org/browse/MNG-1945?page=comments#action_55224 ] Vincent Massol commented on MNG-1945: - err.. the correct code is: private void redirectSourceDirectories() { String oldSourceDirectory =

[jira] Commented: (MCLOVER-16) Using Clover with projects that require class post-processing

[ http://jira.codehaus.org/browse/MCLOVER-16?page=comments#action_55225 ] Vincent Massol commented on MCLOVER-16: --- Mike, I think I have fixed it in svn trunk. if you can could you please rebuild the clover plugin and verify if it works. I'll need to

[jira] Created: (MNG-1922) Renamed maven-it-plugin plugin as its name implies it is for performing integration tests in general

Renamed maven-it-plugin plugin as its name implies it is for performing integration tests in general Key: MNG-1922 URL: http://jira.codehaus.org/browse/MNG-1922 Project:

[jira] Updated: (MNG-1922) Rename maven-it-plugin plugin as its name implies it is for performing integration tests in general

[ http://jira.codehaus.org/browse/MNG-1922?page=all ] Vincent Massol updated MNG-1922: Summary: Rename maven-it-plugin plugin as its name implies it is for performing integration tests in general (was: Renamed maven-it-plugin plugin as its name

[jira] Created: (MCLOVER-17) Use new clover license as the old one is exiring on 30th of Jan 2006

Use new clover license as the old one is exiring on 30th of Jan 2006 Key: MCLOVER-17 URL: http://jira.codehaus.org/browse/MCLOVER-17 Project: Maven 2.x Clover Plugin Type: Task Reporter:

[jira] Closed: (MCLOVER-17) Use new clover license as the old one is exiring on 30th of Jan 2006

[ http://jira.codehaus.org/browse/MCLOVER-17?page=all ] Vincent Massol closed MCLOVER-17: - Resolution: Fixed Upgraded to new license valid till 30 jan 2007. Use new clover license as the old one is exiring on 30th of Jan 2006

[jira] Created: (MPCLOVER-53) Use new clover license as the old one is exiring on 30th of Jan 2006

Use new clover license as the old one is exiring on 30th of Jan 2006 Key: MPCLOVER-53 URL: http://jira.codehaus.org/browse/MPCLOVER-53 Project: maven-clover-plugin Type: Task Reporter: Vincent

[jira] Created: (MNG-1914) Wrong error message when using a mirror

Wrong error message when using a mirror --- Key: MNG-1914 URL: http://jira.codehaus.org/browse/MNG-1914 Project: Maven 2 Type: Bug Versions: 2.0.1 Reporter: Vincent Massol I had the following in my settings.xml:

[jira] Created: (MCHECKSTYLE-27) checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency

checktyle:check does not use custom checkstyle xml files when used in a multiproject mode with a build-tools project passed as a plugin dependency --

[jira] Created: (MCLEAN-3) mvn clean tries to download dependencies

mvn clean tries to download dependencies -- Key: MCLEAN-3 URL: http://jira.codehaus.org/browse/MCLEAN-3 Project: Maven 2.x Clean Plugin Type: Bug Environment: 2.1-SNAPSHOT Reporter: Vincent Massol

[jira] Commented: (MCLEAN-3) mvn clean tries to download dependencies

[ http://jira.codehaus.org/browse/MCLEAN-3?page=comments#action_54513 ] Vincent Massol commented on MCLEAN-3: - Actually i have the same problem with mvn install and it's definitely due to the extension (removing it makes the build work). mvn clean

[jira] Updated: (MCLEAN-3) cannot build and use a build extension in the same build run

[ http://jira.codehaus.org/browse/MCLEAN-3?page=all ] Vincent Massol updated MCLEAN-3: Description: C:\dev\cargo\branches\0.7mvn clean [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Cargo [INFO] Cargo Build Tools [INFO] Cargo

[jira] Moved: (MNG-1904) cannot build and use a build extension in the same build run

[ http://jira.codehaus.org/browse/MNG-1904?page=all ] Vincent Massol moved MCLEAN-3 to MNG-1904: -- Complexity: Intermediate Key: MNG-1904 (was: MCLEAN-3) Project: Maven 2 (was: Maven 2.x Clean Plugin) cannot build and use a

[jira] Created: (MCHECKSTYLE-25) Do not execute checkstyle when the project has no sources

Do not execute checkstyle when the project has no sources - Key: MCHECKSTYLE-25 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-25 Project: Maven 2.x Checkstyle Plugin Type: Improvement Versions:

[jira] Commented: (MCHECKSTYLE-25) Do not execute checkstyle when the project has no sources

[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54557 ] Vincent Massol commented on MCHECKSTYLE-25: --- Hi Fabrizio, I'm using what's in svn trunk which is *supposed* to be the latets. I've just learnt from Brett that trunk is

[jira] Reopened: (MCHECKSTYLE-25) Do not execute checkstyle when the project has no sources

[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=all ] Vincent Massol reopened MCHECKSTYLE-25: --- Assign To: fabrizio giustina (was: Brett Porter) Reopening as Fabrizio has confirmed it's not a dupliate and a real issue. i'll edit the

[jira] Updated: (MCHECKSTYLE-25) Do not execute checkstyle when the project has no sources and when checkstyle is triggered through checkstyle:check

[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=all ] Vincent Massol updated MCHECKSTYLE-25: -- Summary: Do not execute checkstyle when the project has no sources and when checkstyle is triggered through checkstyle:check (was: Do not execute

[jira] Commented: (MCHECKSTYLE-25) Do not execute checkstyle when the project has no sources and when checkstyle is triggered through checkstyle:check

[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54565 ] Vincent Massol commented on MCHECKSTYLE-25: --- Hi Fabrizio, Thanks for fixing this! It's better but there's still an issue: C:\dev\cargo\trunk\coremvn clean install

[jira] Created: (MCHECKSTYLE-26) checkstyle:check fails when the project has no sources

checkstyle:check fails when the project has no sources --- Key: MCHECKSTYLE-26 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-26 Project: Maven 2.x Checkstyle Plugin Type: Bug Reporter: Vincent Massol See

[jira] Commented: (MCHECKSTYLE-25) Do not execute checkstyle when the project has no sources and when checkstyle is triggered through checkstyle:check

[ http://jira.codehaus.org/browse/MCHECKSTYLE-25?page=comments#action_54577 ] Vincent Massol commented on MCHECKSTYLE-25: --- I've opened a new (but related) issue: MCHECKSTYLE-26 Do not execute checkstyle when the project has no sources and when

[jira] Commented: (MCLOVER-16) Using Clover with projects that require class post-processing

[ http://jira.codehaus.org/browse/MCLOVER-16?page=comments#action_54476 ] Vincent Massol commented on MCLOVER-16: --- version 2.0 is not released yet. I stopped in mid-release due to a bug in the deploy plugin... Using Clover with projects that require

[jira] Created: (MSUREFIRE-37) Remove or fix strange battery = null messages displayed on the console

Remove or fix strange battery = null messages displayed on the console Key: MSUREFIRE-37 URL: http://jira.codehaus.org/browse/MSUREFIRE-37 Project: Maven 2.x Surefire Plugin Type: Bug

[jira] Commented: (MNG-1886) Need way to share code between report mojos and main build mojos

[ http://jira.codehaus.org/browse/MNG-1886?page=comments#action_54344 ] Vincent Massol commented on MNG-1886: - I'm talking about sharing configuration elements (fields). Here's an example: configuration cloverDatabase.../cloverDatabase jdk.../jdk

[jira] Commented: (MCLOVER-3) classpath error

[ http://jira.codehaus.org/browse/MCLOVER-3?page=comments#action_54250 ] Vincent Massol commented on MCLOVER-3: -- Hi YueNi, Ok I've played with your example. The problem is that it's not correct. You're putting a resource file in src/main/java whereas

[jira] Closed: (MCLOVER-3) classpath error

[ http://jira.codehaus.org/browse/MCLOVER-3?page=all ] Vincent Massol closed MCLOVER-3: Resolution: Won't Fix Yue, This is not an issue of using an IDE or not. It probably works within Eclipse because your eclipse project compiles the project

[jira] Created: (MRELEASE-63) Error when trying release:prepare a second time

Error when trying release:prepare a second time --- Key: MRELEASE-63 URL: http://jira.codehaus.org/browse/MRELEASE-63 Project: Maven 2.x Release Plugin Type: Bug Environment: 2.1-snapshot (note: the build number is still

[jira] Created: (MRELEASE-64) prerequisites are stripped on release:prepare

prerequisites are stripped on release:prepare --- Key: MRELEASE-64 URL: http://jira.codehaus.org/browse/MRELEASE-64 Project: Maven 2.x Release Plugin Type: Bug Reporter: Vincent Massol Assigned to: Jason van Zyl

[jira] Updated: (MRELEASE-64) prerequisites are stripped on release:prepare

[ http://jira.codehaus.org/browse/MRELEASE-64?page=all ] Vincent Massol updated MRELEASE-64: --- Description: {noformat} Author: vmassol Date: Mon Dec 26 00:42:18 2005 New Revision: 359040 URL: http://svn.apache.org/viewcvs?rev=359040view=rev Log:

[jira] Commented: (MNG-354) Add ability to select modules to build based on a configuration

[ http://jira.codehaus.org/browse/MNG-354?page=comments#action_54215 ] Vincent Massol commented on MNG-354: This issue was closed with a fixed status but I don't think it was ever implemented. The goal here is to be able to tell the build which module

[jira] Commented: (MNG-354) Add ability to select modules to build based on a configuration

[ http://jira.codehaus.org/browse/MNG-354?page=comments#action_54216 ] Vincent Massol commented on MNG-354: Ah forget that. I just re-read http://maven.apache.org/guides/introduction/introduction-to-profiles.html and I've seen that modules can be

[jira] Commented: (MCLOVER-3) classpath error

[ http://jira.codehaus.org/browse/MCLOVER-3?page=comments#action_54158 ] Vincent Massol commented on MCLOVER-3: -- Hi, I've tried to reproduce your problem but couldn't. What I've done is create a project where the tests are loading some resource files

[jira] Created: (MAVENUPLOAD-648) Clover 1.3.11

Clover 1.3.11 - Key: MAVENUPLOAD-648 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-648 Project: maven-upload-requests Type: Task Reporter: Vincent Massol -- This message is automatically generated by JIRA. - If you think it was sent

[jira] Created: (MPCLOVER-52) Upgrade to Clover 1.3.11

Upgrade to Clover 1.3.11 Key: MPCLOVER-52 URL: http://jira.codehaus.org/browse/MPCLOVER-52 Project: maven-clover-plugin Type: Task Versions: 1.10 Reporter: Vincent Massol Assigned to: Vincent Massol Fix For: 1.11 --

[jira] Created: (MCLOVER-15) Upgrade to Clover 1.3.11

Upgrade to Clover 1.3.11 Key: MCLOVER-15 URL: http://jira.codehaus.org/browse/MCLOVER-15 Project: Maven 2.x Clover Plugin Type: Task Reporter: Vincent Massol Assigned to: Vincent Massol Fix For: 2.0 -- This message is

[jira] Closed: (MCLOVER-15) Upgrade to Clover 1.3.11

[ http://jira.codehaus.org/browse/MCLOVER-15?page=all ] Vincent Massol closed MCLOVER-15: - Resolution: Fixed Done Upgrade to Clover 1.3.11 Key: MCLOVER-15 URL:

[jira] Updated: (MPA-36) associate Maven svn with JIRA projects

[ http://jira.codehaus.org/browse/MPA-36?page=all ] Vincent Massol updated MPA-36: -- Attachment: subversion-jira-plugin.properties associate Maven svn with JIRA projects -- Key: MPA-36 URL:

[jira] Created: (MSITE-59) mvn site fails when no site.xml

mvn site fails when no site.xml - Key: MSITE-59 URL: http://jira.codehaus.org/browse/MSITE-59 Project: Maven 2.x Site Plugin Type: Bug Environment: Maven 2.1-SNAPSHOT updated from 2005-12-23, ~17:00GMT+1 Reporter: Vincent Massol

[jira] Commented: (MSITE-59) mvn site fails when no site.xml

[ http://jira.codehaus.org/browse/MSITE-59?page=comments#action_54134 ] Vincent Massol commented on MSITE-59: - after some more investigation it seems the problem is not a missing site.xml. Even with a site.xml the project is failing with the same

[jira] Closed: (MCLOVER-5) Clover fails on multi-module builds

[ http://jira.codehaus.org/browse/MCLOVER-5?page=all ] Vincent Massol closed MCLOVER-5: Resolution: Fixed Fixed. Clover fails on multi-module builds --- Key: MCLOVER-5 URL:

[jira] Commented: (MSUREFIRE-20) forkMode=pertest fails to call setUp

[ http://jira.codehaus.org/browse/MSUREFIRE-20?page=comments#action_53908 ] Vincent Massol commented on MSUREFIRE-20: - I think I have the same issue in the Cargo tests. I need to verify but I'm not sure surefire's pertest is honoring the suite()

[jira] Updated: (MSUREFIRE-20) forkMode=pertest fails to call setUp

[ http://jira.codehaus.org/browse/MSUREFIRE-20?page=all ] Vincent Massol updated MSUREFIRE-20: Priority: Blocker (was: Major) forkMode=pertest fails to call setUp Key: MSUREFIRE-20 URL:

[jira] Created: (MSUREFIRE-35) Improved errors in console

Improved errors in console -- Key: MSUREFIRE-35 URL: http://jira.codehaus.org/browse/MSUREFIRE-35 Project: Maven 2.x Surefire Plugin Type: Improvement Reporter: Vincent Massol Assigned to: Jason van Zyl Here's what I get:

[jira] Created: (MNG-1883) it plugin not picking up the plugin being built (goes to the local repo instead)

it plugin not picking up the plugin being built (goes to the local repo instead) Key: MNG-1883 URL: http://jira.codehaus.org/browse/MNG-1883 Project: Maven 2 Type: Bug Components:

[jira] Updated: (MNG-1883) it plugin not picking up the plugin being built (goes to the local repo instead)

[ http://jira.codehaus.org/browse/MNG-1883?page=all ] Vincent Massol updated MNG-1883: Description: Try the following to reproduce the problem: - checkout the clover plugin - delete the clover plugin from your local - run mvn install on the clover

[jira] Created: (MCLOVER-14) Do not execute instrumentation if no sources are present

Do not execute instrumentation if no sources are present Key: MCLOVER-14 URL: http://jira.codehaus.org/browse/MCLOVER-14 Project: Maven 2.x Clover Plugin Type: Improvement Versions: 2.0-alpha-1

[jira] Closed: (MCLOVER-14) Do not execute instrumentation if no sources are present

[ http://jira.codehaus.org/browse/MCLOVER-14?page=all ] Vincent Massol closed MCLOVER-14: - Resolution: Fixed Done Do not execute instrumentation if no sources are present Key:

[jira] Closed: (MCLOVER-13) Check artifact language

[ http://jira.codehaus.org/browse/MCLOVER-13?page=all ] Vincent Massol closed MCLOVER-13: - Assign To: Vincent Massol Resolution: Fixed Applied thanks. Check artifact language --- Key: MCLOVER-13 URL:

[jira] Created: (MNG-1886) Need way to share code between report mojos and main build mojos

Need way to share code between report mojos and main build mojos Key: MNG-1886 URL: http://jira.codehaus.org/browse/MNG-1886 Project: Maven 2 Type: Improvement Components: Plugin API Versions:

[jira] Created: (MNG-1880) Add new pre and post phases to the integration-test phase

Add new pre and post phases to the integration-test phase - Key: MNG-1880 URL: http://jira.codehaus.org/browse/MNG-1880 Project: Maven 2 Type: Wish Components: Plugins and Lifecycle Versions: 2.0.1

[jira] Moved: (MSOURCES-1) No resources directory is present in the generated jar

[ http://jira.codehaus.org/browse/MSOURCES-1?page=all ] Vincent Massol moved MNG-1748 to MSOURCES-1: Component: (was: maven-sources-plugin) Workflow: jira (was: Maven) Key: MSOURCES-1 (was: MNG-1748) Project: Maven

[jira] Moved: (MRESOURCES-2) No such file or directory when resource targetdirectory contains ../ and target/classes does not exist.

[ http://jira.codehaus.org/browse/MRESOURCES-2?page=all ] Vincent Massol moved MNG-1345 to MRESOURCES-2: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-resources-plugin) Workflow: jira

[jira] Moved: (MRESOURCES-5) Proposal for improved resource filtering

[ http://jira.codehaus.org/browse/MRESOURCES-5?page=all ] Vincent Massol moved MNG-788 to MRESOURCES-5: - Version: (was: 2.0-beta-1) Fix Version: (was: 2.0-beta-2) Component: (was: maven-resources-plugin)

[jira] Moved: (MRESOURCES-6) When filtering, properties defined in projectproperties should be allowed as well.

[ http://jira.codehaus.org/browse/MRESOURCES-6?page=all ] Vincent Massol moved MNG-1194 to MRESOURCES-6: -- Fix Version: (was: 2.0.1) Component: (was: maven-resources-plugin) Workflow: jira (was: Maven) Key:

[jira] Updated: (MCLOVER-3) classpath error

[ http://jira.codehaus.org/browse/MCLOVER-3?page=all ] Vincent Massol updated MCLOVER-3: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin classpath error ---

[jira] Updated: (MCLOVER-4) clover:check fails, even though coverage is 100%

[ http://jira.codehaus.org/browse/MCLOVER-4?page=all ] Vincent Massol updated MCLOVER-4: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover:check fails, even though

[jira] Reopened: (MCLOVER-4) clover:check fails, even though coverage is 100%

[ http://jira.codehaus.org/browse/MCLOVER-4?page=all ] Vincent Massol reopened MCLOVER-4: -- Reopening to set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover:check fails, even though coverage is 100%

[jira] Closed: (MCLOVER-4) clover:check fails, even though coverage is 100%

[ http://jira.codehaus.org/browse/MCLOVER-4?page=all ] Vincent Massol closed MCLOVER-4: Resolution: Fixed Fixed again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover:check fails, even though coverage is 100%

[jira] Updated: (MCLOVER-1) clover has to be declared as project dependency to run clover:report

[ http://jira.codehaus.org/browse/MCLOVER-1?page=all ] Vincent Massol updated MCLOVER-1: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover has to be declared as

[jira] Reopened: (MCLOVER-1) clover has to be declared as project dependency to run clover:report

[ http://jira.codehaus.org/browse/MCLOVER-1?page=all ] Vincent Massol reopened MCLOVER-1: -- Reopen to set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover has to be declared as project dependency to run clover:report

[jira] Closed: (MCLOVER-1) clover has to be declared as project dependency to run clover:report

[ http://jira.codehaus.org/browse/MCLOVER-1?page=all ] Vincent Massol closed MCLOVER-1: Resolution: Fixed Fixed again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover has to be declared as project dependency to run

[jira] Reopened: (MCLOVER-6) change outputDirectory in reports to default to ${project.reporting.outputDirectory}

[ http://jira.codehaus.org/browse/MCLOVER-6?page=all ] Vincent Massol reopened MCLOVER-6: -- Reopen to set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin change outputDirectory in reports to default to

[jira] Updated: (MCLOVER-6) change outputDirectory in reports to default to ${project.reporting.outputDirectory}

[ http://jira.codehaus.org/browse/MCLOVER-6?page=all ] Vincent Massol updated MCLOVER-6: - Version: 2.0-alpha-1 Fix Version: 2.0 type: Improvement (was: Bug) set again versions after the jira move from Maven 2 to Maven 2.x Clover

[jira] Closed: (MCLOVER-6) change outputDirectory in reports to default to ${project.reporting.outputDirectory}

[ http://jira.codehaus.org/browse/MCLOVER-6?page=all ] Vincent Massol closed MCLOVER-6: Resolution: Fixed Fixed again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin change outputDirectory in reports to default to

[jira] Updated: (MCLOVER-2) clover breaks when encountering assert statements.

[ http://jira.codehaus.org/browse/MCLOVER-2?page=all ] Vincent Massol updated MCLOVER-2: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover breaks when encountering

[jira] Reopened: (MCLOVER-2) clover breaks when encountering assert statements.

[ http://jira.codehaus.org/browse/MCLOVER-2?page=all ] Vincent Massol reopened MCLOVER-2: -- Reopen to set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover breaks when encountering assert statements.

[jira] Closed: (MCLOVER-2) clover breaks when encountering assert statements.

[ http://jira.codehaus.org/browse/MCLOVER-2?page=all ] Vincent Massol closed MCLOVER-2: Resolution: Fixed Fixed again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover breaks when encountering assert statements.

[jira] Updated: (MCLOVER-7) mvn clover:report generates errors in tests that execute properly in mvn test

[ http://jira.codehaus.org/browse/MCLOVER-7?page=all ] Vincent Massol updated MCLOVER-7: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin mvn clover:report generates errors

[jira] Updated: (MCLOVER-5) Clover fails on multi-module builds

[ http://jira.codehaus.org/browse/MCLOVER-5?page=all ] Vincent Massol updated MCLOVER-5: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin Clover fails on multi-module builds

[jira] Updated: (MCLOVER-12) clover should generate a placeholder if project do not have test cases

[ http://jira.codehaus.org/browse/MCLOVER-12?page=all ] Vincent Massol updated MCLOVER-12: -- Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin clover should generate a

[jira] Reopened: (MCLOVER-8) Clover default target percentage too high - should be 0%

[ http://jira.codehaus.org/browse/MCLOVER-8?page=all ] Vincent Massol reopened MCLOVER-8: -- Reopen to set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin Clover default target percentage too high - should be 0%

  1   2   3   4   >