[jira] [Commented] (SUREFIRE-1254) add color messages
[ https://issues.apache.org/jira/browse/SUREFIRE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437868#comment-15437868 ] Benno Markiewicz commented on SUREFIRE-1254: Disabling the coloring when running in batch-mode?! That makes sense. Thanks for the feedback! > add color messages > -- > > Key: SUREFIRE-1254 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1254 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Hervé Boutemy >Assignee: Tibor Digana > Fix For: 2.19.2 > > > with MNG-3507 fixed, adding colors to tests results would improve readability -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1254) add color messages
[ https://issues.apache.org/jira/browse/SUREFIRE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437798#comment-15437798 ] Benno Markiewicz commented on SUREFIRE-1254: Please make it optional and disabled by default. Else you will break external tools like Jenkins/NetBeans, which parse the output of the surefire-plugin. Their regex patterns won't match anymore. > add color messages > -- > > Key: SUREFIRE-1254 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1254 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Hervé Boutemy >Assignee: Tibor Digana > Fix For: 2.19.2 > > > with MNG-3507 fixed, adding colors to tests results would improve readability -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1216) TEST-*.xml files generated by Surefire are invalid
[
https://issues.apache.org/jira/browse/SUREFIRE-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437765#comment-15437765
]
Benno Markiewicz commented on SUREFIRE-1216:
FYI: NetBeans IDE has also troubles integrating the test result using 2.19.1
https://netbeans.org/bugzilla/show_bug.cgi?id=257563
> TEST-*.xml files generated by Surefire are invalid
> --
>
> Key: SUREFIRE-1216
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1216
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Mirko Friedenhagen
>Assignee: Mirko Friedenhagen
> Fix For: 2.19.2
>
>
> See SUREFIRE-964 as well. The XML produced is invalid because
> {{schemaLocation}} *must* include two URIs, as outlined in
> [xmlschema-1|http://www.w3.org/TR/xmlschema-1/#schema-loc].
> Because of this, the Xerces parser fails in the Jenkins XUnit plugin and e.g.
> IntelliJ is not able to parse the file correctly.
> Suggested solution is to replace {{xsi:schemaLocation}} by
> {{xsi:noNamespaceSchemaLocation}}, which fixes this for the Unit plugin as
> well the file is parseable by IntelliJ.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] Commented: (MPIR-135) NPE if license URL is not defined
[ http://jira.codehaus.org/browse/MPIR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=154572#action_154572 ] Benno Markiewicz commented on MPIR-135: --- The reason is the comparison using a null string. Line 156: Actual: if ( urlValidator.isValid( url ) || url.startsWith( file:// ) ) Fix if ( urlValidator.isValid( url ) || StringUtils.defaultString(url).startsWith( file:// ) ) NPE if license URL is not defined - Key: MPIR-135 URL: http://jira.codehaus.org/browse/MPIR-135 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: license Affects Versions: 2.1 Environment: maven 2.0.9 java 1.5 Reporter: Andreas Höhmann [INFO] [site:site] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.report.projectinfo.LicenseReport.getLicenseURL(LicenseReport.java:156) at org.apache.maven.report.projectinfo.LicenseReport.canGenerateReport(LicenseReport.java:114) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.filterReports(AbstractSiteRenderingMojo.java:177) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:81) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:49 9) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:585) $ 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) [INFO] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
