[jira] [Commented] (MNG-6428) IT for MNG-5958 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532258#comment-16532258
]
Hudson commented on MNG-6428:
-
Build failed in Jenkins: Maven TLP » maven » build-java8 #4
See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/
> IT for MNG-5958 fails on Java 9+
>
>
> Key: MNG-6428
> URL: https://issues.apache.org/jira/browse/MNG-6428
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The failure lies in the parsing of the error log. It expects:
> {noformat}
> verifier.verifyTextInLog( "[ERROR] Internal error:
> java.lang.ClassCastException: "
> + "org.apache.maven.lifecycle.mapping.LifecyclePhase cannot
> be cast to java.lang.String -> [Help 1]" );
> {noformat}
> while Java 9+ includes the module name:
> {noformat}
> [ERROR] Internal error: java.lang.ClassCastException:
> org.apache.maven.lifecycle.mapping.LifecyclePhase cannot be cast to
> java.base/java.lang.String -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-5958) java.lang.String cannot be cast to org.apache.maven.lifecycle.mapping.LifecyclePhase
[
https://issues.apache.org/jira/browse/MNG-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532259#comment-16532259
]
Hudson commented on MNG-5958:
-
Build failed in Jenkins: Maven TLP » maven » build-java8 #4
See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
>
>
> Key: MNG-5958
> URL: https://issues.apache.org/jira/browse/MNG-5958
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.3.9
> Environment: win 8.1
>Reporter: Meytal Genah
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> Our app uses flex mojo.
> We upgraded from Maven 3.3.3 to Maven 3.3.9 and when building we get:
> {noformat}[ERROR] Internal error: java.lang.ClassCastException:
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhas
> e
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:497)
> 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: java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:119)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:64)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:451)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:421)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:620)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:411)
> at
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> ... 11 more{noformat}
> I didn’t see anyone encountering the same problem. Maybe it is related to the
> fix of https://issues.apache.org/jira/browse/MNG-5805.
> Also, according to the stack trace, the invalid casting is in this line:
> {code:java}LifecyclePhase goals =
> goalsForLifecyclePhase.getValue();{code}
> this is the content of the pom.xml:
> {code:xml}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.myapp.plugin
> GUI
> trunk
>
>
[jira] [Commented] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
[
https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532253#comment-16532253
]
Hudson commented on MNG-5940:
-
Build failed in Jenkins: Maven TLP » maven » build-java8 #4
See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/
> Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
> ---
>
> Key: MNG-5940
> URL: https://issues.apache.org/jira/browse/MNG-5940
> Project: Maven
> Issue Type: Improvement
> Components: core
>Reporter: Karl Heinz Marbaise
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.4
>
>
> At the moment the {{maven-source-plugin:jar}} goal is defined in the Maven
> super pom:
> {code:xml}
>
> true
> maven-source-plugin
>
>
> attach-sources
>
> jar
>
>
>
>
> {code}
> where the goal of {{maven-source-plugin}} should be changed from {{jar}} into
> {{jar-no-fork}}, cause most of the time you need to override this behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6427) IT for MNG-1957 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532256#comment-16532256
]
Hudson commented on MNG-6427:
-
Build failed in Jenkins: Maven TLP » maven » build-java8 #4
See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/
> IT for MNG-1957 fails on Java 9+
>
>
> Key: MNG-6427
> URL: https://issues.apache.org/jira/browse/MNG-6427
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The execution fails with:
> {noformat}
> junit.framework.ComparisonFailure: expected: but was:
> at
> org.apache.maven.it.MavenITmng1957JdkActivationWithVersionRangeTest.testitMNG1957(MavenITmng1957JdkActivationWithVersionRangeTest.java:64)
> {noformat}
> This is caused by incorrect JDK ranges in the {{pom.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6426) IT for MNG-6127 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532254#comment-16532254
]
Hudson commented on MNG-6426:
-
Build failed in Jenkins: Maven TLP » maven » build-java8 #4
See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/
> IT for MNG-6127 fails on Java 9+
>
>
> Key: MNG-6426
> URL: https://issues.apache.org/jira/browse/MNG-6426
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> Failure on Java 10 in Windows:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project mng-6127-plugin: Compilation failure
> [ERROR]
> /D:/Entwicklung/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6127-plugin-execution-configuration-interference/plugin/src/main/java/org/apache/maven/its/mng6127/plugin/TestMojo.java:[67,13]
> try-with-resources is not supported in -source 6
> [ERROR] (use -source 7 or higher to enable try-with-resources)
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project mng-6127-plugin: Compilation failure
> {noformat}
> The compiled plugin uses Java 7, but the code introduced in
> ee3cae93ce70f9ff1898b5c10f3cce59898923af autoresets everything to 1.6.
> Drop all occurencies of {{maven.compiler.*}} and remove the
> try-with-resources statement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-1957) clause in the activation section has to provide more complex expressions.
[ https://issues.apache.org/jira/browse/MNG-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532257#comment-16532257 ] Hudson commented on MNG-1957: - Build failed in Jenkins: Maven TLP » maven » build-java8 #4 See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/ > clause in the activation section has to provide more complex > expressions. > - > > Key: MNG-1957 > URL: https://issues.apache.org/jira/browse/MNG-1957 > Project: Maven > Issue Type: Improvement > Components: POM >Affects Versions: 2.0, 2.0.1 >Reporter: Trustin Lee >Assignee: Brett Porter >Priority: Major > Fix For: 2.1.0 > > Attachments: MNG-1957-maven-project.patch > > > For now, provides only one operator '!' which means negation, but > it would be great if i can use '+' and ~ operator: > 1.5+ > 1.1 ~ 1.4 > ~ 1.3 > 1.4 ~ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532255#comment-16532255 ] Hudson commented on MNG-6127: - Build failed in Jenkins: Maven TLP » maven » build-java8 #4 See https://builds.apache.org/job/maven-box/job/maven/job/build-java8/4/ > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Robert Scholte >Priority: Major > Fix For: 3.5.2 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6427) IT for MNG-1957 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532241#comment-16532241
]
Hudson commented on MNG-6427:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/
> IT for MNG-1957 fails on Java 9+
>
>
> Key: MNG-6427
> URL: https://issues.apache.org/jira/browse/MNG-6427
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The execution fails with:
> {noformat}
> junit.framework.ComparisonFailure: expected: but was:
> at
> org.apache.maven.it.MavenITmng1957JdkActivationWithVersionRangeTest.testitMNG1957(MavenITmng1957JdkActivationWithVersionRangeTest.java:64)
> {noformat}
> This is caused by incorrect JDK ranges in the {{pom.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6428) IT for MNG-5958 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532243#comment-16532243
]
Hudson commented on MNG-6428:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/
> IT for MNG-5958 fails on Java 9+
>
>
> Key: MNG-6428
> URL: https://issues.apache.org/jira/browse/MNG-6428
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The failure lies in the parsing of the error log. It expects:
> {noformat}
> verifier.verifyTextInLog( "[ERROR] Internal error:
> java.lang.ClassCastException: "
> + "org.apache.maven.lifecycle.mapping.LifecyclePhase cannot
> be cast to java.lang.String -> [Help 1]" );
> {noformat}
> while Java 9+ includes the module name:
> {noformat}
> [ERROR] Internal error: java.lang.ClassCastException:
> org.apache.maven.lifecycle.mapping.LifecyclePhase cannot be cast to
> java.base/java.lang.String -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
[
https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532245#comment-16532245
]
Hudson commented on MNG-5940:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/
> Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
> ---
>
> Key: MNG-5940
> URL: https://issues.apache.org/jira/browse/MNG-5940
> Project: Maven
> Issue Type: Improvement
> Components: core
>Reporter: Karl Heinz Marbaise
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.4
>
>
> At the moment the {{maven-source-plugin:jar}} goal is defined in the Maven
> super pom:
> {code:xml}
>
> true
> maven-source-plugin
>
>
> attach-sources
>
> jar
>
>
>
>
> {code}
> where the goal of {{maven-source-plugin}} should be changed from {{jar}} into
> {{jar-no-fork}}, cause most of the time you need to override this behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6426) IT for MNG-6127 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532246#comment-16532246
]
Hudson commented on MNG-6426:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/
> IT for MNG-6127 fails on Java 9+
>
>
> Key: MNG-6426
> URL: https://issues.apache.org/jira/browse/MNG-6426
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> Failure on Java 10 in Windows:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project mng-6127-plugin: Compilation failure
> [ERROR]
> /D:/Entwicklung/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6127-plugin-execution-configuration-interference/plugin/src/main/java/org/apache/maven/its/mng6127/plugin/TestMojo.java:[67,13]
> try-with-resources is not supported in -source 6
> [ERROR] (use -source 7 or higher to enable try-with-resources)
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project mng-6127-plugin: Compilation failure
> {noformat}
> The compiled plugin uses Java 7, but the code introduced in
> ee3cae93ce70f9ff1898b5c10f3cce59898923af autoresets everything to 1.6.
> Drop all occurencies of {{maven.compiler.*}} and remove the
> try-with-resources statement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-1957) clause in the activation section has to provide more complex expressions.
[ https://issues.apache.org/jira/browse/MNG-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532249#comment-16532249 ] Hudson commented on MNG-1957: - Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/ > clause in the activation section has to provide more complex > expressions. > - > > Key: MNG-1957 > URL: https://issues.apache.org/jira/browse/MNG-1957 > Project: Maven > Issue Type: Improvement > Components: POM >Affects Versions: 2.0, 2.0.1 >Reporter: Trustin Lee >Assignee: Brett Porter >Priority: Major > Fix For: 2.1.0 > > Attachments: MNG-1957-maven-project.patch > > > For now, provides only one operator '!' which means negation, but > it would be great if i can use '+' and ~ operator: > 1.5+ > 1.1 ~ 1.4 > ~ 1.3 > 1.4 ~ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5958) java.lang.String cannot be cast to org.apache.maven.lifecycle.mapping.LifecyclePhase
[
https://issues.apache.org/jira/browse/MNG-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532251#comment-16532251
]
Hudson commented on MNG-5958:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
>
>
> Key: MNG-5958
> URL: https://issues.apache.org/jira/browse/MNG-5958
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.3.9
> Environment: win 8.1
>Reporter: Meytal Genah
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> Our app uses flex mojo.
> We upgraded from Maven 3.3.3 to Maven 3.3.9 and when building we get:
> {noformat}[ERROR] Internal error: java.lang.ClassCastException:
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhas
> e
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:497)
> 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: java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:119)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:64)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:451)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:421)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:620)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:411)
> at
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> ... 11 more{noformat}
> I didn’t see anyone encountering the same problem. Maybe it is related to the
> fix of https://issues.apache.org/jira/browse/MNG-5805.
> Also, according to the stack trace, the invalid casting is in this line:
> {code:java}LifecyclePhase goals =
> goalsForLifecyclePhase.getValue();{code}
> this is the content of the pom.xml:
> {code:xml}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.myapp.plugin
> GUI
> trunk
>
>
[jira] [Commented] (MNG-5958) java.lang.String cannot be cast to org.apache.maven.lifecycle.mapping.LifecyclePhase
[
https://issues.apache.org/jira/browse/MNG-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532244#comment-16532244
]
Hudson commented on MNG-5958:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
>
>
> Key: MNG-5958
> URL: https://issues.apache.org/jira/browse/MNG-5958
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.3.9
> Environment: win 8.1
>Reporter: Meytal Genah
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> Our app uses flex mojo.
> We upgraded from Maven 3.3.3 to Maven 3.3.9 and when building we get:
> {noformat}[ERROR] Internal error: java.lang.ClassCastException:
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhas
> e
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:497)
> 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: java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:119)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:64)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:451)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:421)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:620)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:411)
> at
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> ... 11 more{noformat}
> I didn’t see anyone encountering the same problem. Maybe it is related to the
> fix of https://issues.apache.org/jira/browse/MNG-5805.
> Also, according to the stack trace, the invalid casting is in this line:
> {code:java}LifecyclePhase goals =
> goalsForLifecyclePhase.getValue();{code}
> this is the content of the pom.xml:
> {code:xml}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.myapp.plugin
> GUI
> trunk
>
>
[jira] [Commented] (MNG-6426) IT for MNG-6127 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532239#comment-16532239
]
Hudson commented on MNG-6426:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/
> IT for MNG-6127 fails on Java 9+
>
>
> Key: MNG-6426
> URL: https://issues.apache.org/jira/browse/MNG-6426
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> Failure on Java 10 in Windows:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project mng-6127-plugin: Compilation failure
> [ERROR]
> /D:/Entwicklung/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6127-plugin-execution-configuration-interference/plugin/src/main/java/org/apache/maven/its/mng6127/plugin/TestMojo.java:[67,13]
> try-with-resources is not supported in -source 6
> [ERROR] (use -source 7 or higher to enable try-with-resources)
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project mng-6127-plugin: Compilation failure
> {noformat}
> The compiled plugin uses Java 7, but the code introduced in
> ee3cae93ce70f9ff1898b5c10f3cce59898923af autoresets everything to 1.6.
> Drop all occurencies of {{maven.compiler.*}} and remove the
> try-with-resources statement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532247#comment-16532247 ] Hudson commented on MNG-6127: - Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/ > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Robert Scholte >Priority: Major > Fix For: 3.5.2 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
[
https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532238#comment-16532238
]
Hudson commented on MNG-5940:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/
> Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
> ---
>
> Key: MNG-5940
> URL: https://issues.apache.org/jira/browse/MNG-5940
> Project: Maven
> Issue Type: Improvement
> Components: core
>Reporter: Karl Heinz Marbaise
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.4
>
>
> At the moment the {{maven-source-plugin:jar}} goal is defined in the Maven
> super pom:
> {code:xml}
>
> true
> maven-source-plugin
>
>
> attach-sources
>
> jar
>
>
>
>
> {code}
> where the goal of {{maven-source-plugin}} should be changed from {{jar}} into
> {{jar-no-fork}}, cause most of the time you need to override this behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6428) IT for MNG-5958 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532250#comment-16532250
]
Hudson commented on MNG-6428:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/
> IT for MNG-5958 fails on Java 9+
>
>
> Key: MNG-6428
> URL: https://issues.apache.org/jira/browse/MNG-6428
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The failure lies in the parsing of the error log. It expects:
> {noformat}
> verifier.verifyTextInLog( "[ERROR] Internal error:
> java.lang.ClassCastException: "
> + "org.apache.maven.lifecycle.mapping.LifecyclePhase cannot
> be cast to java.lang.String -> [Help 1]" );
> {noformat}
> while Java 9+ includes the module name:
> {noformat}
> [ERROR] Internal error: java.lang.ClassCastException:
> org.apache.maven.lifecycle.mapping.LifecyclePhase cannot be cast to
> java.base/java.lang.String -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-1957) clause in the activation section has to provide more complex expressions.
[ https://issues.apache.org/jira/browse/MNG-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532242#comment-16532242 ] Hudson commented on MNG-1957: - Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/ > clause in the activation section has to provide more complex > expressions. > - > > Key: MNG-1957 > URL: https://issues.apache.org/jira/browse/MNG-1957 > Project: Maven > Issue Type: Improvement > Components: POM >Affects Versions: 2.0, 2.0.1 >Reporter: Trustin Lee >Assignee: Brett Porter >Priority: Major > Fix For: 2.1.0 > > Attachments: MNG-1957-maven-project.patch > > > For now, provides only one operator '!' which means negation, but > it would be great if i can use '+' and ~ operator: > 1.5+ > 1.1 ~ 1.4 > ~ 1.3 > 1.4 ~ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6427) IT for MNG-1957 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532248#comment-16532248
]
Hudson commented on MNG-6427:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6344 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6344/3/
> IT for MNG-1957 fails on Java 9+
>
>
> Key: MNG-6427
> URL: https://issues.apache.org/jira/browse/MNG-6427
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The execution fails with:
> {noformat}
> junit.framework.ComparisonFailure: expected: but was:
> at
> org.apache.maven.it.MavenITmng1957JdkActivationWithVersionRangeTest.testitMNG1957(MavenITmng1957JdkActivationWithVersionRangeTest.java:64)
> {noformat}
> This is caused by incorrect JDK ranges in the {{pom.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532240#comment-16532240 ] Hudson commented on MNG-6127: - Build failed in Jenkins: Maven TLP » maven » MNG-6391 #8 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6391/8/ > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Robert Scholte >Priority: Major > Fix For: 3.5.2 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MCOMPILER-347) Includes and excludes not passed into CompilerConfiguration
zhangchang created MCOMPILER-347:
Summary: Includes and excludes not passed into
CompilerConfiguration
Key: MCOMPILER-347
URL: https://issues.apache.org/jira/browse/MCOMPILER-347
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.5
Reporter: zhangchang
Some groovy script is only for runtime excute, other source need compile for
test.
So I set exclude in maven-compiler-plugin tag, but it not work.
{code:java}
...
maven-compiler-plugin
3.5
groovy-eclipse-compiler
**/rest/*
org.codehaus.groovy
groovy-eclipse-compiler
2.9.2-01
org.codehaus.groovy
groovy-eclipse-batch
2.4.3-01
...
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1532) MIME type for javascript is now officially application/javascript
[ https://issues.apache.org/jira/browse/SUREFIRE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532043#comment-16532043 ] ASF GitHub Bot commented on SUREFIRE-1532: -- Tibor17 commented on issue #188: [SUREFIRE-1532] MIME type for javascript is now officially application/javascript URL: https://github.com/apache/maven-surefire/pull/188#issuecomment-402314595 @based2 Please run the build locally. You will see this error `testWithIdenticalNames(org.apache.maven.surefire.its.jiras.Surefire260TestWithIdenticalNamesIT): ReferenceError: "toggleDisplay" is not defined. (javascript url#184)` I am not sure if this is the only one. Feel free to run the build like this `mvn install -P run-its`. See the README. There are instructions to use JDK8+. Do not worry if it takes one hour to complete. One hint, do not overload the PC with other tasks. The build has performance tests and if the delays are paused by overloaded CPU, other tests fail. Squash all changes in one commit. Thx 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 > MIME type for javascript is now officially application/javascript > - > > Key: SUREFIRE-1532 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1532 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Basile Chandesris >Priority: Minor > Labels: easyfix > > > ref [http://www.rfc-editor.org/rfc/rfc4329.txt > |http://www.rfc-editor.org/rfc/rfc4329.txt]Scripting Media Types > src > [https://stackoverflow.com/questions/189850/what-is-the-javascript-mime-type-for-the-type-attribute-of-a-script-tag] > "This is a common mistake. The MIME type for javascript wasn't standardized > for years. It's now officially: "application/javascript"." > github > https://github.com/apache/maven-surefire/pull/188#issuecomment-401559853 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Tibor17 commented on issue #188: [SUREFIRE-1532] MIME type for javascript is now officially application/javascript
Tibor17 commented on issue #188: [SUREFIRE-1532] MIME type for javascript is now officially application/javascript URL: https://github.com/apache/maven-surefire/pull/188#issuecomment-402314595 @based2 Please run the build locally. You will see this error `testWithIdenticalNames(org.apache.maven.surefire.its.jiras.Surefire260TestWithIdenticalNamesIT): ReferenceError: "toggleDisplay" is not defined. (javascript url#184)` I am not sure if this is the only one. Feel free to run the build like this `mvn install -P run-its`. See the README. There are instructions to use JDK8+. Do not worry if it takes one hour to complete. One hint, do not overload the PC with other tasks. The build has performance tests and if the delays are paused by overloaded CPU, other tests fail. Squash all changes in one commit. Thx 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] [Issue Comment Deleted] (SUREFIRE-1408) Surefire shows random tests failing with fork issue when one of the tests hangs
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sourabh Utkhade updated SUREFIRE-1408:
--
Comment: was deleted
(was: As we know that this issue is opened and blocking our tests can anyone
please suggest a way to bypass this issue and proceed with our tests? Please
note I am using JDK 1.10.)
> Surefire shows random tests failing with fork issue when one of the tests
> hangs
> ---
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> This was blocking 100% of test runs. Random tests were failing due to fork
> issue. Which made us really confused on what is happening. We tried a lot of
> options to fix this (fix memory,ulimits,sys.exit etc.)
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
>
[jira] [Commented] (SUREFIRE-1408) Surefire shows random tests failing with fork issue when one of the tests hangs
[
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532017#comment-16532017
]
Sourabh Utkhade commented on SUREFIRE-1408:
---
As we know that this issue is opened and blocking our tests can anyone please
suggest a way to bypass this issue and proceed with our tests? Please note I am
using JDK 1.10.
> Surefire shows random tests failing with fork issue when one of the tests
> hangs
> ---
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> This was blocking 100% of test runs. Random tests were failing due to fork
> issue. Which made us really confused on what is happening. We tried a lot of
> options to fix this (fix memory,ulimits,sys.exit etc.)
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE
> [28:40.637s]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
> /tmp/ambari_test_java/ambari-server/target/surefire
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR]
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server &&
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m
> -Xms1024m -jar
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
>
[jira] [Commented] (SUREFIRE-1532) MIME type for javascript is now officially application/javascript
[ https://issues.apache.org/jira/browse/SUREFIRE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531935#comment-16531935 ] ASF GitHub Bot commented on SUREFIRE-1532: -- Tibor17 commented on issue #188: [SUREFIRE-1532] MIME type for javascript is now officially application/javascript URL: https://github.com/apache/maven-surefire/pull/188#issuecomment-402294513 @based2 Let's wait for the response from CI https://builds.apache.org/job/maven-box/job/maven-surefire/job/1532/ 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 > MIME type for javascript is now officially application/javascript > - > > Key: SUREFIRE-1532 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1532 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Basile Chandesris >Priority: Minor > Labels: easyfix > > > ref [http://www.rfc-editor.org/rfc/rfc4329.txt > |http://www.rfc-editor.org/rfc/rfc4329.txt]Scripting Media Types > src > [https://stackoverflow.com/questions/189850/what-is-the-javascript-mime-type-for-the-type-attribute-of-a-script-tag] > "This is a common mistake. The MIME type for javascript wasn't standardized > for years. It's now officially: "application/javascript"." > github > https://github.com/apache/maven-surefire/pull/188#issuecomment-401559853 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Tibor17 commented on issue #188: [SUREFIRE-1532] MIME type for javascript is now officially application/javascript
Tibor17 commented on issue #188: [SUREFIRE-1532] MIME type for javascript is now officially application/javascript URL: https://github.com/apache/maven-surefire/pull/188#issuecomment-402294513 @based2 Let's wait for the response from CI https://builds.apache.org/job/maven-box/job/maven-surefire/job/1532/ 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] (MNG-6130) Loss of profile information in workaround for MNG-4900
[
https://issues.apache.org/jira/browse/MNG-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531870#comment-16531870
]
Michael Osipov commented on MNG-6130:
-
[~rfscholte], thanks for the analysis. {{DefaultProjectBuilder}} is out of my
knowledge. Any ideas how we can proceed here?
[~boris_brodski], can you make sure that all of the plugins you are using in
the faulty build are Maven 3+?
> Loss of profile information in workaround for MNG-4900
> --
>
> Key: MNG-6130
> URL: https://issues.apache.org/jira/browse/MNG-6130
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9, 3.5.0
> Environment: Windows
>Reporter: Boris Brodski
>Priority: Major
> Labels: easyfix, patch
> Fix For: waiting-for-feedback
>
> Attachments: MNG-6130.patch
>
>
> Please, forgive me not providing example project reproducing the bug.
> It's very tricky and hopefully not necessary, since the 1-line fix is
> provided.
> Using profiles together with maven-javadoc-plugin results in the following
> problem:
> - Configuration from active profiles is not considered during dependency
> resolution started problematically from the maven-javadoc-plugin.
> This leads to unpredictable behavior, that is somewhat hard to reproduce.
> Here is the technical inside and the 1-line fix:
> In the DefaultMavenProjectBuilder.toRequest():
> {noformat}
> if ( profileManager != null ) {
>...
> } else {
> ...
> /*
>* MNG-4900: Hack to workaround deficiency of legacy API which makes it
> impossible for plugins to access the
>* global profile manager which is required to build a POM like a CLI
> invocation does. Failure to consider
>* the activated profiles can cause repo declarations to be lost which in
> turn will result in artifact
>* resolution failures, in particular when using the enhanced local repo
> which guards access to local files
>* based on the configured remote repos.
>*/
> request.setActiveProfileIds( req.getActiveProfiles() );
> request.setInactiveProfileIds( req.getInactiveProfiles() );
> }
> {noformat}
> Here we copy active and inactive profile ids, but we don't copy the list of
> all profile ids. Missing line:
> {noformat}
> request.setProfiles( req.getProfiles() );
> {noformat}
> As the result the method DefaultProfileManager.getActiveProfiles() always
> returns an empty list:
> {noformat}
> List activeProfiles = new ArrayList<>( profiles.size() );
> for ( Profile profile : profiles ) {
> ...
> }
> return activeProfiles;
> {noformat}
> "profiles" here is empty, since it wasn't copied together with
> "getActiveProfiles()" and "getInactiveProfiles()"
> Adding the missing line fixes the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6130) Loss of profile information in workaround for MNG-4900
[
https://issues.apache.org/jira/browse/MNG-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531762#comment-16531762
]
Robert Scholte commented on MNG-6130:
-
{{DefaultMavenProjectBuilder}} is part of maven-compat, it is deprecated and
should only be used by Maven2 plugins. Instead plugins should use
{{DefaultProjectBuilder}}.
I prefer not to touch maven-compat, it is there only for compatibilty.
I'm kind of surprised that it is used, the maven-javadoc-plugin shouldn't use
it (latest is already Maven 3 only and doesn't use maven-compat), nor should
Maven.
So we should verify if this is an issue for {{DefaultProjectBuilder}}, in the
end that's the used implementation.
> Loss of profile information in workaround for MNG-4900
> --
>
> Key: MNG-6130
> URL: https://issues.apache.org/jira/browse/MNG-6130
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9, 3.5.0
> Environment: Windows
>Reporter: Boris Brodski
>Priority: Major
> Labels: easyfix, patch
> Fix For: waiting-for-feedback
>
> Attachments: MNG-6130.patch
>
>
> Please, forgive me not providing example project reproducing the bug.
> It's very tricky and hopefully not necessary, since the 1-line fix is
> provided.
> Using profiles together with maven-javadoc-plugin results in the following
> problem:
> - Configuration from active profiles is not considered during dependency
> resolution started problematically from the maven-javadoc-plugin.
> This leads to unpredictable behavior, that is somewhat hard to reproduce.
> Here is the technical inside and the 1-line fix:
> In the DefaultMavenProjectBuilder.toRequest():
> {noformat}
> if ( profileManager != null ) {
>...
> } else {
> ...
> /*
>* MNG-4900: Hack to workaround deficiency of legacy API which makes it
> impossible for plugins to access the
>* global profile manager which is required to build a POM like a CLI
> invocation does. Failure to consider
>* the activated profiles can cause repo declarations to be lost which in
> turn will result in artifact
>* resolution failures, in particular when using the enhanced local repo
> which guards access to local files
>* based on the configured remote repos.
>*/
> request.setActiveProfileIds( req.getActiveProfiles() );
> request.setInactiveProfileIds( req.getInactiveProfiles() );
> }
> {noformat}
> Here we copy active and inactive profile ids, but we don't copy the list of
> all profile ids. Missing line:
> {noformat}
> request.setProfiles( req.getProfiles() );
> {noformat}
> As the result the method DefaultProfileManager.getActiveProfiles() always
> returns an empty list:
> {noformat}
> List activeProfiles = new ArrayList<>( profiles.size() );
> for ( Profile profile : profiles ) {
> ...
> }
> return activeProfiles;
> {noformat}
> "profiles" here is empty, since it wasn't copied together with
> "getActiveProfiles()" and "getInactiveProfiles()"
> Adding the missing line fixes the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6130) Loss of profile information in workaround for MNG-4900
[
https://issues.apache.org/jira/browse/MNG-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531736#comment-16531736
]
Michael Osipov commented on MNG-6130:
-
[~boris_brodski], thank you for looking into this.I do really appreciate.
Please join IRC on freenode, #maven.
[~rfscholte], any idea how we can proceed here? The requester is unable to
strip down his issue. I don't want to reject hard work just because the IT is
too complex to build.
> Loss of profile information in workaround for MNG-4900
> --
>
> Key: MNG-6130
> URL: https://issues.apache.org/jira/browse/MNG-6130
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9, 3.5.0
> Environment: Windows
>Reporter: Boris Brodski
>Priority: Major
> Labels: easyfix, patch
> Fix For: waiting-for-feedback
>
> Attachments: MNG-6130.patch
>
>
> Please, forgive me not providing example project reproducing the bug.
> It's very tricky and hopefully not necessary, since the 1-line fix is
> provided.
> Using profiles together with maven-javadoc-plugin results in the following
> problem:
> - Configuration from active profiles is not considered during dependency
> resolution started problematically from the maven-javadoc-plugin.
> This leads to unpredictable behavior, that is somewhat hard to reproduce.
> Here is the technical inside and the 1-line fix:
> In the DefaultMavenProjectBuilder.toRequest():
> {noformat}
> if ( profileManager != null ) {
>...
> } else {
> ...
> /*
>* MNG-4900: Hack to workaround deficiency of legacy API which makes it
> impossible for plugins to access the
>* global profile manager which is required to build a POM like a CLI
> invocation does. Failure to consider
>* the activated profiles can cause repo declarations to be lost which in
> turn will result in artifact
>* resolution failures, in particular when using the enhanced local repo
> which guards access to local files
>* based on the configured remote repos.
>*/
> request.setActiveProfileIds( req.getActiveProfiles() );
> request.setInactiveProfileIds( req.getInactiveProfiles() );
> }
> {noformat}
> Here we copy active and inactive profile ids, but we don't copy the list of
> all profile ids. Missing line:
> {noformat}
> request.setProfiles( req.getProfiles() );
> {noformat}
> As the result the method DefaultProfileManager.getActiveProfiles() always
> returns an empty list:
> {noformat}
> List activeProfiles = new ArrayList<>( profiles.size() );
> for ( Profile profile : profiles ) {
> ...
> }
> return activeProfiles;
> {noformat}
> "profiles" here is empty, since it wasn't copied together with
> "getActiveProfiles()" and "getInactiveProfiles()"
> Adding the missing line fixes the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6130) Loss of profile information in workaround for MNG-4900
[
https://issues.apache.org/jira/browse/MNG-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531338#comment-16531338
]
Boris Brodski commented on MNG-6130:
Hello Michael, sure it would be awesome :)
I gave it another try. For about 3 days I tried really hard to isolate and
reproduce the problem. I gained more knowledge about to matter, but still was
unable to pinpoint it. Our build, that reproduces the problem is huge with lots
of modules, parent hierarchy, repos, m2 configuration and plugins. The error
hangs somehow together with javadoc plugin with a custom doclet + javadoc
dependencies of the 'eclipse-plugin' type. This dependency shouldn't exist
locally. Resolving it requires expanding property-variables, that doesn't work
correctly resulting in a corrupt URL exception. My problem is, that at some
point I can't reduce the project without loosing the error. Removing even
completely unrelated parts of the configuration prevents the error.
At the end I still have a huge project with many parents, custom m2
configuration, many repos and some plugins. Too large to build a regression
test out of it :(
If you would like to help me, we could chat on the matter. I'm very interested
in this bugfix being included into the upcoming release!
Thank you!
> Loss of profile information in workaround for MNG-4900
> --
>
> Key: MNG-6130
> URL: https://issues.apache.org/jira/browse/MNG-6130
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.3.9, 3.5.0
> Environment: Windows
>Reporter: Boris Brodski
>Priority: Major
> Labels: easyfix, patch
> Fix For: waiting-for-feedback
>
> Attachments: MNG-6130.patch
>
>
> Please, forgive me not providing example project reproducing the bug.
> It's very tricky and hopefully not necessary, since the 1-line fix is
> provided.
> Using profiles together with maven-javadoc-plugin results in the following
> problem:
> - Configuration from active profiles is not considered during dependency
> resolution started problematically from the maven-javadoc-plugin.
> This leads to unpredictable behavior, that is somewhat hard to reproduce.
> Here is the technical inside and the 1-line fix:
> In the DefaultMavenProjectBuilder.toRequest():
> {noformat}
> if ( profileManager != null ) {
>...
> } else {
> ...
> /*
>* MNG-4900: Hack to workaround deficiency of legacy API which makes it
> impossible for plugins to access the
>* global profile manager which is required to build a POM like a CLI
> invocation does. Failure to consider
>* the activated profiles can cause repo declarations to be lost which in
> turn will result in artifact
>* resolution failures, in particular when using the enhanced local repo
> which guards access to local files
>* based on the configured remote repos.
>*/
> request.setActiveProfileIds( req.getActiveProfiles() );
> request.setInactiveProfileIds( req.getInactiveProfiles() );
> }
> {noformat}
> Here we copy active and inactive profile ids, but we don't copy the list of
> all profile ids. Missing line:
> {noformat}
> request.setProfiles( req.getProfiles() );
> {noformat}
> As the result the method DefaultProfileManager.getActiveProfiles() always
> returns an empty list:
> {noformat}
> List activeProfiles = new ArrayList<>( profiles.size() );
> for ( Profile profile : profiles ) {
> ...
> }
> return activeProfiles;
> {noformat}
> "profiles" here is empty, since it wasn't copied together with
> "getActiveProfiles()" and "getInactiveProfiles()"
> Adding the missing line fixes the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6438) Continuous Delivery friendly versions do not work on root pom's parent
[
https://issues.apache.org/jira/browse/MNG-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16530884#comment-16530884
]
Konrad Windszus commented on MNG-6438:
--
[~khmarbaise] The documentation at
https://maven.apache.org/maven-ci-friendly.html does not explicitly state that
referencing a parent outside the reactor is not possible with those properties.
This would be very useful, e.g. when using your iterator-maven-plugin with goal
{{invoker}} https://github.com/khmarbaise/iterator-maven-plugin. When you
parameterize the parent version like this, releasing is a lot easier.
Is there any technical reason, why parent versions should not work in a similar
fashion?
> Continuous Delivery friendly versions do not work on root pom's parent
> --
>
> Key: MNG-6438
> URL: https://issues.apache.org/jira/browse/MNG-6438
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/local/Cellar/maven/3.5.3/libexec
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.5", arch: "x86_64", family: "mac"
>Reporter: Konrad Windszus
>Priority: Major
>
> If I use either {{${revision}}},{{${sha1}}}, or {{${changelist}}} in the root
> pom's parent version it simply does not work, even when the project is
> invoked via
> {{mvn package -Drevision=1.0}} and the according parent is available in
> version {{1.0}} in my Maven repo.
> Instead I get the following error
> {code}
> mvn package -Dsha1=1.0
> [INFO] Scanning for projects...
> Downloading from central:
> https://repo.maven.apache.org/maven2/some/test/myparent/$%7Bsha1%7D/myparent-$%7Bsha1%7D.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for some.test:root:[unknown-version]: Could
> not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project some.test:root:[unknown-version]
> (/Users/konradwindszus/Downloads/pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for some.test:root:[unknown-version]:
> Could not find artifact some.test:myparent:pom:${sha1} in central
> (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 11, column 13 -> [Help 2]
> [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/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {code}
> The following minimum pom can be used for testing
> {code}
>
> xmlns="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
>
> some.test
> myparent
>
> ${sha1}
>
> root
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
