[jira] Created: (MSITE-190) Bad file name for external_classic.png in classic skin

Bad file name for external_classic.png in classic skin -- Key: MSITE-190 URL: http://jira.codehaus.org/browse/MSITE-190 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions:

[jira] Commented: (MSITE-190) Bad file name for external_classic.png in classic skin

[ http://jira.codehaus.org/browse/MSITE-190?page=comments#action_79328 ] J-C Walmetz commented on MSITE-190: --- There is probably the same bug with newwindow-classic.png. I suppose it should be newwindow.png > Bad file name for external_classic.

[jira] Commented: (MSITE-190) Bad file name for external_classic.png in classic skin

[ http://jira.codehaus.org/browse/MSITE-190?page=comments#action_79344 ] J-C Walmetz commented on MSITE-190: --- Issue is with the maven-changes-plugin. My changes.xml file contains the line In the report at the end of the issue, there is a smal

[jira] Created: (MSUREFIRE-178) Known bug should not break the build

Known bug should not break the build Key: MSUREFIRE-178 URL: http://jira.codehaus.org/browse/MSUREFIRE-178 Project: Maven 2.x Surefire Plugin Issue Type: Improvement Components: Junit 3.x suppor

[jira] Commented: (MSUREFIRE-170) Classpath in XML report is wrong

[ http://jira.codehaus.org/browse/MSUREFIRE-170?page=comments#action_80626 ] J-C Walmetz commented on MSUREFIRE-170: --- Properties written in the XML report are just a dump of the System.getProperties() executed after tests. It does not used

[jira] Updated: (MSUREFIREREP-22) Aggragated surefire report from modules

[ http://jira.codehaus.org/browse/MSUREFIREREP-22?page=all ] J-C Walmetz updated MSUREFIREREP-22: Attachment: patch2.patch First proposed patched does not works when I have more than 2 levels of modules. Patch2 corrects that issue > Aggragated sure

[jira] Updated: (MSUREFIRE-170) Classpath in XML report is wrong

[ http://jira.codehaus.org/browse/MSUREFIRE-170?page=all ] J-C Walmetz updated MSUREFIRE-170: -- Attachment: patch.patch Patch for surefire-api trunk. For Junit tests, the java.class.path system properties added in the XML report is a dump of the classlo

[jira] Created: (MASSEMBLY-251) NullPointer wehn using scope system in a dependencySet

NullPointer wehn using scope system in a dependencySet -- Key: MASSEMBLY-251 URL: http://jira.codehaus.org/browse/MASSEMBLY-251 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affect

[jira] Updated: (SCM-34) Add PVCS support

[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J-C Walmetz updated SCM-34: --- Attachment: maven-scm-provider-pvcs.zip I started to implement a plugin for PVCS. I use it with the release plugin. Ex

[jira] Commented: (SCM-34) Add PVCS support

[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89959 ] J-C Walmetz commented on SCM-34: I'll try to add some junit tests (not before one or two weeks). Problem is that tests uses a loc

[jira] Commented: (SCM-34) Add PVCS support

[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89962 ] J-C Walmetz commented on SCM-34: OK, I'll have a look to existing tests for Perforce for example. I suppose that the same problem

[jira] Commented: (SCM-34) Add PVCS support

[ http://jira.codehaus.org/browse/SCM-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90389 ] J-C Walmetz commented on SCM-34: Yes, i'll do so cleaning > Add PVCS support > > > Key: SCM-34 >

[jira] Created: (MEV-534) Dependencies of commons-logging should be optional

Dependencies of commons-logging should be optional -- Key: MEV-534 URL: http://jira.codehaus.org/browse/MEV-534 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM

[jira] Commented: (MEV-534) Dependencies of commons-logging should be optional

[ http://jira.codehaus.org/browse/MEV-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100700 ] J-C Walmetz commented on MEV-534: - Just a mistake in previous post log4j log4j

[jira] Commented: (MEV-534) Dependencies of commons-logging should be optional

[ http://jira.codehaus.org/browse/MEV-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100705 ] J-C Walmetz commented on MEV-534: - Yes that's a mistake, log4j should be optional too. That's purpose of common-loggings to be