[jira] (MDEPLOY-195) deploy:deploy will try to deploy a nonexistent attached file (and succeed, depending on the repository)

[ https://jira.codehaus.org/browse/MDEPLOY-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365886#comment-365886 ] Peter Janes commented on MDEPLOY-195: - Since they're both hosted here, can you move the issue

[jira] (MDEPLOY-195) deploy:deploy will try to deploy a nonexistent attached file (and succeed, depending on the repository)

Peter Janes created MDEPLOY-195: --- Summary: deploy:deploy will try to deploy a nonexistent attached file (and succeed, depending on the repository) Key: MDEPLOY-195 URL: https://jira.codehaus.org/browse/MDEPLOY-195

[jira] (MNG-5510) Maven causing ClassCastException with container plugins when project is using other SLF4J implementation than slf4j-simple

[ https://jira.codehaus.org/browse/MNG-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361470#comment-361470 ] Peter Janes commented on MNG-5510: -- The SonarQube occurrence of this issue mentioned in the second c

[jira] (MCHECKSTYLE-144) If 'src/main/java' does not exist in a project then checkstyle skips the other source folders of the project

[ https://jira.codehaus.org/browse/MCHECKSTYLE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318019#comment-318019 ] Peter Janes commented on MCHECKSTYLE-144: - MCHECKSTYLE-185 (which I guess is a duplica

[jira] (MCHECKSTYLE-185) Empty checkstyle-results.xml in a tests-only project

Peter Janes created MCHECKSTYLE-185: --- Summary: Empty checkstyle-results.xml in a tests-only project Key: MCHECKSTYLE-185 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-185 Project: Maven 2.x Check

[jira] (MCHANGES-291) Cannot authenticate to Jira OnDemand

[ https://jira.codehaus.org/browse/MCHANGES-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MCHANGES-291: - Attachment: MCHANGES-291.patch Using the current (2.9-SNAPSHOT) trunk I can authenticate successfull

[jira] (MDEP-366) NPE when running site

[ https://jira.codehaus.org/browse/MDEP-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MDEP-366: - Attachment: mdep-366.patch Looks like the project variable was set as a Parameter in AnalyzeReportMojo.java ins

[jira] (MDEP-366) NPE when running site

[ https://jira.codehaus.org/browse/MDEP-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MDEP-366: - Attachment: mdep-366-it.patch Here's an IT that triggers the bug (for some reason the project variable is null

[jira] Created: (MEV-659) Snapshot Clover artifact directories on repo1

Snapshot Clover artifact directories on repo1 - Key: MEV-659 URL: http://jira.codehaus.org/browse/MEV-659 Project: Maven Evangelism Issue Type: Bug Components: Invalid Metadata

[jira] Commented: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent

[ http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214507#action_214507 ] Peter Janes commented on MRELEASE-317: -- The attached patch is still clean when applied to eith

[jira] Commented: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

[ http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208814#action_208814 ] Peter Janes commented on MRELEASE-458: -- updateWorkingCopyVersions=false appears to work again

[jira] Commented: (MJAVADOC-265) Generate a combined javadoc using all dependency source jars.

[ http://jira.codehaus.org/browse/MJAVADOC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202554#action_202554 ] Peter Janes commented on MJAVADOC-265: -- I've been using maven-dependency-plugin and maven-java

[jira] Updated: (MPIR-132) Dependency report fails on system-scope dependencies

[ http://jira.codehaus.org/browse/MPIR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MPIR-132: - Attachment: MPIR-132-test.patch I can't duplicate the problem either (although it's happened to someone else her

[jira] Commented: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

[ http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188842#action_188842 ] Peter Janes commented on MRELEASE-458: -- It's also present in 2.0-beta-9 running under Maven 2.

[jira] Created: (MAVENUPLOAD-2555) Uploading proguard 4.4 to the central repository

Uploading proguard 4.4 to the central repository Key: MAVENUPLOAD-2555 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2555 Project: Maven Upload Requests Issue Type: Wish Reporte

[jira] Closed: (MAVENUPLOAD-2554) Uploading proguard 4.4 to The Central Repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes closed MAVENUPLOAD-2554. Resolution: Fixed Sorry, I thought clone would allow me to edit the issue before it was su

[jira] Created: (MAVENUPLOAD-2554) Uploading proguard 4.4 to The Central Repository

Uploading proguard 4.4 to The Central Repository Key: MAVENUPLOAD-2554 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2554 Project: Maven Upload Requests Issue Type: Wish Reporte

[jira] Updated: (MRESOURCES-77) Filters for copy-resources goal in plugin configuration section are ignored

[ http://jira.codehaus.org/browse/MRESOURCES-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MRESOURCES-77: -- Attachment: MRESOURCES-77.patch This is a new patch (with test cases, basically combining the conf

[jira] Updated: (SCM-418) Support for Perforce changelogs in Continuum and changelog plugin

[ http://jira.codehaus.org/browse/SCM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated SCM-418: Attachment: scm-418-against-769975.patch New patch against current trunk > Support for Perforce changelogs in Conti

[jira] Updated: (SCM-418) Support for Perforce changelogs in Continuum and changelog plugin

[ http://jira.codehaus.org/browse/SCM-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated SCM-418: Attachment: scm-418.patch Patch against current trunk > Support for Perforce changelogs in Continuum and changelog

[jira] Commented: (WAGON-228) role hint: 'scpexe' has a hint, but there are other implementations that don't

[ http://jira.codehaus.org/browse/WAGON-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168231#action_168231 ] Peter Janes commented on WAGON-228: --- I've just updated to Maven 2.0.10 and still see this error with

[jira] Commented: (SUREFIRE-524) Forked Process not terminated if maven process aborted. Provide means to clean up.

[ http://jira.codehaus.org/browse/SUREFIRE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167892#action_167892 ] Peter Janes commented on SUREFIRE-524: -- Another option might be to use (something like) the Pr

[jira] Updated: (MCOMPILER-91) source and output directories should be configurable

[ http://jira.codehaus.org/browse/MCOMPILER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MCOMPILER-91: - Attachment: maven-compiler-plugin.patch The updated patch includes a test case for the new configurat

[jira] Issue Comment Edited: (SUREFIRE-413) Ctrl-C during tests won't kill forked subprocesses

[ http://jira.codehaus.org/browse/SUREFIRE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165528#action_165528 ] Peter Janes edited comment on SUREFIRE-413 at 2/13/09 1:42 PM: --- The s

[jira] Commented: (SUREFIRE-413) Ctrl-C during tests won't kill forked subprocesses

[ http://jira.codehaus.org/browse/SUREFIRE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165528#action_165528 ] Peter Janes commented on SUREFIRE-413: -- The same thing happens if the test times out. > Ctrl-

[jira] Updated: (MCOMPILER-91) source and output directories should be configurable

[ http://jira.codehaus.org/browse/MCOMPILER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MCOMPILER-91: - Attachment: maven-compiler-plugin.patch I have a similar need for test trees (separating strict unit

[jira] Created: (SCM-418) Support for Perforce changelogs in Continuum and changelog plugin

Support for Perforce changelogs in Continuum and changelog plugin - Key: SCM-418 URL: http://jira.codehaus.org/browse/SCM-418 Project: Maven SCM Issue Type: Bug Compon

[jira] Commented: (SCM-414) Patch Submisson Fix Maven Perforce SCM Plugin so that it will work with Continuum

[ http://jira.codehaus.org/browse/SCM-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149419#action_149419 ] Peter Janes commented on SCM-414: - Apologies, I was reading the patch in isolation from the report. The

[jira] Updated: (SCM-414) Patch Submisson Fix Maven Perforce SCM Plugin so that it will work with Continuum

[ http://jira.codehaus.org/browse/SCM-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated SCM-414: Attachment: scm-414.patch The previous patch touched more files than necessary. I've reduced it to only the single

[jira] Created: (SCM-417) PerforceDiffCommand uses "head" instead of "now" pseudo-revision

PerforceDiffCommand uses "head" instead of "now" pseudo-revision Key: SCM-417 URL: http://jira.codehaus.org/browse/SCM-417 Project: Maven SCM Issue Type: Bug Componen

[jira] Created: (SCM-416) Backslashes in Perforce clientspec name should be replaced

Backslashes in Perforce clientspec name should be replaced -- Key: SCM-416 URL: http://jira.codehaus.org/browse/SCM-416 Project: Maven SCM Issue Type: Bug Components: maven-sc

[jira] Updated: (SCM-415) 1.1 requires setting a Perforce password breaking Perforce setup for external authentication

[ http://jira.codehaus.org/browse/SCM-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated SCM-415: Attachment: scm-415.patch Alternative patch that logs an info message when no password is set and attempts to conti

[jira] Issue Comment Edited: (SCM-246) p4 command reports most or all errors on stderr but maven-scm-provider-perforce throws away stderr

[ http://jira.codehaus.org/browse/SCM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149021#action_149021 ] peterj edited comment on SCM-246 at 9/25/08 3:58 PM: -- scm-246.patch restores th

[jira] Updated: (SCM-246) p4 command reports most or all errors on stderr but maven-scm-provider-perforce throws away stderr

[ http://jira.codehaus.org/browse/SCM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated SCM-246: Attachment: scm-246.patch Restores input streams to commands that need it. > p4 command reports most or all errors

[jira] Commented: (SCM-246) p4 command reports most or all errors on stderr but maven-scm-provider-perforce throws away stderr

[ http://jira.codehaus.org/browse/SCM-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149018#action_149018 ] Peter Janes commented on SCM-246: - r691823 broke commands which use a "form" provided from stdin, i.e.

[jira] Commented: (SCM-332) Perforce provider give one changeset entry for each file

[ http://jira.codehaus.org/browse/SCM-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148895#action_148895 ] Peter Janes commented on SCM-332: - I understand from SCM-155 that there isn't a Perforce server to test

[jira] Commented: (SCM-349) The and parameters appear not to work with a StarTeam scm:checkout

[ http://jira.codehaus.org/browse/SCM-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148894#action_148894 ] Peter Janes commented on SCM-349: - Same for the perforce provider. > The and parameters appear not to

[jira] Created: (MINVOKER-51) NPE when packaging is pom

NPE when packaging is pom - Key: MINVOKER-51 URL: http://jira.codehaus.org/browse/MINVOKER-51 Project: Maven 2.x Invoker Plugin Issue Type: Bug Affects Versions: 1.2.1 Environment: Linux x86_64, Java 1.6,

[jira] Commented: (MJAVADOC-200) Exception creating report - slash/backslash problem

[ http://jira.codehaus.org/browse/MJAVADOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142631#action_142631 ] Peter Janes commented on MJAVADOC-200: -- Without JAVA_HOME in the CLASSPATH, the reporting is n

[jira] Updated: (MJAVADOC-200) Exception creating report - slash/backslash problem

[ http://jira.codehaus.org/browse/MJAVADOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MJAVADOC-200: - Attachment: packages options javadoc.bat Thanks for your support; my

[jira] Updated: (MJAVADOC-200) Exception creating report - slash/backslash problem

[ http://jira.codehaus.org/browse/MJAVADOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MJAVADOC-200: - Attachment: env.log > Exception creating report - slash/backslash problem > -

[jira] Updated: (MJAVADOC-200) Exception creating report - slash/backslash problem

[ http://jira.codehaus.org/browse/MJAVADOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Janes updated MJAVADOC-200: - Attachment: log2.log log.log log.log: Log file of mvn clean site -X -e > log.log (lon

[jira] Commented: (MJAVADOC-200) Exception creating report - slash/backslash problem

[ http://jira.codehaus.org/browse/MJAVADOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142467#action_142467 ] Peter Janes commented on MJAVADOC-200: -- First of all, thanks for the quick turn around time. S

[jira] Created: (MSITE-344) Exception creating report - slash/backslash problem

Exception creating report - slash/backslash problem --- Key: MSITE-344 URL: http://jira.codehaus.org/browse/MSITE-344 Project: Maven 2.x Site Plugin Issue Type: Bug Environment: Window

[jira] Created: (SUREFIRE-485) Support AntUnit XML output

Support AntUnit XML output -- Key: SUREFIRE-485 URL: http://jira.codehaus.org/browse/SUREFIRE-485 Project: Maven Surefire Issue Type: Improvement Components: report plugin Affects Versions: 2.4.2