[jira] [Updated] (MPLUGIN-326) Remove timestamp in generated descriptor
[
https://issues.apache.org/jira/browse/MPLUGIN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPLUGIN-326:
--
Description:
maven-plugin-tools-generator adds (in PluginDescriptorGenerator.java) the
following comment line in {{META-INF/maven/plugin.xml}} and {{plugin-help.xml}}
descriptors: "
> Key: MPLUGIN-326
> URL: https://issues.apache.org/jira/browse/MPLUGIN-326
> Project: Maven Plugin Tools
> Issue Type: Improvement
>Reporter: Zlika
>Priority: Trivial
> Fix For: 3.5.1
>
>
> maven-plugin-tools-generator adds (in PluginDescriptorGenerator.java) the
> following comment line in {{META-INF/maven/plugin.xml}} and
> {{plugin-help.xml}} descriptors:
[jira] [Updated] (MPLUGIN-326) Remove timestamp in generated descriptor
[
https://issues.apache.org/jira/browse/MPLUGIN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPLUGIN-326:
--
Description:
maven-plugin-tools-generator adds (in PluginDescriptorGenerator.java) the
following comment line in {{META-INF/maven/plugin.xml}} and {{plugin-help.xml}}
descriptors: {{
> Key: MPLUGIN-326
> URL: https://issues.apache.org/jira/browse/MPLUGIN-326
> Project: Maven Plugin Tools
> Issue Type: Improvement
>Reporter: Zlika
>Priority: Trivial
> Fix For: 3.5.1
>
>
> maven-plugin-tools-generator adds (in PluginDescriptorGenerator.java) the
> following comment line in {{META-INF/maven/plugin.xml}} and
> {{plugin-help.xml}} descriptors:
[jira] [Updated] (MPLUGIN-326) Remove timestamp in generated descriptor
[ https://issues.apache.org/jira/browse/MPLUGIN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPLUGIN-326: -- Fix Version/s: 3.5.1 > Remove timestamp in generated descriptor > > > Key: MPLUGIN-326 > URL: https://issues.apache.org/jira/browse/MPLUGIN-326 > Project: Maven Plugin Tools > Issue Type: Improvement >Reporter: Zlika >Priority: Trivial > Fix For: 3.5.1 > > > maven-plugin-tools-generator adds (in PluginDescriptorGenerator.java) the > following comment line in plugin.xml and plugin-help.xml descriptors:
[jira] [Updated] (MPLUGIN-330) If and else-if branches has the same condition
[
https://issues.apache.org/jira/browse/MPLUGIN-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPLUGIN-330:
--
Fix Version/s: 3.5.1
> If and else-if branches has the same condition
> --
>
> Key: MPLUGIN-330
> URL: https://issues.apache.org/jira/browse/MPLUGIN-330
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5
>Reporter: songwanging
>Priority: Minor
> Fix For: 3.5.1
>
>
> Our tool DeepTect has detected a piece of buggy code snippet, in which the if
> and else branches has the same condition.
> Path:
> maven-plugin-tools/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.java
> {code:java}
> public void execute(){
> ...
> Set requestDependencies;
> if ( mojoDependencies == null )
> {
> requestDependencies = dependencies;
> }
> else if ( mojoDependencies == null )
> {
> requestDependencies = null;
> }
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188
[
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPLUGIN-328:
--
Fix Version/s: 3.5.1
> ArrayIndexOutOfBoundsException: 48188
> --
>
> Key: MPLUGIN-328
> URL: https://issues.apache.org/jira/browse/MPLUGIN-328
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5
> Environment:
> :\Users\fandre\Documents\MXW\MI\MI-4.1.1\Installer>C:\ASF\apache-maven-3.5.0\bin\mvn
> -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T21:39:06+02:00)
> Maven home: C:\ASF\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_141\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
> Fix For: 3.5.1
>
> Attachments: MPLUGIN_328_ArrayIndexOutOfBoundsException__48188.patch,
> plugin.zip, pom.xml
>
>
> Hi
> Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an
> empty execution element
> {code:xml}
>
> maven-plugin-plugin
> 3.5
>
> {code}
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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.PluginExecutionException: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 48188
> at org.objectweb.asm.ClassReader.readClass(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:215)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scanArchive(DefaultMojoAnnotationsScanner.java:145)
> at
>
[jira] [Updated] (MPLUGIN-331) Check the existence of plugin.xml rather than project packaging in PluginReport.canGenerateReport()
[
https://issues.apache.org/jira/browse/MPLUGIN-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPLUGIN-331:
--
Fix Version/s: 3.5.1
> Check the existence of plugin.xml rather than project packaging in
> PluginReport.canGenerateReport()
> ---
>
> Key: MPLUGIN-331
> URL: https://issues.apache.org/jira/browse/MPLUGIN-331
> Project: Maven Plugin Tools
> Issue Type: Task
> Components: Plugin Plugin
>Reporter: Peter Palaga
> Fix For: 3.5.1
>
>
> {{org.apache.maven.plugin.plugin.PluginReport.canGenerateReport()}} currently
> reads
> {code}
> return "maven-plugin".equals( project.getPackaging() );
> {code}
> I propose to change it to
> {code}
> return "maven-plugin".equals( project.getPackaging() )
> || "takari-maven-plugin".equals( project.getPackaging() );
> {code}
> so that also takari-maven-plugins are supported.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188
[
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MPLUGIN-328:
--
Description:
Hi
Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an
empty execution element
{code:xml}
maven-plugin-plugin
3.5
{code}
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
(default-descriptor) on project scortes-maven-plugin: Execution
default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
(default-descriptor) on project scortes-maven-plugin: Execution
default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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.PluginExecutionException: Execution
default-descriptor of goal
org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 48188
at org.objectweb.asm.ClassReader.readClass(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:215)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scanArchive(DefaultMojoAnnotationsScanner.java:145)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:112)
at
org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scan(DefaultMojoAnnotationsScanner.java:79)
at
org.apache.maven.tools.plugin.extractor.annotations.JavaAnnotationsMojoDescriptorExtractor.scanAnnotations(JavaAnnotationsMojoDescriptorExtractor.java:124)
at
org.apache.maven.tools.plugin.extractor.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:103)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:283)
at
org.apache.maven.plugin.plugin.DescriptorGeneratorMojo.execute(DescriptorGeneratorMojo.java:90)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following
[jira] [Created] (MNG-6334) Maven not processing custom annotation
amara jayaseelan created MNG-6334: - Summary: Maven not processing custom annotation Key: MNG-6334 URL: https://issues.apache.org/jira/browse/MNG-6334 Project: Maven Issue Type: Bug Affects Versions: 3.6.0 Environment: windows, java jdk 1.7 Reporter: amara jayaseelan Attachments: Handleable.java, HandleableProcessor.java, annotationconsumer.java Maven is not processing annotations defined in my file. A class is supposed to be generated and it is not generated. First noticed while compiling netbeans code where annotation processors are used with ant build. As per docs, no special plugins are needed for annotations to be processed. However, the annotation is not getting processed. Also it is supposed to occur before the compilation so the generated classes can be referred to in the code directly even though they havent been generated yet. This could be a useful feature. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription
[
https://issues.apache.org/jira/browse/SUREFIRE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310522#comment-16310522
]
Hudson commented on SUREFIRE-1372:
--
FAILURE: Integrated in Jenkins build maven-surefire #1816 (See
[https://builds.apache.org/job/maven-surefire/1816/])
[SUREFIRE-1372] Rerunning failing tests fails in combination with (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=0a81c48971e3ee4b79b0858be7b8f4b13ece7287])
* (edit) maven-surefire-plugin/src/site/site.xml
* (add) maven-surefire-plugin/src/site/apt/examples/cucumber.apt.vm
* (edit)
surefire-providers/common-junit4/src/main/java/org/apache/maven/surefire/common/junit4/JUnit4ProviderUtil.java
* (add)
surefire-integration-tests/src/test/resources/junit47-rerun-failing-tests-with-cucumber/src/test/java/org/sample/cucumber/FlakeCucumberTest.java
* (edit)
surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/JUnitCoreProvider.java
* (add)
surefire-integration-tests/src/test/resources/junit47-rerun-failing-tests-with-cucumber/src/test/resources/org/sample/cucumber/Sample.feature
* (add)
surefire-providers/common-junit4/src/main/java/org/apache/maven/surefire/common/junit4/MatchDescriptions.java
* (delete)
surefire-providers/common-junit48/src/main/java/org/apache/maven/surefire/common/junit48/FailingMethodFilter.java
* (edit) maven-surefire-plugin/src/site/apt/examples/rerun-failing-tests.apt.vm
* (edit)
surefire-providers/surefire-junit4/src/main/java/org/apache/maven/surefire/junit4/JUnit4Provider.java
* (add)
surefire-integration-tests/src/test/resources/junit47-rerun-failing-tests-with-cucumber/src/test/java/org/sample/cucumber/StepDefs.java
* (edit)
surefire-providers/common-junit4/src/test/java/org/apache/maven/surefire/common/junit4/JUnit4ProviderUtilTest.java
* (add)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/JUnit47RerunFailingTestWithCucumberIT.java
* (add)
surefire-integration-tests/src/test/resources/junit47-rerun-failing-tests-with-cucumber/pom.xml
* (edit)
surefire-providers/common-junit48/src/main/java/org/apache/maven/surefire/common/junit48/FilterFactory.java
> Rerunning failing tests fails in combination with
> Description#createSuiteDescription
>
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> When using surefire to rerun failing tests created by a Runner that uses
> {noformat}Description#createSuiteDescription{noformat} with a human readable
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create
> test class 'Scenario: Fail when running'
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription
[
https://issues.apache.org/jira/browse/SUREFIRE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1372.
--
Resolution: Fixed
https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=0a81c48971e3ee4b79b0858be7b8f4b13ece7287
> Rerunning failing tests fails in combination with
> Description#createSuiteDescription
>
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
> Fix For: 2.21.0.Jigsaw
>
>
> When using surefire to rerun failing tests created by a Runner that uses
> {noformat}Description#createSuiteDescription{noformat} with a human readable
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create
> test class 'Scenario: Fail when running'
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310472#comment-16310472 ] Hudson commented on SUREFIRE-1416: -- SUCCESS: Integrated in Jenkins build maven-surefire #1815 (See [https://builds.apache.org/job/maven-surefire/1815/]) [SUREFIRE-1416] maven-surefire-parser: add new method isError in (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=869d6f29ff81bf2116a118f8118b63f21de4aa8a]) * (edit) surefire-report-parser/src/test/java/org/apache/maven/plugins/surefire/report/SurefireReportParserTest.java * (edit) surefire-report-parser/src/main/java/org/apache/maven/plugins/surefire/report/ReportTestSuite.java * (edit) surefire-report-parser/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java * (edit) maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java * (edit) surefire-report-parser/src/test/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParserTest.java * (edit) surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire260TestWithIdenticalNamesIT.java * (edit) surefire-report-parser/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportParser.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/StatelessXmlReporter.java * (edit) surefire-report-parser/src/main/java/org/apache/maven/plugins/surefire/report/ReportTestCase.java * (edit) maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/Surefire597Test.java > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310450#comment-16310450 ] ASF GitHub Bot commented on SUREFIRE-1416: -- Github user surli closed the pull request at: https://github.com/apache/maven-surefire/pull/143 > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] maven-surefire pull request #143: [SUREFIRE-1416] maven-surefire-parser: add...
Github user surli closed the pull request at: https://github.com/apache/maven-surefire/pull/143 ---
[jira] [Updated] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188
[
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Heid updated MPLUGIN-328:
Attachment: MPLUGIN_328_ArrayIndexOutOfBoundsException__48188.patch
> ArrayIndexOutOfBoundsException: 48188
> --
>
> Key: MPLUGIN-328
> URL: https://issues.apache.org/jira/browse/MPLUGIN-328
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5
> Environment:
> :\Users\fandre\Documents\MXW\MI\MI-4.1.1\Installer>C:\ASF\apache-maven-3.5.0\bin\mvn
> -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T21:39:06+02:00)
> Maven home: C:\ASF\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_141\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
> Attachments: MPLUGIN_328_ArrayIndexOutOfBoundsException__48188.patch,
> plugin.zip, pom.xml
>
>
> Hi
> Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an
> empty execution element
> {code:java}
> maven-plugin-plugin
> 3.5
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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.PluginExecutionException: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 48188
> at org.objectweb.asm.ClassReader.readClass(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:215)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.scanArchive(DefaultMojoAnnotationsScanner.java:145)
> at
>
[jira] [Commented] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188
[
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310432#comment-16310432
]
Daniel Heid commented on MPLUGIN-328:
-
I changed the default annotation scanner to just print a warning in case a
class could not be analyzed. This should not let a build fail. In my case, I
added a dependency compiled with AspectJ and that leads to a build interruption.
> ArrayIndexOutOfBoundsException: 48188
> --
>
> Key: MPLUGIN-328
> URL: https://issues.apache.org/jira/browse/MPLUGIN-328
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5
> Environment:
> :\Users\fandre\Documents\MXW\MI\MI-4.1.1\Installer>C:\ASF\apache-maven-3.5.0\bin\mvn
> -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T21:39:06+02:00)
> Maven home: C:\ASF\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_141\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
> Attachments: plugin.zip, pom.xml
>
>
> Hi
> Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an
> empty execution element
> {code:java}
> maven-plugin-plugin
> 3.5
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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.PluginExecutionException: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 48188
> at org.objectweb.asm.ClassReader.readClass(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at org.objectweb.asm.ClassReader.accept(Unknown Source)
> at
> org.apache.maven.tools.plugin.extractor.annotations.scanner.DefaultMojoAnnotationsScanner.analyzeClassStream(DefaultMojoAnnotationsScanner.java:215)
> at
>
[jira] [Commented] (MPLUGIN-328) ArrayIndexOutOfBoundsException: 48188
[
https://issues.apache.org/jira/browse/MPLUGIN-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310429#comment-16310429
]
ASF GitHub Bot commented on MPLUGIN-328:
dheid opened a new pull request #11: MPLUGIN-328
ArrayIndexOutOfBoundsException: 48188
URL: https://github.com/apache/maven-plugin-tools/pull/11
If a dependency contains a class that could not be read by the default mojo
annotation scanner, Maven will fail. Especially classes compiled using AspectJ
are affected. Please consider merging this pull request, as it just lets Maven
print a warning and won't let it interrupt the build process.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> ArrayIndexOutOfBoundsException: 48188
> --
>
> Key: MPLUGIN-328
> URL: https://issues.apache.org/jira/browse/MPLUGIN-328
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.5
> Environment:
> :\Users\fandre\Documents\MXW\MI\MI-4.1.1\Installer>C:\ASF\apache-maven-3.5.0\bin\mvn
> -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T21:39:06+02:00)
> Maven home: C:\ASF\apache-maven-3.5.0\bin\..
> Java version: 1.8.0_141, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_141\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: zosrothko
> Attachments: plugin.zip, pom.xml
>
>
> Hi
> Got a ArrayIndexOutOfBoundsException on the maven-plugin-plugin:3.5 with an
> empty execution element
> {code:java}
> maven-plugin-plugin
> 3.5
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor
> (default-descriptor) on project scortes-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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.PluginExecutionException: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.5:descriptor failed: 48188
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
>
[GitHub] dheid opened a new pull request #11: MPLUGIN-328 ArrayIndexOutOfBoundsException: 48188
dheid opened a new pull request #11: MPLUGIN-328 ArrayIndexOutOfBoundsException: 48188 URL: https://github.com/apache/maven-plugin-tools/pull/11 If a dependency contains a class that could not be read by the default mojo annotation scanner, Maven will fail. Especially classes compiled using AspectJ are affected. Please consider merging this pull request, as it just lets Maven print a warning and won't let it interrupt the build process. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MCHANGES-317) GitHub: "API rate limit exceeded"
[ https://issues.apache.org/jira/browse/MCHANGES-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310375#comment-16310375 ] Ivan Fedotov commented on MCHANGES-317: --- Hi! In 2.12 version a Username/Password authentication was added, thank you! Can you add an OAuth2 token authentication, please? > GitHub: "API rate limit exceeded" > - > > Key: MCHANGES-317 > URL: https://issues.apache.org/jira/browse/MCHANGES-317 > Project: Maven Changes Plugin > Issue Type: Bug > Components: github >Affects Versions: 2.9 >Reporter: John Schneider > > I tried to generate a report and got this message: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project > stax-mate: Error during page generation: Error rendering Maven report: API > rate limit exceeded for 149.###.###.##. See > http://developer.github.com/v3/#rate-limiting for details. (403) -> [Help 1] > I think this is caused by having a low limit for unauthenticated requests. I > think it would be great if there was a way to authenticate... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9
[ https://issues.apache.org/jira/browse/SUREFIRE-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1450. -- Resolution: Fixed https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=869d6f29ff81bf2116a118f8118b63f21de4aa8a > TestNG Listener aren't working from Property Tag in POM.xml With JDK9 > - > > Key: SUREFIRE-1450 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1450 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG > support >Affects Versions: 2.20.1 > Environment: macOS + Ubuntu, JDK9 >Reporter: Hammad >Assignee: Tibor Digana > Labels: newbie > Fix For: 2.21.0.Jigsaw > > > TestNG Listener are not working when using: > Maven = Apache Maven 3.5.2 > JDK9 > Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire > I executed it with jdk8 in same environment listener did work, but they > aren't working with JDK9 > FYI: > https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SUREFIRE-1450) TestNG Listener aren't working from Property Tag in POM.xml With JDK9
[ https://issues.apache.org/jira/browse/SUREFIRE-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1450: --- Fix Version/s: 2.21.0.Jigsaw > TestNG Listener aren't working from Property Tag in POM.xml With JDK9 > - > > Key: SUREFIRE-1450 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1450 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, TestNG > support >Affects Versions: 2.20.1 > Environment: macOS + Ubuntu, JDK9 >Reporter: Hammad >Assignee: Tibor Digana > Labels: newbie > Fix For: 2.21.0.Jigsaw > > > TestNG Listener are not working when using: > Maven = Apache Maven 3.5.2 > JDK9 > Here is relevant repo: https://github.com/HammadHost/poc_testng_surefire > I executed it with jdk8 in same environment listener did work, but they > aren't working with JDK9 > FYI: > https://stackoverflow.com/questions/47560412/maven-surefire-is-not-respecting-testng-listeners-in-property-tag -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310350#comment-16310350 ] ASF GitHub Bot commented on SUREFIRE-1416: -- Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli Thx for contributing. Now you can close the PR. > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] maven-surefire issue #143: [SUREFIRE-1416] maven-surefire-parser: add new me...
Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli Thx for contributing. Now you can close the PR. ---
[jira] [Commented] (MSITE-806) Site generation does not work when no report configured nor Doxia document provided
[ https://issues.apache.org/jira/browse/MSITE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310184#comment-16310184 ] Peter Jeszenszky commented on MSITE-806: Thank you very much! > Site generation does not work when no report configured nor Doxia document > provided > --- > > Key: MSITE-806 > URL: https://issues.apache.org/jira/browse/MSITE-806 > Project: Maven Site Plugin > Issue Type: Bug >Affects Versions: 3.7 > Environment: Apache Maven 3.5.2 > (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T09:58:13+02:00) > Maven home: /opt/apache-maven-3.5.2 > Java version: 9.0.1, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-9-oracle > Default locale: hu_HU, platform encoding: UTF-8 > OS name: "linux", version: "3.13.0-37-generic", arch: "amd64", family: "unix" >Reporter: Peter Jeszenszky >Priority: Minor > Fix For: 3.7.1 > > Attachments: maven-hello.zip > > > Running "mvn site" results in a target/site/ directory without any HTML > files. The resulting directory contains only the css/ and the images/ > subdirectories. > I have attached a small project to reproduce the bug (?). Switching back to > version 3.6 of the plugin solves the problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310006#comment-16310006 ] ASF GitHub Bot commented on SUREFIRE-1416: -- Github user surli commented on the issue: https://github.com/apache/maven-surefire/pull/143 @Tibor17 I can confirm it's working for me and it's useful! See my PR https://github.com/Spirals-Team/librepair/pull/380 > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] maven-surefire issue #143: [SUREFIRE-1416] maven-surefire-parser: add new me...
Github user surli commented on the issue: https://github.com/apache/maven-surefire/pull/143 @Tibor17 I can confirm it's working for me and it's useful! See my PR https://github.com/Spirals-Team/librepair/pull/380 ---
[GitHub] maven-surefire issue #143: [SUREFIRE-1416] maven-surefire-parser: add new me...
Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli Pls try to use it in your projects. I want to know if it is useful for you and working. Thx. ---
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309784#comment-16309784 ] ASF GitHub Bot commented on SUREFIRE-1416: -- Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli Pls try to use it in your projects. I want to know if it is useful for you and working. Thx. > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MCHECKSTYLE-344) StringIndexOutOfBoundsException in RuleUtil
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309744#comment-16309744
]
richard commented on MCHECKSTYLE-344:
-
We hit this as well in sevntu at
https://travis-ci.org/sevntu-checkstyle/sevntu.checkstyle/jobs/324422086 .
{noformat}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: -1
at java.lang.String.substring (String.java:1967)
at org.apache.maven.plugin.checkstyle.RuleUtil.getCategory
(RuleUtil.java:95)
at
org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.countViolations
(CheckstyleViolationCheckMojo.java:651)
at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute
(CheckstyleViolationCheckMojo.java:576)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:134)
{noformat}
This is the result of a change in the XML file in Checkstyle starting with
version 8.2 at https://github.com/checkstyle/checkstyle/issues/4607 .
By giving a module a unique id, we changed the XML file to print the id as the
source instead of the full class name. This is why maven plugin is expecting a
period in the source.
> StringIndexOutOfBoundsException in RuleUtil
> ---
>
> Key: MCHECKSTYLE-344
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-344
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 2.17
>Reporter: fdvxxii
>
> {{RuleUtil}} has a bug at line 95:
> {code}
> final int end = eventSrcName.lastIndexOf('.');
> eventSrcName = eventSrcName.substring(0, end);
> {code}
> This code leads to a StringIndexOutOfBoundsException if the variable does not
> contain a period. I don't know if its a convention to have a period in that
> string, but either way the error message should me more expressive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MCHECKSTYLE-346) Release a new version
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309731#comment-16309731 ] richard commented on MCHECKSTYLE-346: - Robert Scholte Please release the plugin as it is now and let's close this issue. We will go from there by either opening new issues or pinging you on existing ones. Since we are new to the project, there will probably be questions we will be asking as we to try to help out. Thanks. > Release a new version > - > > Key: MCHECKSTYLE-346 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-346 > Project: Maven Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.17 > Environment: All >Reporter: richard >Priority: Blocker > > Hello, > Since my posts in another issue have gone unnoticed > (https://issues.apache.org/jira/browse/MCHECKSTYLE-332), I am creating this > one to bring it up front. > The main checkstyle community have been waiting years for a 2.18 release for > fixes and functionality needed. As it is now, we cannot remove old deprecated > code from our utility as the plugin relies on them too much and breaks if > they are removed which forces us to continue supporting them just for you. > See Issue: https://github.com/checkstyle/checkstyle/issues/2883 > The last release for maven checkstyle plugin was 2015, but you continue to > update the code base. Why is this? Is there something that prevents you from > creating a new release? Do you lack personnel of some kind? Is it possible to > give us a time table for a 2.18 release? > If things continue as they are now, we may begin looking into breaking > compatibility with the plugin in newer versions as this project seems to have > run stagnant and is lacking support. If compatibility is broken, the current > plugin released will then only work with old and outdated versions. I, and I > am sure the community, don't wish to see this happen but the checkstyle > utility needs to keep evolving and remove outdated code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309624#comment-16309624 ] ASF GitHub Bot commented on SUREFIRE-1416: -- Github user surli commented on the issue: https://github.com/apache/maven-surefire/pull/143 Hi @Tibor17 sorry I was off lately so I just saw your comments. I did not check what you asked before. I'm currently reviewing your code and it looks fine for me :) Thanks! > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] maven-surefire issue #143: [SUREFIRE-1416] maven-surefire-parser: add new me...
Github user surli commented on the issue: https://github.com/apache/maven-surefire/pull/143 Hi @Tibor17 sorry I was off lately so I just saw your comments. I did not check what you asked before. I'm currently reviewing your code and it looks fine for me :) Thanks! ---
[GitHub] maven-surefire issue #143: [SUREFIRE-1416] maven-surefire-parser: add new me...
Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli If there are no objections, I would push the branch SUREFIRE-1416 to master. Thx. ---
[jira] [Commented] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309622#comment-16309622 ] ASF GitHub Bot commented on SUREFIRE-1416: -- Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli If there are no objections, I would push the branch SUREFIRE-1416 to master. Thx. > maven-surefire-parser: add new method isError in ReportTestCase > --- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin >Reporter: Simon Urli >Assignee: Tibor Digana >Priority: Minor > Fix For: 2.21.0.Jigsaw > > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-39) deadlock during multithreaded dependency resolution
[ https://issues.apache.org/jira/browse/MRESOLVER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309584#comment-16309584 ] Zoltan Haindrich commented on MRESOLVER-39: --- [~stevestorey] Geat! I can confirm that issue is gone using maven-3.5.2 + pull/14 by using the same things I've used to locate the problem :) > deadlock during multithreaded dependency resolution > --- > > Key: MRESOLVER-39 > URL: https://issues.apache.org/jira/browse/MRESOLVER-39 > Project: Maven Resolver > Issue Type: Bug >Reporter: Zoltan Haindrich > > narrowed down a resolution problem to the commit ad50215 ; which belongs to > MRESOLVER-13 > Probably the changes in PartialFile might be the most relevant wrt to this > problem. > for stack traces, see MNG-6323, MNG-6324 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MRESOLVER-39) deadlock during multithreaded dependency resolution
[ https://issues.apache.org/jira/browse/MRESOLVER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309272#comment-16309272 ] Steve Storey commented on MRESOLVER-39: --- I've made a PR that fixes the problem for me: https://github.com/apache/maven-resolver/pull/14 (and comment on the PR includes instructions on how to test / apply to your own local install) > deadlock during multithreaded dependency resolution > --- > > Key: MRESOLVER-39 > URL: https://issues.apache.org/jira/browse/MRESOLVER-39 > Project: Maven Resolver > Issue Type: Bug >Reporter: Zoltan Haindrich > > narrowed down a resolution problem to the commit ad50215 ; which belongs to > MRESOLVER-13 > Probably the changes in PartialFile might be the most relevant wrt to this > problem. > for stack traces, see MNG-6323, MNG-6324 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
