[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MPMD-142. Resolution: Fixed Fix Version/s: 2.7.1 Fixed in [r1241358|http://svn.apache.org/viewvc?view=revision&revision=1241358]. > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka >Assignee: Dennis Lundberg > Fix For: 2.7.1 > > Attachments: testpom.xml > > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5239) Maven integration developers would like to be able to override the maven logging appender.
Paul Ryan created MNG-5239: -- Summary: Maven integration developers would like to be able to override the maven logging appender. Key: MNG-5239 URL: https://jira.codehaus.org/browse/MNG-5239 Project: Maven 2 & 3 Issue Type: Improvement Components: Logging Affects Versions: 2.2.1 Reporter: Paul Ryan Integrations with maven logging right now have to be down with primitive piping that loses context of the log. A greatly improved mechanism would be by allowing integration developers to control where and how logs are output and give an much improved integration capability. This could be achieved by exposing the logging configuration to the maven user (through a configuration file such as the log4j.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290953#comment-290953 ] Jan Ruzicka commented on MPMD-142: -- Thank you, the 2.7.1-SNAPSHOT worked without Exception. The biggest delay was fighting Nexus. > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka >Assignee: Dennis Lundberg > Attachments: testpom.xml > > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290948#comment-290948 ] Dennis Lundberg commented on MPMD-142: -- Please try the 2.7.1-SNAPSHOT that I just deployed. > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka >Assignee: Dennis Lundberg > Attachments: testpom.xml > > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290945#comment-290945 ] Dennis Lundberg commented on MPMD-142: -- Jan, thanks for the sample project. I've reproduced the problem locally and have a fix in the works. In the mean time you can use version 2.6 of the plugin as a work-around. > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka > Attachments: testpom.xml > > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-365) and do not seem to work correctly during scm:checkin
[ https://jira.codehaus.org/browse/SCM-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290944#comment-290944 ] Robert Scholte commented on SCM-365: Is this still an issue with version 1.6? > and do not seem to work correctly during scm:checkin > -- > > Key: SCM-365 > URL: https://jira.codehaus.org/browse/SCM-365 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs >Affects Versions: 1.0 >Reporter: Nathan Jones > > I am trying to use the scm plugin automatically during Maven builds. My real > goal for this is to check only one file back in, but no matter what I try, > the plugin checks in ANY file that has been changed. Below is one > configuration that I have tried. > >org.apache.maven.plugins >maven-scm-plugin >1.0 >false > > > process-resources > > checkin > > > **/** > version.properties > > > > > I also tried using only the tag without excluding anything, but it > did not work either. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Ruzicka updated MPMD-142: - Attachment: testpom.xml Empty project with attached pom would trigger the execption. > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka > Attachments: testpom.xml > > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290942#comment-290942 ] Jan Ruzicka commented on MPMD-142: -- It seems to be triggered by exclusion using excludeRoots. > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-618) StringIndexOutOfBoundsException when doing checkout from SVN in combination with plexus-utils:2.0.5+
[
https://jira.codehaus.org/browse/SCM-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed SCM-618.
--
Resolution: Fixed
Fix Version/s: 1.7
Assignee: Robert Scholte
Fixed in [rev. 1241192|http://svn.apache.org/viewvc?rev=1241192&view=rev]
> StringIndexOutOfBoundsException when doing checkout from SVN in combination
> with plexus-utils:2.0.5+
>
>
> Key: SCM-618
> URL: https://jira.codehaus.org/browse/SCM-618
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.5
>Reporter: Benjamin Bentmann
>Assignee: Robert Scholte
> Fix For: 1.7
>
> Attachments: pom.xml
>
>
> Running {{mvn clean generate-sources}} on the attached POM yields
> {noformat}
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - test:test:jar:0.1
> [INFO]task-segment: [clean, generate-sources]
> [INFO]
>
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] Deleting directory D:\z\target
> [INFO] [scm:checkout {execution: checkout}]
> [INFO] Removing D:\z\target\maven-model
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout
> http://svn.apache.org/repos/asf/maven/pom/trunk/maven
> "D:\z\target\maven-model""
> [INFO] Working directory: D:\z\target
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Cannot run checkout command :
> Embedded error: Exception while executing SCM command.
> String index out of range: -1
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Cannot run checkout
> command :
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot run
> checkout command :
> at
> org.apache.maven.scm.plugin.CheckoutMojo.checkout(CheckoutMojo.java:137)
> at
> org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:93)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM
> command.
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:428)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:405)
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290939#comment-290939 ] Dennis Lundberg commented on MPMD-142: -- Can you supply a small sample project that exhibits this problem? > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-478) SvnScmProviderRepository getParent() with endless loop
[
https://jira.codehaus.org/browse/SCM-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed SCM-478.
--
Resolution: Fixed
Fix Version/s: 1.7
Assignee: Robert Scholte
Fixed in [rev. 1241178|http://svn.apache.org/viewvc?rev=1241178&view=rev]
> SvnScmProviderRepository getParent() with endless loop
> --
>
> Key: SCM-478
> URL: https://jira.codehaus.org/browse/SCM-478
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.2
>Reporter: Florian Albrecht
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 1.7
>
>
> In SvnScmProviderRepository.getParent(), you find these lines:
> ...
> while ( newUrl.endsWith( "/" ) )
> {
> newUrl = newUrl.substring( 0, newUrl.length() );
> }
> ...
> I wanted to use that method in a project which actually HAS an scm URL set
> ending with "/trunk/". A call to this method on an SvnScmProviderRepository
> object created from that URL will never return. Note that s.substring(0,
> s.length()) will always return s, so in the code above, newUrl will not
> change.
> The body of the loop must be
> newUrl = newUrl.substring(0, newUrl.length() - 1);
> Workaround, of course, was to remove the ending slash from the SCM URL in the
> pom.xml. But this should not be a prerequisite for calling this method...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-556) Perform fails with 'working directory "...\workspace\target\checkout\workspace" does not exist!'
[
https://jira.codehaus.org/browse/MRELEASE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290936#comment-290936
]
Mark Struberg commented on MRELEASE-556:
I'm not really firm with perforce, but
"client -d
myProjectWorkspace-MavenSCM-E:\hudson\jobs\myHudsonJob\workspace\target\checkout"
looks a bit weird, because there is no space before E:\.
I'm not sure if MRELEASE-516 is really the same thing.
> Perform fails with 'working directory
> "...\workspace\target\checkout\workspace" does not exist!'
>
>
> Key: MRELEASE-556
> URL: https://jira.codehaus.org/browse/MRELEASE-556
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0
> Environment: Windows XP
>Reporter: Ed Slocombe
>
> I have maven project that fails when release:perform is called, though
> release;prepare works as expected.
> I have found two bug reports which may be of relevance:
> MRELEASE-261 -> Closed and fixed in version 2.0 but seems similiar
> MRELEASE-516 -> Output of perform is identical
> The last few lines of output I get:
> {code}
> [INFO] Executing: cmd.exe /X /C
> "p4 -d E:\hudson\jobs\myHudsonJob\workspace\target\checkout -p
> 1.1.1.1::
> client -d
> myProjectWorkspace-MavenSCM-E:\hudson\jobs\myHudsonJob\workspace\target\checkout"
> [INFO] Executing goals 'deploy'...
> [WARNING] Base directory is a file. Using base directory as POM location.
> [WARNING] Maven will be executed in interactive mode, but no input stream has
> been configured for this MavenInvoker instance.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error executing Maven.
>
> Working directory
> "E:\hudson\jobs\myHudsonJob\workspace\target\checkout\workspace" does not
> exist!
> {code}
> From reading the aforementioned bug reports, the possible cause of the error
> may be related to my modules' structure, I've tried to outline it below:
> {code}
> /workspace
> |
> |+ pom.xml (root pom whose parent is the build pom,
> | calling release:perform on this pom)
> | [Modules: moduleA and moduleB]
> |
> |- moduleA
>|+ pom.xml (parent is also build pom)
>|+ build/pom.xml (the build pom - no custom parent)
> |- moduleB
>|+ pom.xml (parent is build pom)
> {code}
> It seems that the root pom should be in some common directory inside
> 'workspace' from the error but tried that and doesn't work, nor make sense as
> to why I need it.
> It then figures that the base directory is *workspace* which then means the
> working directory is not found...the working directory it should be using
> (having seen where everything is checked out) is
> 'E:\hudson\jobs\myHudsonJob\workspace\target\checkout\'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-641) NPE when workingDirectory is null
[
https://jira.codehaus.org/browse/SCM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290932#comment-290932
]
Robert Scholte commented on SCM-641:
Actually, (and here's the real question from Olivier) what did you do to get
this exception? What caused the workingDirectory to be {{null}}? Did you use
the maven-release-plugin or maven-scm-plugin or ...?
> NPE when workingDirectory is null
> -
>
> Key: SCM-641
> URL: https://jira.codehaus.org/browse/SCM-641
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.5
> Environment: Ubuntu Natty, JAVA_HOME = /usr/lib/jvm/java-6-sun
>Reporter: Thibault Kruse
>
> $ maven-scm-client checkout rx
> scm:svn:https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1
> [INFO] Executing: /bin/sh -c svn --non-interactive checkout
> https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1 /home/tk/work/rx
> Error while executing the SCM command.
> org.apache.maven.scm.ScmException: Exception while executing SCM command.
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:428)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:405)
> at
> org.apache.maven.scm.manager.AbstractScmManager.checkOut(AbstractScmManager.java:399)
> at
> org.apache.maven.scm.client.cli.MavenScmCli.checkOut(MavenScmCli.java:238)
> at
> org.apache.maven.scm.client.cli.MavenScmCli.execute(MavenScmCli.java:190)
> at
> org.apache.maven.scm.client.cli.MavenScmCli.main(MavenScmCli.java:154)
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:86)
> at
> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82)
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
> ... 8 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-641) NPE when workingDirectory is null
[ https://jira.codehaus.org/browse/SCM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-641: --- Summary: NPE when workingDirectory is null (was: NullPointer in logging block) > NPE when workingDirectory is null > - > > Key: SCM-641 > URL: https://jira.codehaus.org/browse/SCM-641 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.5 > Environment: Ubuntu Natty, JAVA_HOME = /usr/lib/jvm/java-6-sun >Reporter: Thibault Kruse > > $ maven-scm-client checkout rx > scm:svn:https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1 > [INFO] Executing: /bin/sh -c svn --non-interactive checkout > https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1 /home/tk/work/rx > Error while executing the SCM command. > org.apache.maven.scm.ScmException: Exception while executing SCM command. > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) > at > org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356) > at > org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292) > at > org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:428) > at > org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:405) > at > org.apache.maven.scm.manager.AbstractScmManager.checkOut(AbstractScmManager.java:399) > at > org.apache.maven.scm.client.cli.MavenScmCli.checkOut(MavenScmCli.java:238) > at > org.apache.maven.scm.client.cli.MavenScmCli.execute(MavenScmCli.java:190) > at > org.apache.maven.scm.client.cli.MavenScmCli.main(MavenScmCli.java:154) > Caused by: java.lang.NullPointerException > at > org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:86) > at > org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82) > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) > ... 8 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-641) NullPointer in logging block
[
https://jira.codehaus.org/browse/SCM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290931#comment-290931
]
Robert Scholte commented on SCM-641:
Seems like the {{workingDir}} can be {{null}}. This has already been fixed for
Git, the others still call {{workingDir.getAbsolutePath()}} which causes the
NPE.
> NullPointer in logging block
>
>
> Key: SCM-641
> URL: https://jira.codehaus.org/browse/SCM-641
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.5
> Environment: Ubuntu Natty, JAVA_HOME = /usr/lib/jvm/java-6-sun
>Reporter: Thibault Kruse
>
> $ maven-scm-client checkout rx
> scm:svn:https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1
> [INFO] Executing: /bin/sh -c svn --non-interactive checkout
> https://code.ros.org/svn/ros/stacks/rx/tags/rx-1.6.1 /home/tk/work/rx
> Error while executing the SCM command.
> org.apache.maven.scm.ScmException: Exception while executing SCM command.
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
> at
> org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:428)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:405)
> at
> org.apache.maven.scm.manager.AbstractScmManager.checkOut(AbstractScmManager.java:399)
> at
> org.apache.maven.scm.client.cli.MavenScmCli.checkOut(MavenScmCli.java:238)
> at
> org.apache.maven.scm.client.cli.MavenScmCli.execute(MavenScmCli.java:190)
> at
> org.apache.maven.scm.client.cli.MavenScmCli.main(MavenScmCli.java:154)
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:86)
> at
> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82)
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
> ... 8 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-584) Checkout branch with Git uses unfamiliar command sequence which leads to errors during checkout
[
https://jira.codehaus.org/browse/SCM-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290930#comment-290930
]
Mark Struberg commented on SCM-584:
---
patch looks good, thanks Sebastian!
> Checkout branch with Git uses unfamiliar command sequence which leads to
> errors during checkout
> ---
>
> Key: SCM-584
> URL: https://jira.codehaus.org/browse/SCM-584
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.4
>Reporter: Daniel Strassenburg
>Priority: Critical
> Attachments: SCM-584.patch, SCM-584-test-prj.zip
>
>
> I want to checkout a specific branch from my git repo using the
> maven-scm-plugin. The plugin first clones the repo and gets the default
> branch as selected in gitorious. After that the plugin executes git pull ...
> mybranch which works fine as long as there are no merge conflicts between
> current branch and branch to checkout. In the case of any conflict an error
> occurs.
> The git checkout -b command should be used instead.
> {noformat}
> [INFO] Working directory:
> [INFO] Executing: /bin/sh -c cd /home/maven-proj/target/deploy-workspace &&
> git fetch git://gitorious/<...>/my-proj.git
> [INFO] Working directory:
> [INFO] Executing: /bin/sh -c cd /home/maven-proj/target/deploy-workspace &&
> git checkout HEAD
> [INFO] Working directory:
> [INFO] Executing: /bin/sh -c cd /home/maven-proj/target/deploy-workspace &&
> git ls-files
> [INFO] Working directory:
> [INFO]
> [INFO] --- maven-scm-plugin:1.4:update (switch-branch)
> [INFO] Executing: /bin/sh -c cd /home/maven-proj/target/deploy-workspace &&
> git pull git://gitorious/<..>/deploy.git mysql55
> [WARNING] failed to update git, return code 1
> [ERROR] Provider message:
> [ERROR] The git-pull origin master command failed.
> [ERROR] Command output:
> [ERROR] From git://gitorious/<...>/deploy
> * branchmysql55-> FETCH_HEAD
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-819) Surefire 2.11 fails if useManifestOnlyJar is false
[
https://jira.codehaus.org/browse/SUREFIRE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey closed SUREFIRE-819.
Resolution: Fixed
Fix Version/s: 2.12
I can confirm that this works for me in 2.12, and fails with 2.11.
> Surefire 2.11 fails if useManifestOnlyJar is false
> --
>
> Key: SUREFIRE-819
> URL: https://jira.codehaus.org/browse/SUREFIRE-819
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Scott Carey
> Fix For: 2.12
>
>
> When I tried to upgrade Avro
> (http://svn.apache.org/repos/asf/avro/trunk/lang/java) from surefire 2.10 to
> 2.11, I found that every single test failed. They all fail with
> initializationErrors such as
> {quote}
>
> initializationError(org.apache.avro.io.parsing.TestResolvingGrammarGenerator):
> Test class should have exactly one public zero-argument constructor
>
> initializationError(org.apache.avro.io.parsing.TestResolvingGrammarGenerator):
> No runnable methods
> {quote}
> These are valid JUnit 4 type tests that run fine with 2.10. We have JUnit
> 4.10 in our test scope.
> If I change useManifestOnlyJar to true, it works. Unfortunately one of our
> tests will not function with the manifectOnlyJar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[
https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290928#comment-290928
]
Andrew Gaul edited comment on SUREFIRE-827 at 2/6/12 1:28 PM:
--
Oliver I believe that this is related to parallel tests and is a regression
from SUREFIRE-760. Given an Apache commons-lang 3.1 project and setting the
surefire version in the pom to ${surefire.version}, I get these results:
{noformat}
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.12
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{noformat}
I cannot speak to Falko's symptoms.
was (Author: gaul):
Oliver I believe that this is related to parallel tests and is a regression
from SUREFIRE-760. Given an Apache commons-lang 3.1 project and setting the
surefire version in the pom to ${surefire.version}, I get these results:
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.12
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
I cannot speak to Falko's symptoms.
> Surefire 2.12 cannot run a single test, regression from 2.11
>
>
> Key: SUREFIRE-827
> URL: https://jira.codehaus.org/browse/SUREFIRE-827
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Ubuntu 11.10
>Reporter: Andrew Gaul
>
> # Surefire 2.11
> $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
> ...
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> # Surefire 2.12
> mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
> ...
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
[
https://jira.codehaus.org/browse/SUREFIRE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290928#comment-290928
]
Andrew Gaul commented on SUREFIRE-827:
--
Oliver I believe that this is related to parallel tests and is a regression
from SUREFIRE-760. Given an Apache commons-lang 3.1 project and setting the
surefire version in the pom to ${surefire.version}, I get these results:
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=classes
-Dsurefire.version=2.12
...
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.11
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
$ mvn test -Dtest=ImmutablePairTest#testBasic -Dparallel=none
-Dsurefire.version=2.12
...
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
I cannot speak to Falko's symptoms.
> Surefire 2.12 cannot run a single test, regression from 2.11
>
>
> Key: SUREFIRE-827
> URL: https://jira.codehaus.org/browse/SUREFIRE-827
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Ubuntu 11.10
>Reporter: Andrew Gaul
>
> # Surefire 2.11
> $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
> ...
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> # Surefire 2.12
> mvn test -Dtest=DataTest#testDataServerGetNonExistentFile
> ...
> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-662) Performing a release with localCheckout fail on Windows
[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290926#comment-290926
]
Mark Struberg commented on SCM-662:
---
fixed in r1241119.
> Performing a release with localCheckout fail on Windows
> ---
>
> Key: SCM-662
> URL: https://jira.codehaus.org/browse/SCM-662
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: Windows Vista, msysgit, Maven 3.0.0
>Reporter: Daniel Spilker
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitScmProviderRepository.patch
>
>
> When trying to perform a release on a Windows machine with localCheckout set
> to true, I get the following error message. The path
> 'C:\Users\daspilker\workspaces\myproject' is a git repository.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on
> project warp:
> Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C\Users\daspilker\workspaces\myproject' does not appear to be
> a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :myproject
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-662) Performing a release with localCheckout fail on Windows
[
https://jira.codehaus.org/browse/SCM-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290925#comment-290925
]
Mark Struberg commented on SCM-662:
---
fixed in r1241119.
> Performing a release with localCheckout fail on Windows
> ---
>
> Key: SCM-662
> URL: https://jira.codehaus.org/browse/SCM-662
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.6
> Environment: Windows Vista, msysgit, Maven 3.0.0
>Reporter: Daniel Spilker
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: GitScmProviderRepository.patch
>
>
> When trying to perform a release on a Windows machine with localCheckout set
> to true, I get the following error message. The path
> 'C:\Users\daspilker\workspaces\myproject' is a git repository.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:perform (default-cli) on
> project warp:
> Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'C\Users\daspilker\workspaces\myproject' does not appear to be
> a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :myproject
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-637) parsing of git urls fails on windows
[ https://jira.codehaus.org/browse/SCM-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed SCM-637. - Resolution: Fixed Fix Version/s: 1.7 fixed in r1241119 by taking the whole rest of the url as path if PROTOCOL_FILE is being used. This is fine because per definition any file:// must not contain a hostname, thus also cannot contain a port number! > parsing of git urls fails on windows > > > Key: SCM-637 > URL: https://jira.codehaus.org/browse/SCM-637 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.5 >Reporter: Felix Simmendinger >Assignee: Mark Struberg >Priority: Blocker > Fix For: 1.7 > > > please fix this issue raised in the release plugin > http://jira.codehaus.org/browse/MRELEASE-624 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-123) Add a custom ruleset file via command line
[ https://jira.codehaus.org/browse/MPMD-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290922#comment-290922 ] Andreas Dangel edited comment on MPMD-123 at 2/6/12 12:41 PM: -- See attachment: Adds the expression to set the rulesets property. However - this solution will only work with maven 3 (and break maven2!!). Works for me with maven 3.0.3 at least. was (Author: adangel): Adds the expression to set the rulesets property. However - this solution will only work with maven 3 (and break maven2!!). Works for me with maven 3.0.3 at least. > Add a custom ruleset file via command line > -- > > Key: MPMD-123 > URL: https://jira.codehaus.org/browse/MPMD-123 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: PMD > Environment: All >Reporter: Olivier Ribardière > Attachments: > 0001-Adding-possibility-to-specify-pmd.rulesets-as-a-comm.patch > > > I have plenty of maven projects and cannot really change their pom.xml, > however my continuous integration tool runs pmd so I need to be able to > specify my custom ruleset file (c:/toto/myrulesetfile.xml) directly in the > maven command line. > Would be great if we could run "mvn pmd:pmd > -Dpmd.rulesetfile=c:/toto/myrulesetfile.xml" > (Of course if I could change the pom.xml I would have added > > > d:\rulesets\strings.xml > ... but I cannot change the pom.xml and via command line it is not possible > to set a string[] parameter) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-123) Add a custom ruleset file via command line
[ https://jira.codehaus.org/browse/MPMD-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-123: Attachment: 0001-Adding-possibility-to-specify-pmd.rulesets-as-a-comm.patch Adds the expression to set the rulesets property. However - this solution will only work with maven 3 (and break maven2!!). Works for me with maven 3.0.3 at least. > Add a custom ruleset file via command line > -- > > Key: MPMD-123 > URL: https://jira.codehaus.org/browse/MPMD-123 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: PMD > Environment: All >Reporter: Olivier Ribardière > Attachments: > 0001-Adding-possibility-to-specify-pmd.rulesets-as-a-comm.patch > > > I have plenty of maven projects and cannot really change their pom.xml, > however my continuous integration tool runs pmd so I need to be able to > specify my custom ruleset file (c:/toto/myrulesetfile.xml) directly in the > maven command line. > Would be great if we could run "mvn pmd:pmd > -Dpmd.rulesetfile=c:/toto/myrulesetfile.xml" > (Of course if I could change the pom.xml I would have added > > > d:\rulesets\strings.xml > ... but I cannot change the pom.xml and via command line it is not possible > to set a string[] parameter) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-581) Git relative pathing broken with release plugin
[ https://jira.codehaus.org/browse/MRELEASE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290921#comment-290921 ] Marvin Froeder commented on MRELEASE-581: - this only happen on windows when using cygwin. > Git relative pathing broken with release plugin > --- > > Key: MRELEASE-581 > URL: https://jira.codehaus.org/browse/MRELEASE-581 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: windows xp, service pack 2 >Reporter: Matthew Sandoz >Assignee: Mark Struberg > Attachments: gitexe.zip > > > i have a multimodule project, and when i try to do a release, i get > everything working fine until the end. It seems to think for some reason that > I am at the root of my scm tree. The repo i have to work in has several > projects, and mine is in a subdirectory - domains/redemption. the plugin > appears to try to check in my submodules at my current location instead of my > scm root. > COMMAND: > mvn release:prepare -DpreparationGoals="clean install" -DskipTests > -DautoVersionSubmod > ules=true > END OF OUTPUT: > [INFO] [INFO] Reactor Summary: > [INFO] [INFO] > > [INFO] [INFO] Redemption Parent POM . SUCCESS > [2.595s] > [INFO] [INFO] Redemption Runtime Confguration ... SUCCESS > [3.531s] > [INFO] [INFO] Redemption Service Metadata ... SUCCESS > [18.816s] > [INFO] [INFO] Redemption Model .. SUCCESS > [35.693s] > [INFO] [INFO] Redemption DAO SUCCESS > [41.770s] > [INFO] [INFO] Redemption Service Implementation . SUCCESS > [17.517s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Parent POM ... SUCCESS > [0.016s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: XSLT . SUCCESS > [5.469s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: EIP .. SUCCESS > [0.343s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Version Router ... SUCCESS > [3.157s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Binding Component :: > Service Unit SUCCESS [3.656s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Service Assembly . SUCCESS > [3.516s] > [INFO] [INFO] > > [INFO] [INFO] > > [INFO] [INFO] BUILD SUCCESSFUL > [INFO] [INFO] > > [INFO] [INFO] Total time: 2 minutes 26 seconds > [INFO] [INFO] Finished at: Tue Jul 27 17:18:02 EDT 2010 > [INFO] [INFO] Final Memory: 116M/254M > [INFO] [INFO] > > [INFO] Checking in modified POMs... > [INFO] Executing: cmd.exe /X /C "git add pom.xml redemption-conf\pom.xml > redemption-metadata\pom.xml redemption-model\pom.xml rede > mption-dao\pom.xml redemption-impl\pom.xml redemption-esb\pom.xml > redemption-esb\redemption-xslt\pom.xml redemption-esb\redemption > -eip\pom.xml redemption-esb\redemption-router\pom.xml > redemption-esb\redemption-bc-su\pom.xml redemption-esb\redemption-sa\pom.xml > " > [INFO] Working directory: D:\workspaces\crm-dev\domains\redemption > [INFO] Executing: cmd.exe /X /C "git status" > [INFO] Working directory: D:\workspaces\crm-dev\domains\redemption > [INFO] Executing: cmd.exe /X /C "git commit --verbose -F > D:\DOCUME~1\sandozm\LOCALS~1\Temp\maven-scm-1862033505.commit pom.xml red > emption-conf\pom.xml redemption-metadata\pom.xml redemption-model\pom.xml > redemption-dao\pom.xml redemption-impl\pom.xml redemptio > n-esb\pom.xml redemption-esb\redemption-xslt\pom.xml > redemption-esb\redemption-eip\pom.xml redemption-esb\redemption-router\pom.xm > l redemption-esb\redemption-bc-su\pom.xml > redemption-esb\redemption-sa\pom.xml" > [INFO] Working directory: D:\workspaces\crm-dev\domains\redemption > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to commit files > Provider message: > The git-commit command failed. > Command output: > error: pathspec 'redemption-conf\pom.xml' did not match any file(s) known to > git. > error: pathspec 'redemption-metadata\pom.xml' did not match any file(s) known > to git. > error: pathspec 'redemption-model\pom.xml' did not match any file(s) known to > git. > error: pathspec 'redemption-dao\pom.xml' did not match any file(s) known to > git. > error: pathspec 'redemption-impl\pom.
[jira] (MRELEASE-581) Git relative pathing broken with release plugin
[ https://jira.codehaus.org/browse/MRELEASE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290920#comment-290920 ] Mark Struberg commented on MRELEASE-581: might this be a Windows pathing problem? I never suffered from such problems under Linux and OSX! > Git relative pathing broken with release plugin > --- > > Key: MRELEASE-581 > URL: https://jira.codehaus.org/browse/MRELEASE-581 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: windows xp, service pack 2 >Reporter: Matthew Sandoz >Assignee: Mark Struberg > Attachments: gitexe.zip > > > i have a multimodule project, and when i try to do a release, i get > everything working fine until the end. It seems to think for some reason that > I am at the root of my scm tree. The repo i have to work in has several > projects, and mine is in a subdirectory - domains/redemption. the plugin > appears to try to check in my submodules at my current location instead of my > scm root. > COMMAND: > mvn release:prepare -DpreparationGoals="clean install" -DskipTests > -DautoVersionSubmod > ules=true > END OF OUTPUT: > [INFO] [INFO] Reactor Summary: > [INFO] [INFO] > > [INFO] [INFO] Redemption Parent POM . SUCCESS > [2.595s] > [INFO] [INFO] Redemption Runtime Confguration ... SUCCESS > [3.531s] > [INFO] [INFO] Redemption Service Metadata ... SUCCESS > [18.816s] > [INFO] [INFO] Redemption Model .. SUCCESS > [35.693s] > [INFO] [INFO] Redemption DAO SUCCESS > [41.770s] > [INFO] [INFO] Redemption Service Implementation . SUCCESS > [17.517s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Parent POM ... SUCCESS > [0.016s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: XSLT . SUCCESS > [5.469s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: EIP .. SUCCESS > [0.343s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Version Router ... SUCCESS > [3.157s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Binding Component :: > Service Unit SUCCESS [3.656s] > [INFO] [INFO] crm :: guest :: redemption :: ESB :: Service Assembly . SUCCESS > [3.516s] > [INFO] [INFO] > > [INFO] [INFO] > > [INFO] [INFO] BUILD SUCCESSFUL > [INFO] [INFO] > > [INFO] [INFO] Total time: 2 minutes 26 seconds > [INFO] [INFO] Finished at: Tue Jul 27 17:18:02 EDT 2010 > [INFO] [INFO] Final Memory: 116M/254M > [INFO] [INFO] > > [INFO] Checking in modified POMs... > [INFO] Executing: cmd.exe /X /C "git add pom.xml redemption-conf\pom.xml > redemption-metadata\pom.xml redemption-model\pom.xml rede > mption-dao\pom.xml redemption-impl\pom.xml redemption-esb\pom.xml > redemption-esb\redemption-xslt\pom.xml redemption-esb\redemption > -eip\pom.xml redemption-esb\redemption-router\pom.xml > redemption-esb\redemption-bc-su\pom.xml redemption-esb\redemption-sa\pom.xml > " > [INFO] Working directory: D:\workspaces\crm-dev\domains\redemption > [INFO] Executing: cmd.exe /X /C "git status" > [INFO] Working directory: D:\workspaces\crm-dev\domains\redemption > [INFO] Executing: cmd.exe /X /C "git commit --verbose -F > D:\DOCUME~1\sandozm\LOCALS~1\Temp\maven-scm-1862033505.commit pom.xml red > emption-conf\pom.xml redemption-metadata\pom.xml redemption-model\pom.xml > redemption-dao\pom.xml redemption-impl\pom.xml redemptio > n-esb\pom.xml redemption-esb\redemption-xslt\pom.xml > redemption-esb\redemption-eip\pom.xml redemption-esb\redemption-router\pom.xm > l redemption-esb\redemption-bc-su\pom.xml > redemption-esb\redemption-sa\pom.xml" > [INFO] Working directory: D:\workspaces\crm-dev\domains\redemption > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to commit files > Provider message: > The git-commit command failed. > Command output: > error: pathspec 'redemption-conf\pom.xml' did not match any file(s) known to > git. > error: pathspec 'redemption-metadata\pom.xml' did not match any file(s) known > to git. > error: pathspec 'redemption-model\pom.xml' did not match any file(s) known to > git. > error: pathspec 'redemption-dao\pom.xml' did not match any file(s) known
[jira] (MRELEASE-731) Change Maven prerequisite from 2.0.9 to 2.2.1
[
https://jira.codehaus.org/browse/MRELEASE-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290917#comment-290917
]
Mark Struberg commented on MRELEASE-731:
Imo it's fairly safe to update the prerequisites to 2.2.1 those days. +1 for it.
> Change Maven prerequisite from 2.0.9 to 2.2.1
> -
>
> Key: MRELEASE-731
> URL: https://jira.codehaus.org/browse/MRELEASE-731
> Project: Maven 2.x Release Plugin
> Issue Type: Task
>Affects Versions: 2.2.2
>Reporter: Robert Scholte
>
> Upgrading the plexus-utils might solve a couple of issues, but is now locked
> at 1.5.8.
> When upgrading this to a more recent version a lot of tests fail due to a
> CNFE:
> {noformat}
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component 'org.apache.maven.project.MavenProjectBuilder', it
> could not be started
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
> at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:216)
> at
> org.apache.maven.shared.release.phase.AbstractReleaseTestCase.setUp(AbstractReleaseTestCase.java:99)
> at
> org.apache.maven.shared.release.phase.ScmCommitPreparationPhaseTest.setUp(ScmCommitPreparationPhaseTest.java:72)
> at junit.framework.TestCase.runBare(TestCase.java:128)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
> Error starting component
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
> at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
> ... 16 more
> Caused by:
> org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
> Error composing component
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
> ... 19 more
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed of field profilesBuilder in object of type
> org.apache.maven.project.DefaultMavenProjectBuilder because the requirement
> ComponentRequirement{role='org.apache.maven.profiles.MavenProfilesBuilder',
> roleHint='null', fieldName='null'} was missing
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
> ... 21 more
> Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component 'org.apache.maven.profiles.MavenProfilesBuilder',
> it could not be created
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(Def
[jira] (MRELEASE-702) Could not release project due to GIT clone error when working in sub-directory
[
https://jira.codehaus.org/browse/MRELEASE-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290916#comment-290916
]
Mark Struberg commented on MRELEASE-702:
This issue is caused by a 'fix' for SVN which got applied a _long_ time ago. By
default the maven model builder adds the child modules to the URLS like
. You can work around this by just manually adding the scm
section in your child modules as well.
Btw, this should only affect you if you try to start the release from within
the child modules. If you start it from the root of the SCM project, then it
works fine.
> Could not release project due to GIT clone error when working in sub-directory
> --
>
> Key: MRELEASE-702
> URL: https://jira.codehaus.org/browse/MRELEASE-702
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: Git
>Affects Versions: 2.2.1
> Environment: LINUX, GIT, Maven 3.X, maven-release-plugin:2.2.1:perform
>Reporter: jurevert
>Assignee: Mark Struberg
>
> We have multi modules project structure like :
> {code}
> ParentPom
> |-- pom.xml (Modules : SampleProjectEAR,SampleProjectWeb,SampleProjectCommons)
> SampleProjectEAR
> |-- pom.xml (Parent : ParentPom pom.xml)
> SampleProjectWeb
> |-- pom.xml (Parent : ParentPom pom.xml)
> SampleProjectCommons
> |-- pom.xml (Parent : ParentPom pom.xml)
> {code}
> Our goal is to release the project. Th eparent project is in a subdir.
> When running the following command from root directory; we've got the
> following error :
> {code}
> mvn release:clean release:prepare release:perform -B -U -X -f
> ParentPom/pom.xml
> [...]
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.1:perform (default-cli) on
> project WelcomTutorial: Unable to checkout from SCM
> [ERROR] Provider message:
> [ERROR] The git-clone command failed.
> [ERROR] Command output:
> [ERROR] fatal:
> '/app/DINB/bamboo-agent-home/xml-data/build-dir/WTUT-RELEASE-JOB1/ParentPom'
> does not appear to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.2.1:perform
> (default-cli) on project WelcomTutorial: Unable to checkout from SCM
> Provider message:
> The git-clone command failed.
> Command output:
> fatal:
> '/app/DINB/bamboo-agent-home/xml-data/build-dir/WTUT-RELEASE-JOB1/ParentPom'
> does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to checkout
> from SCM
> Provider message:
> The git-clone command failed.
> Command output:
> fatal:
> '/app/DINB/bamboo-agent-home/xml-data/build-dir/WTUT-RELEASE-JOB1/ParentPom'
> does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.plugins.rele
[jira] (MCHANGES-218) Downloading from JIRA fails if issueManagement.url has trailing slash
[
https://jira.codehaus.org/browse/MCHANGES-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290911#comment-290911
]
Cristian Lupu commented on MCHANGES-218:
I would create a unit test to test this method, getJiraUrlAndProjectId from
JiraHelper class before trying to fix it again. And run it with different
values for issueManagementUrl:
http://jira.codehaus.org/browse/DOXIA/
http://jira.codehaus.org/
http://jira.codehaus.org
http://jira.codehaus.org/browse/DOXIA
and then try to fix it
> Downloading from JIRA fails if issueManagement.url has trailing slash
> -
>
> Key: MCHANGES-218
> URL: https://jira.codehaus.org/browse/MCHANGES-218
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 2.4
>
>
> With an issueManagement.url like http://jira.codehaus.org/browse/DOXIA/ (note
> trailing slash), the jira report chokes
> {noformat}
> [WARNING] Downloading from JIRA failed. Received: [404]
> {noformat}
> and an empty report is generated. removing the trailing slash makes it work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-218) Downloading from JIRA fails if issueManagement.url has trailing slash
[
https://jira.codehaus.org/browse/MCHANGES-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290908#comment-290908
]
Cristian Lupu commented on MCHANGES-218:
This fix doesn't work for the case when url is set to a value like
"http://jira.codehaus.org/";
Because it will remove the last "/" and few lines below it tries to extract url
again based on the last index for "/" and the url extracted in that case is
"http:/"
54 if ( url.endsWith( "/" ) )
55 {
56 // MCHANGES-218
57 url = url.substring( 0, url.lastIndexOf( '/' ) );
58 }
.
72 String jiraUrl = url.substring( 0, url.lastIndexOf( '/' ) );
Easy to test with a quick unit test and a different value for
issueManagementUrl:
Map jiraUrlAndProjectId =
getJiraUrlAndProjectId("http://jira.codehaus.org/";);
assertEquals("http://jira.codehaus.org";, jiraUrlAndProjectId.get("url"));
> Downloading from JIRA fails if issueManagement.url has trailing slash
> -
>
> Key: MCHANGES-218
> URL: https://jira.codehaus.org/browse/MCHANGES-218
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.3
>Reporter: Lukas Theussl
>Assignee: Lukas Theussl
> Fix For: 2.4
>
>
> With an issueManagement.url like http://jira.codehaus.org/browse/DOXIA/ (note
> trailing slash), the jira report chokes
> {noformat}
> [WARNING] Downloading from JIRA failed. Received: [404]
> {noformat}
> and an empty report is generated. removing the trailing slash makes it work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
[ https://jira.codehaus.org/browse/MPMD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290905#comment-290905 ] Jan Ruzicka commented on MPMD-142: -- this error appears for all goals pmd:check, pmd:cpd-check, pmd:pmd, pmd:cpd > PMD Report for maven site fails with ClassCastException > > > Key: MPMD-142 > URL: https://jira.codehaus.org/browse/MPMD-142 > Project: Maven 2.x PMD Plugin > Issue Type: Bug >Affects Versions: 2.7 > Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 >Reporter: Jan Ruzicka > > Maven 2.2.1 is complaining when mvn site is run. > It is stopping in PMD report. > Section from log is below. > This error appeared freshly this morning. The site goal run successfully > before. > [INFO] Generating "PMD Report" report. > [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink > instance and no SinkFactory available. Please update this plugin. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] java.lang.String cannot be cast to java.io.File > [INFO] > > [INFO] Trace > java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File > at > org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) > at > org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) > at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) > at > org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-142) PMD Report for maven site fails with ClassCastException
Jan Ruzicka created MPMD-142: Summary: PMD Report for maven site fails with ClassCastException Key: MPMD-142 URL: https://jira.codehaus.org/browse/MPMD-142 Project: Maven 2.x PMD Plugin Issue Type: Bug Affects Versions: 2.7 Environment: Maven 2.2.1, Jenkins 1.424.1, Linux RHEL 5 Reporter: Jan Ruzicka Maven 2.2.1 is complaining when mvn site is run. It is stopping in PMD report. Section from log is below. This error appeared freshly this morning. The site goal run successfully before. [INFO] Generating "PMD Report" report. [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] java.lang.String cannot be cast to java.io.File [INFO] [INFO] Trace java.lang.ClassCastException: java.lang.String cannot be cast to java.io.File at org.apache.maven.plugin.pmd.AbstractPmdReport.getFilesToProcess(AbstractPmdReport.java:284) at org.apache.maven.plugin.pmd.PmdReport.generateReport(PmdReport.java:249) at org.apache.maven.plugin.pmd.PmdReport.execute(PmdReport.java:175) at org.apache.maven.plugin.pmd.PmdReport.executeReport(PmdReport.java:149) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPDF-54) Umlaute are not represented correctly (not always)
Valeriy created MPDF-54: --- Summary: Umlaute are not represented correctly (not always) Key: MPDF-54 URL: https://jira.codehaus.org/browse/MPDF-54 Project: Maven 2.x PDF Plugin Issue Type: Bug Affects Versions: 1.1 Environment: Win 7, Maven 2.2.1, JVM "1.6.0_29" Reporter: Valeriy Attachments: MPDF_BUG.PNG The german umlauts (äöüß) are not represented correctly. Instead of it appears # symbol. But not always. The items from Document Descriptor are represented correctly. For instance: in document descriptor we have In 0-uebersicht.apt we have a line: Übersicht test äöüß ÄÖÜ The output looks: #bersicht test ###. See also attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-256) it's not possible to create classes attachment without classifier
[
https://jira.codehaus.org/browse/MWAR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290896#comment-290896
]
Dmitry Goldenberg commented on MWAR-256:
Totally agreed. Am dealing with this issue now and not sure how to work around
it.
> it's not possible to create classes attachment without classifier
> -
>
> Key: MWAR-256
> URL: https://jira.codehaus.org/browse/MWAR-256
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Rafal Krzewski
>
> I would like to package classes in my war-packaged project into a jar, but I
> don't want to use default 'classes' classifier assigned by the plugin. The
> generated artifacts have distinct packaging types, so there is no conflict
> and the classifier provides no useful additional information. Using the
> following configuration:
> {quote}
> {{}}
> {{}}
> {{}}
> {quote}
> Results in "classes" classifier being used anyway. If I understand the
> behavior correctly Plexus assigns the variable it's default value, when
> presented an empty input. I don't think this can be fixed in way that is both
> clean and backward compatible. Either the default value will change, which
> would break existing builds that don't specify plugin version explicitly, or
> some clunky additional parameter like
> {{false}}, or magic value like
> {{NONE}} need to be introduced.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-829) junit | Support inheritance while running test cases belonging to a particular category/group
Gayathri Muralidharan created SUREFIRE-829: -- Summary: junit | Support inheritance while running test cases belonging to a particular category/group Key: SUREFIRE-829 URL: https://jira.codehaus.org/browse/SUREFIRE-829 Project: Maven Surefire Issue Type: Bug Components: Junit 4.x support Affects Versions: 2.12 Reporter: Gayathri Muralidharan We have a parent class which is extended by all the unit test cases (multi module maven based project) It would be great if surefire plugin config looks for the category in parent class as well. This will avoid redundant @Category(UnitTestCategory.class) annotations, as we expect all unit test cases to extend the corresponding base class and the base class will alone be annotated with @Category(UnitTestCategory.class) Please let me know if this can be achieved by any other config. Thanks, Gayathri -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-145) Documentation does not list layouts
Benson Margulies created MDEPLOY-145: Summary: Documentation does not list layouts Key: MDEPLOY-145 URL: https://jira.codehaus.org/browse/MDEPLOY-145 Project: Maven 2.x and 3.x Deploy Plugin Issue Type: Bug Components: deploy:deploy Affects Versions: 2.7 Reporter: Benson Margulies the documentation for deploy:deploy never lists the valid, or even likely, values for 'layout'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290880#comment-290880
]
Julian Atienza edited comment on MNG-2971 at 2/6/12 7:06 AM:
-
That happens to me creating a project from an archetype from my company. Even
having the parameters required in the archeype-metadata.xml and passing them on
mvn archetype:generate, the resulting pom has not the parameters (groupId,
artifactId...) replaced
This is the output from mvn archetype:generate:
Using following parameters for creating project from Archetype:
mygroup-archetype:1.0-SNAPSHOT
[INFO]
[INFO] Parameter: groupId, Value: org.myorg.mygroup.myproject
[INFO] Parameter: artifactId, Value: myproject
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: package, Value: org.myorg.mygroup
[INFO] Parameter: packageInPathFormat, Value: org/myorg/mygroup
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: package, Value: org.myorg.mygroup
[INFO] Parameter: groupId, Value: org.myorg.mygroup.myproject
[INFO] Parameter: artifactId, Value: myproject
this is the generated project's pom file:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
$org.myorg.mygroup
$mygroup-archetype
$1.0-SNAPSHOT
junit
junit
3.8.1
test
this is a section of the archetype-metadata.xml for my company's archetype
http://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.0.0
http://maven.apache.org/xsd/archetype-descriptor-1.0.0.xsd";
name="mygroup-archetype" partial="false">
src/main/java
**/*.java
src/test/java/
**/*.java
/src/main/generated
**/*.java
...
was (Author: julianah):
my archetype pom
> Variables are not replaced into installed pom file
> --
>
> Key: MNG-2971
> URL: https://jira.codehaus.org/browse/MNG-2971
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
>Reporter: Laurent Dauvilaire
>Assignee: Ralph Goers
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: pom.xml
>
>
> Variables are not replaced into installed pom file.
> Here is a sample pom file
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.xxx.root
> root
> pom
> ${prop.version}
> My Project
> ...
>
> 3.0.20
>
>
> The installed pom is into
> ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
> is the same as the project pom file but the version referenced into the
> installed pom file is ${prop.version} instead of 3.0.20
> which creates problem to artifacts depending of this one.
> Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Atienza updated MNG-2971:
Attachment: pom.xml
my archetype pom
> Variables are not replaced into installed pom file
> --
>
> Key: MNG-2971
> URL: https://jira.codehaus.org/browse/MNG-2971
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
>Reporter: Laurent Dauvilaire
>Assignee: Ralph Goers
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: pom.xml
>
>
> Variables are not replaced into installed pom file.
> Here is a sample pom file
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.xxx.root
> root
> pom
> ${prop.version}
> My Project
> ...
>
> 3.0.20
>
>
> The installed pom is into
> ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
> is the same as the project pom file but the version referenced into the
> installed pom file is ${prop.version} instead of 3.0.20
> which creates problem to artifacts depending of this one.
> Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-614) site plugin failure when forking a lifecycle
[ https://jira.codehaus.org/browse/MSITE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290875#comment-290875 ] Florian Probst commented on MSITE-614: -- I'm getting an similar message in my project. It seems that the site Plugin can't execute the javadoc plugin for an submodule: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-cli) on project DE_Project: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.2:exploded (default) on project DE_IndustrialWiki_Web: Failed to copy file for artifact [-041:DE_Project_Ext:jar:1.0.0-SNAPSHOT:compile]: D:\FP\Projekte\\-041\Java\DE_Project\DE_Project_Ext\target\classes (Zugriff verweigert) -> [Help 1] Dennis, what do you mean if you say the plugin is not correctly configured? As Andreas said, the same project works well with version 2.3 of the site plugin, while version 3.0 fails... > site plugin failure when forking a lifecycle > > > Key: MSITE-614 > URL: https://jira.codehaus.org/browse/MSITE-614 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0 >Reporter: Andreas Pieber > Attachments: 5ebbfe13_maven-test.tar.gz > > > If you execute "mvn site" in the attached test project it fails because of > the forked cycles. The test project could therefore not be resolved in the > maven plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-154) With option supressions will be ignored for testsources.
[ https://jira.codehaus.org/browse/MCHECKSTYLE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290868#comment-290868 ] Michael Nitschke commented on MCHECKSTYLE-154: -- I was not able to try it with 2.6 caused to many subsequent problems. And project guidelines preventing me to switch the whole project to 2.6. Sorry, for the delay. Please have someone else verify the fix. > With option supressions will be ignored for > testsources. > - > > Key: MCHECKSTYLE-154 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-154 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Michael Nitschke > > We have set up a mulit pom maven project with checkstyle and suppressions. > For the source run all supressions (some whitespace) will be followed. > For the testsources the supressions will be ignored, resulting in ~6000 wrong > false in a single subproject. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
