[jira] Created: (MCLOVER-34) Generate Aggregated site reports on the first build run

Generate Aggregated site reports on the first build run --- Key: MCLOVER-34 URL: http://jira.codehaus.org/browse/MCLOVER-34 Project: Maven 2.x Clover Plugin Type: Bug Versions: 2.1 Reporter: Vincent Mas

[jira] Closed: (MCLOVER-25) Create aggregated report when Clover is executed in a multimodule build

[ http://jira.codehaus.org/browse/MCLOVER-25?page=all ] Vincent Massol closed MCLOVER-25: - Resolution: Fixed All implemented. Only issue is that the aggregated clover report requires that Clover dbs in modules exist. See MCLOVER-34. > Create aggre

[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: (was: 2.0-alpha-1) 2.0 Fix Version: (was: 2.1) > clover should generate a placeholder if project do not have test cases

[jira] Updated: (MCLOVER-20) Please add an option to save historical clover data

[ http://jira.codehaus.org/browse/MCLOVER-20?page=all ] Vincent Massol updated MCLOVER-20: -- Version: 2.0 > Please add an option to save historical clover data > --- > > Key: MCLOVER-20 >

[jira] Closed: (MCLOVER-26) dependencies omitted from classpath during clover compile

[ http://jira.codehaus.org/browse/MCLOVER-26?page=all ] Vincent Massol closed MCLOVER-26: - Resolution: Fixed Working fine here. Please reopen if you have an issue. > dependencies omitted from classpath during clover compile > --

[jira] Updated: (MNG-939) specify maven settings from command line

[ http://jira.codehaus.org/browse/MNG-939?page=all ] Renaud Julienne updated MNG-939: Attachment: MNG-939-maven-core.patch > specify maven settings from command line > > > Key: MNG-939 > URL: htt

[jira] Closed: (MCLOVER-32) Add support for aggregating functional tests results

[ http://jira.codehaus.org/browse/MCLOVER-32?page=all ] Vincent Massol closed MCLOVER-32: - Resolution: Fixed Fix Version: 2.1 Done > Add support for aggregating functional tests results > >

[jira] Created: (MSITE-113) generated-site no longer working

generated-site no longer working Key: MSITE-113 URL: http://jira.codehaus.org/browse/MSITE-113 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0-beta-5 Reporter: Brett Porter Fix For: 2.0-beta-5 the changes to

[jira] Commented: (MIDEA-41) Source attachments are maintained when running idea:idea

[ http://jira.codehaus.org/browse/MIDEA-41?page=comments#action_63128 ] Johann Reyes commented on MIDEA-41: --- It has been decided better than just keep the sources untouched, it'll be better if we keep the whole library untouched since the library can have

[jira] Closed: (MIDEA-47) Clean up Idea Sources

[ http://jira.codehaus.org/browse/MIDEA-47?page=all ] Johann Reyes closed MIDEA-47: - Resolution: Won't Fix > Clean up Idea Sources > - > > Key: MIDEA-47 > URL: http://jira.codehaus.org/browse/MIDEA-47 > Project

[jira] Commented: (MIDEA-47) Clean up Idea Sources

[ http://jira.codehaus.org/browse/MIDEA-47?page=comments#action_63127 ] Johann Reyes commented on MIDEA-47: --- Yes, It's a big patch and already out of dat. I'll close it. Initial thought was to start indenting the code as per maven style, but also rearrange

[jira] Closed: (MSUREFIRE-79) Docs for systemProperties on website are wrong

[ http://jira.codehaus.org/browse/MSUREFIRE-79?page=all ] Brett Porter closed MSUREFIRE-79: - Assign To: Brett Porter Resolution: Won't Fix Fix Version: (was: 2.2) the web site is correct - expanded properties are what are valid in 2.1

[jira] Created: (MINSTALL-18) Bad algorithm to decide if the main artifact is to be installed or not

Bad algorithm to decide if the main artifact is to be installed or not -- Key: MINSTALL-18 URL: http://jira.codehaus.org/browse/MINSTALL-18 Project: Maven 2.x Install Plugin Type: Bug Versions:

[jira] Closed: (MONE-1) building an m1 plugin inside the reactor doesn't include the plugin.jelly and properties files

[ http://jira.codehaus.org/browse/MONE-1?page=all ] Brett Porter closed MONE-1: --- Assign To: Brett Porter Resolution: Fixed Fix Version: 1.1 > building an m1 plugin inside the reactor doesn't include the plugin.jelly and > properties files > --

[jira] Created: (MONE-1) building an m1 plugin inside the reactor doesn't include the plugin.jelly and properties files

building an m1 plugin inside the reactor doesn't include the plugin.jelly and properties files -- Key: MONE-1 URL: http://jira.codehaus.org/browse/MONE-1 Project: Maven 2.x M1 Plugin

[jira] Updated: (MCHECKSTYLE-38) checsktyle:check seems to fail on warning too

[ http://jira.codehaus.org/browse/MCHECKSTYLE-38?page=all ] Brett Porter updated MCHECKSTYLE-38: Fix Version: 2.1 ok, that certainly could be considered a bug in its current state, and its not going to regress on someone (the worst is it will fail n

[jira] Commented: (MCHECKSTYLE-38) checsktyle:check seems to fail on warning too

[ http://jira.codehaus.org/browse/MCHECKSTYLE-38?page=comments#action_63122 ] Vincent Massol commented on MCHECKSTYLE-38: --- {quote} Is it unreasonable to fail on warnings? {quote} Yes it's unreasonable as this is not the behavior of checkstyle its

[jira] Closed: (MPMD-24) Check goals fail in multi-module builds

[ http://jira.codehaus.org/browse/MPMD-24?page=all ] Brett Porter closed MPMD-24: Assign To: Brett Porter Resolution: Fixed > Check goals fail in multi-module builds > --- > > Key: MPMD-24 > URL

[jira] Commented: (MCHECKSTYLE-38) checsktyle:check seems to fail on warning too

[ http://jira.codehaus.org/browse/MCHECKSTYLE-38?page=comments#action_63121 ] Brett Porter commented on MCHECKSTYLE-38: - since this was in a release version, I'm not going to change the pending RC which was already voted on. Is it unreasonable to f

[jira] Closed: (MPIR-42) use of POM artifactId for svn report creates issues when file layout doesn't match artifact names

[ http://jira.codehaus.org/browse/MPIR-42?page=all ] Brett Porter closed MPIR-42: Assign To: Brett Porter Resolution: Won't Fix the plugin shouldn't be smarter. It is using just as it should. The issue is the confusion caused by the core's append

[jira] Closed: (MSUREFIRE-89) add a property called test in settings override the

[ http://jira.codehaus.org/browse/MSUREFIRE-89?page=all ] Brett Porter closed MSUREFIRE-89: - Assign To: Brett Porter Resolution: Won't Fix yes, it's normal. I'm not sure it's a great thing to have happen, but its "by design". It would be a cor

[jira] Updated: (MSUREFIRE-87) Improve error stack trace when the error comes from the user's test code

[ http://jira.codehaus.org/browse/MSUREFIRE-87?page=all ] Brett Porter updated MSUREFIRE-87: -- Fix Version: 2.2 > Improve error stack trace when the error comes from the user's test code > -

[jira] Commented: (MIDEA-47) Clean up Idea Sources

[ http://jira.codehaus.org/browse/MIDEA-47?page=comments#action_63118 ] Brett Porter commented on MIDEA-47: --- this is a big patch to just apply (and its already out of date). It's not helped by the rearranging of elements and reformatting. Can you explain

[jira] Commented: (WAGONSSH-44) directoryPermissions is not repected when I deploy a POM

[ http://jira.codehaus.org/browse/WAGONSSH-44?page=comments#action_63117 ] Trustin Lee commented on WAGONSSH-44: - Thanks! :D > directoryPermissions is not repected when I deploy a POM > > >

[jira] Commented: (WAGONSSH-44) directoryPermissions is not repected when I deploy a POM

[ http://jira.codehaus.org/browse/WAGONSSH-44?page=comments#action_63116 ] Brett Porter commented on WAGONSSH-44: -- I was getting there! :) applied the second patch in r392495 > directoryPermissions is not repected when I deploy a POM > -

[jira] Commented: (WAGONSSH-44) directoryPermissions is not repected when I deploy a POM

[ http://jira.codehaus.org/browse/WAGONSSH-44?page=comments#action_63115 ] Trustin Lee commented on WAGONSSH-44: - Great. Then why don't you check in the second patch first so we can use scpexe meanwhile? > directoryPermissions is not repected when I de

[jira] Closed: (MNG-2134) Population problem when ${project.organization.name} is used in pom, e.g. in plugin configuration.

[ http://jira.codehaus.org/browse/MNG-2134?page=all ] Brett Porter closed MNG-2134: - Assign To: Brett Porter Resolution: Duplicate > Population problem when ${project.organization.name} is used in pom, e.g. in > plugin configuration. > ---

[jira] Commented: (WAGONSSH-44) directoryPermissions is not repected when I deploy a POM

[ http://jira.codehaus.org/browse/WAGONSSH-44?page=comments#action_63114 ] Brett Porter commented on WAGONSSH-44: -- I'd still like to investigate this some more for the wagon-ssh one. I don't understand the circumstances where C0664 doesn't work as it ha