[jira] (MSITE-737) French translation
Olivier Maury created MSITE-737: --- Summary: French translation Key: MSITE-737 URL: https://jira.codehaus.org/browse/MSITE-737 Project: Maven Site Plugin Issue Type: Improvement Components: localization Reporter: Olivier Maury Priority: Minor Attachments: project-info-report_fr.properties Some corrections on typography and term. File from http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report_fr.properties -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1135) Improve ignore message for TestNG
Michal Bocek created SUREFIRE-1135: -- Summary: Improve ignore message for TestNG Key: SUREFIRE-1135 URL: https://jira.codehaus.org/browse/SUREFIRE-1135 Project: Maven Surefire Issue Type: New Feature Components: TestNG support Reporter: Michal Bocek Once the test is ignored/skipped in TestNG no additional informations are reported. Surefire xml report contains only "skipped" element without any information. It will be very useful to provide addition info like message and stacktrace. JUnit reporter correctly provide ignore message from "Ignore" annotation so we can similarly provide message from SkipException. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1135) Improve ignore message for TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361141#comment-361141 ] Tibor Digana commented on SUREFIRE-1135: Hi Michal, Pls provide IT or project and your expected result in xml. We can include it in next release faster. > Improve ignore message for TestNG > - > > Key: SUREFIRE-1135 > URL: https://jira.codehaus.org/browse/SUREFIRE-1135 > Project: Maven Surefire > Issue Type: New Feature > Components: TestNG support >Reporter: Michal Bocek > > Once the test is ignored/skipped in TestNG no additional informations are > reported. Surefire xml report contains only "skipped" element without any > information. It will be very useful to provide addition info like message and > stacktrace. > JUnit reporter correctly provide ignore message from "Ignore" annotation so > we can similarly provide message from SkipException. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1135) Improve ignore message for TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana reassigned SUREFIRE-1135: -- Assignee: Tibor Digana > Improve ignore message for TestNG > - > > Key: SUREFIRE-1135 > URL: https://jira.codehaus.org/browse/SUREFIRE-1135 > Project: Maven Surefire > Issue Type: New Feature > Components: TestNG support >Reporter: Michal Bocek >Assignee: Tibor Digana > > Once the test is ignored/skipped in TestNG no additional informations are > reported. Surefire xml report contains only "skipped" element without any > information. It will be very useful to provide addition info like message and > stacktrace. > JUnit reporter correctly provide ignore message from "Ignore" annotation so > we can similarly provide message from SkipException. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-469) analyze-report java.io.FileNotFoundException:
[
https://jira.codehaus.org/browse/MDEP-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361149#comment-361149
]
Stephan Schroevers commented on MDEP-469:
-
I can confirm that version 2.8 is no affected. Specific repro case:
# Have an aggregator build with two modules _A_ and _B_.
# Make sure _B_ depends on _A_.
# Configure the {{analyze-only}} goal to be run during the
{{process-test-classes}} phase.
# Run {{`mvn test`}} on the aggragator (i.e., the top level module).
> analyze-report java.io.FileNotFoundException:
> -
>
> Key: MDEP-469
> URL: https://jira.codehaus.org/browse/MDEP-469
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: jieryn
>
> Apache Maven 3.2.3, multi-module project,
> maven-dependency-plugin:analyze-report:2.9 throws FileNotFoundException
> during site phase (same exact project and configuration but with 2.8 is
> successful):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> dao: Error generating maven-dependency-plugin:2.9:analyze-report: Cannot
> analyze dependencies:
> /var/lib/jenkins/jobs/site_com.acme.proj/workspace/domain/target/classes (Is
> a directory) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project dao: Error generating maven-dependency-plugin:2.9:analyze-report:
> Cannot analyze dependencies
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
> maven-dependency-plugin:2.9:analyze-report: Cannot analyze dependencies
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:146)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> generating maven-dependency-plugin:2.9:analyze-report: Cannot analyze
> dependencies
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:311)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:129)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:182)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:141)
> ... 21 more
> Caused by: org.apache.maven.reporting.MavenReportException: Cannot analyze
> dependencies
> at
> org.apache.maven.plugin.dependency.analyze.AnalyzeReportMojo.executeReport(AnalyzeReportMojo.java:145)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196)
> at
> org.apa
[jira] (MDEP-469) analyze-report java.io.FileNotFoundException:
[
https://jira.codehaus.org/browse/MDEP-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361149#comment-361149
]
Stephan Schroevers edited comment on MDEP-469 at 1/13/15 7:46 AM:
--
I can confirm that version 2.8 is not affected. Specific reproduction case:
# Have an aggregator build with two modules _A_ and _B_.
# Make sure _B_ depends on _A_.
# Configure the {{analyze-only}} goal to be run during the
{{process-test-classes}} phase.
# Run {{`mvn test`}} on the aggragator (i.e., the top level module).
was (Author: stephan202):
I can confirm that version 2.8 is no affected. Specific repro case:
# Have an aggregator build with two modules _A_ and _B_.
# Make sure _B_ depends on _A_.
# Configure the {{analyze-only}} goal to be run during the
{{process-test-classes}} phase.
# Run {{`mvn test`}} on the aggragator (i.e., the top level module).
> analyze-report java.io.FileNotFoundException:
> -
>
> Key: MDEP-469
> URL: https://jira.codehaus.org/browse/MDEP-469
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: jieryn
>
> Apache Maven 3.2.3, multi-module project,
> maven-dependency-plugin:analyze-report:2.9 throws FileNotFoundException
> during site phase (same exact project and configuration but with 2.8 is
> successful):
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> dao: Error generating maven-dependency-plugin:2.9:analyze-report: Cannot
> analyze dependencies:
> /var/lib/jenkins/jobs/site_com.acme.proj/workspace/domain/target/classes (Is
> a directory) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
> project dao: Error generating maven-dependency-plugin:2.9:analyze-report:
> Cannot analyze dependencies
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
> maven-dependency-plugin:2.9:analyze-report: Cannot analyze dependencies
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:146)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> generating maven-dependency-plugin:2.9:analyze-report: Cannot analyze
> dependencies
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:239)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:311)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:129)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:182)
> at
> org.apache.maven.plug
[jira] (SCM-788) new goal to manipulate scm ignore metadata (e.g. .gitignore)
jieryn created SCM-788: -- Summary: new goal to manipulate scm ignore metadata (e.g. .gitignore) Key: SCM-788 URL: https://jira.codehaus.org/browse/SCM-788 Project: Maven SCM Issue Type: Improvement Reporter: jieryn Priority: Minor Please allow the plugin to manipulate and update standard SCM ignore metadata: .cvsignore, svn:ignore, .gitignore -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-785) Upgrade Plugin Required Maven Version to 2.2.1
[ https://jira.codehaus.org/browse/SCM-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed SCM-785. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [fc12e06660b1698bf3da061b3989ed04d00b9f03|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commitdiff;h=fc12e06660b1698bf3da061b3989ed04d00b9f03;hp=06c39544f2aa1534cdbd7e41a054f86d9b635f08] > Upgrade Plugin Required Maven Version to 2.2.1 > -- > > Key: SCM-785 > URL: https://jira.codehaus.org/browse/SCM-785 > Project: Maven SCM > Issue Type: Wish > Components: maven-plugin >Affects Versions: 1.9.2 >Reporter: Herve Boutemy >Assignee: Karl-Heinz Marbaise > Fix For: 1.9.3 > > > 2.2.1 is the unified minimum Maven version we're targetting > see > https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html > for report -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-789) Upgrade to maven-parent version 26
Karl-Heinz Marbaise created SCM-789: --- Summary: Upgrade to maven-parent version 26 Key: SCM-789 URL: https://jira.codehaus.org/browse/SCM-789 Project: Maven SCM Issue Type: Task Affects Versions: 1.9.3 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade to maven-parent version 2.6 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-789) Upgrade to maven-parent version 26
[ https://jira.codehaus.org/browse/SCM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated SCM-789: Fix Version/s: 1.9.3 > Upgrade to maven-parent version 26 > -- > > Key: SCM-789 > URL: https://jira.codehaus.org/browse/SCM-789 > Project: Maven SCM > Issue Type: Task >Affects Versions: 1.9.3 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.9.3 > > > Upgrade to maven-parent version 2.6 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-789) Upgrade to maven-parent version 26
[ https://jira.codehaus.org/browse/SCM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed SCM-789. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [11778e29546f5dcac860673f7b316b771f703fee|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commitdiff;h=11778e29546f5dcac860673f7b316b771f703fee] > Upgrade to maven-parent version 26 > -- > > Key: SCM-789 > URL: https://jira.codehaus.org/browse/SCM-789 > Project: Maven SCM > Issue Type: Task >Affects Versions: 1.9.3 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.9.3 > > > Upgrade to maven-parent version 2.6 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-785) Upgrade Plugin Required Maven Version to 2.2.1
[ https://jira.codehaus.org/browse/SCM-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361163#comment-361163 ] Karl-Heinz Marbaise commented on SCM-785: - Follow up in [3f5720e4354549bc3ff1fb7e861ae0b71699f68a|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commitdiff;h=3f5720e4354549bc3ff1fb7e861ae0b71699f68a] > Upgrade Plugin Required Maven Version to 2.2.1 > -- > > Key: SCM-785 > URL: https://jira.codehaus.org/browse/SCM-785 > Project: Maven SCM > Issue Type: Wish > Components: maven-plugin >Affects Versions: 1.9.2 >Reporter: Herve Boutemy >Assignee: Karl-Heinz Marbaise > Fix For: 1.9.3 > > > 2.2.1 is the unified minimum Maven version we're targetting > see > https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html > for report -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSTAGE-19) Upgrade maven-wagon to 2.8
Karl-Heinz Marbaise created MSTAGE-19: - Summary: Upgrade maven-wagon to 2.8 Key: MSTAGE-19 URL: https://jira.codehaus.org/browse/MSTAGE-19 Project: Maven Stage Plugin Issue Type: Task Affects Versions: 1.0 Reporter: Karl-Heinz Marbaise Priority: Minor Upgrade maven-wagon to 2.8 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSTAGE-19) Upgrade maven-wagon to 2.8
[ https://jira.codehaus.org/browse/MSTAGE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MSTAGE-19: -- Fix Version/s: 1.0 > Upgrade maven-wagon to 2.8 > -- > > Key: MSTAGE-19 > URL: https://jira.codehaus.org/browse/MSTAGE-19 > Project: Maven Stage Plugin > Issue Type: Task >Affects Versions: 1.0 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.0 > > > Upgrade maven-wagon to 2.8 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSTAGE-19) Upgrade maven-wagon to 2.8
[ https://jira.codehaus.org/browse/MSTAGE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MSTAGE-19. - Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1651493|http://svn.apache.org/r1651493]. > Upgrade maven-wagon to 2.8 > -- > > Key: MSTAGE-19 > URL: https://jira.codehaus.org/browse/MSTAGE-19 > Project: Maven Stage Plugin > Issue Type: Task >Affects Versions: 1.0 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 1.0 > > > Upgrade maven-wagon to 2.8 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPH-103) Remove unused dependency maven-monitor
Karl-Heinz Marbaise created MPH-103: --- Summary: Remove unused dependency maven-monitor Key: MPH-103 URL: https://jira.codehaus.org/browse/MPH-103 Project: Maven Help Plugin Issue Type: Task Affects Versions: 2.2.1 Reporter: Karl-Heinz Marbaise Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPH-103) Remove unused dependency maven-monitor
[ https://jira.codehaus.org/browse/MPH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MPH-103: Fix Version/s: 2.2.1 > Remove unused dependency maven-monitor > -- > > Key: MPH-103 > URL: https://jira.codehaus.org/browse/MPH-103 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 2.2.1 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.2.1 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPH-103) Remove unused dependency maven-monitor
[ https://jira.codehaus.org/browse/MPH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MPH-103. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1651495|http://svn.apache.org/r1651495] > Remove unused dependency maven-monitor > -- > > Key: MPH-103 > URL: https://jira.codehaus.org/browse/MPH-103 > Project: Maven Help Plugin > Issue Type: Task >Affects Versions: 2.2.1 >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.2.1 > > -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-780) Duplicate connection url's properties
[
https://jira.codehaus.org/browse/SCM-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361168#comment-361168
]
Dan Tran commented on SCM-780:
--
The reason why I reluctant to commit the fix since user may already use this
accidental feature ( one external property for both internal configurations.
Thought?
> Duplicate connection url's properties
> -
>
> Key: SCM-780
> URL: https://jira.codehaus.org/browse/SCM-780
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-plugin
>Affects Versions: 1.9.1
>Reporter: Dan Tran
>Assignee: Dan Tran
> Fix For: 1.9.3
>
>
> at AbstractScmMojo
> /**
> * The SCM connection URL.
> */
> @Parameter( property = "connectionUrl", defaultValue =
> "${project.scm.connection}" )
> private String connectionUrl;
> /**
> * The SCM connection URL for developers.
> */
> @Parameter( property = "connectionUrl", defaultValue =
> "${project.scm.developerConnection}" )
> private String developerConnectionUrl;
> the property "connectionUrl" is used by both connectionUrl and
> developerConnectionUrl
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1135) Improve ignore message for TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361171#comment-361171 ] Michal Bocek commented on SUREFIRE-1135: Hi Tibor, I have created pull request with patch and IT. https://github.com/apache/maven-surefire/pull/79 > Improve ignore message for TestNG > - > > Key: SUREFIRE-1135 > URL: https://jira.codehaus.org/browse/SUREFIRE-1135 > Project: Maven Surefire > Issue Type: New Feature > Components: TestNG support >Reporter: Michal Bocek >Assignee: Tibor Digana > Attachments: TEST-testng.SkipExceptionReportTest.xml > > > Once the test is ignored/skipped in TestNG no additional informations are > reported. Surefire xml report contains only "skipped" element without any > information. It will be very useful to provide addition info like message and > stacktrace. > JUnit reporter correctly provide ignore message from "Ignore" annotation so > we can similarly provide message from SkipException. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-1135) Improve ignore message for TestNG
[ https://jira.codehaus.org/browse/SUREFIRE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Bocek updated SUREFIRE-1135: --- Attachment: TEST-testng.SkipExceptionReportTest.xml Sample surefire report > Improve ignore message for TestNG > - > > Key: SUREFIRE-1135 > URL: https://jira.codehaus.org/browse/SUREFIRE-1135 > Project: Maven Surefire > Issue Type: New Feature > Components: TestNG support >Reporter: Michal Bocek >Assignee: Tibor Digana > Attachments: TEST-testng.SkipExceptionReportTest.xml > > > Once the test is ignored/skipped in TestNG no additional informations are > reported. Surefire xml report contains only "skipped" element without any > information. It will be very useful to provide addition info like message and > stacktrace. > JUnit reporter correctly provide ignore message from "Ignore" annotation so > we can similarly provide message from SkipException. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
