date:20180423

[jira] [Commented] (SUREFIRE-1508) SurefireBooterForkException with Maven 3.5.3

2018-04-23 Thread Andreas Gudian (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449400#comment-16449400
 ] 

Andreas Gudian commented on SUREFIRE-1508:
--

I'm not talking about the maven image, I'm talking about the openjdk image:

Alpine {{ps}} doesn't support {{-p}}
{code}
> docker run --rm openjdk:8-jdk-alpine /bin/ps -p 1
/bin/ps: unrecognized option: p
{code}

Debian slim doesn't come with {{ps}} out of the box, thus the check is 
disabled, unless the {{procps}} package is being installed (like it is for the 
latest Maven images, which is not used everywhere):
{code}
> docker run --rm openjdk:8-jdk-slim which ps
> (nothing)
{code}

So how about checking the exit code of {{ps -p 1}} in the PpidChecker and if 
it's not 0, then use an alternative alive-check? (process id 1 should always be 
available, right?). Or don't use {{ps -p}} on linux and check the file 
{{/proc//stat}}?

> SurefireBooterForkException with Maven 3.5.3
> 
>
> Key: SUREFIRE-1508
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1508
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
> Environment: Docker Image maven:3.5.2-jdk-8
> SpringBoot Application testet with Spring Platform Versions Brussels-SR7 and 
> Brussels-SR3
>Reporter: Pertschy Simon
>Priority: Major
> Attachments: 2018-03-28T16-00-51_221-jvmRun1.dump, 
> failsafe-summary.xml
>
>
> Running junit integration tests with Maven 3.5.3 gives 
> org.apache.maven.surefire.booter.SurefireBooterForkException. 
> With Maven 3.5.2 everything runs fine.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:verify (default) on 
> project explosive: There are test failures.
> [ERROR] 
> [ERROR] Please refer to /usr/src/mymaven/target/failsafe-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] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> [ERROR] Command was /bin/sh -c cd /usr/src/mymaven && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Dfile.encoding=UTF-8 -jar 
> /usr/src/mymaven/target/surefire/surefirebooter8650244765410237450.jar 
> /usr/src/mymaven/target/surefire 2018-03-28T16-00-51_221-jvmRun1 
> surefire1685882686721224264tmp surefire_03464518048239249547tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.in

[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread Akira Ajisaka (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449364#comment-16449364
 ] 

Akira Ajisaka commented on MSITE-812:
-

Thanks [~hboutemy] for the additional fix!

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dorian Vallant updated MNG-6394:

Attachment: test-projects-flatten.jar

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects-flatten.jar, test-projects.jar, 
> test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449356#comment-16449356
 ] 

Dorian Vallant commented on MNG-6394:
-

Same example with maven-flatten-plugin included...

 [^test-projects-flatten.jar] 

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects-flatten.jar, test-projects.jar, 
> test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dorian Vallant updated MNG-6394:

Comment: was deleted

(was: Same example with maven-flatten-plugin included in parent's pom.xml...

 [^test-projects.jar] )

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar, test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449353#comment-16449353
 ] 

Dorian Vallant commented on MNG-6394:
-

Same example with maven-flatten-plugin included in parent's pom.xml...

 [^test-projects.jar] 

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar, test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dorian Vallant updated MNG-6394:

Attachment: test-projects.jar

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar, test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSITE-817) inherit edit value in site.xml

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MSITE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MSITE-817.
---
Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=1042495efdaa4329e3f68548d04b7554435b1b18

> inherit edit value in site.xml
> --
>
> Key: MSITE-817
> URL: https://issues.apache.org/jira/browse/MSITE-817
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: doxia integration
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> see DOXIASITETOOLS-187



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MSITE-812.
---
Resolution: Fixed
  Assignee: Hervé Boutemy

https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=348b9fcc58e5fc4a42691ca2ecd49201a055e4d3

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition

2018-04-23 Thread Alan Czajkowski (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Czajkowski updated MNG-6397:
-
Description: 
_*Note:* I am trying to do a build behind a firewall which means I cannot 
access the Internet, I can only access my internal Maven repository inside my 
network, so:_
- _grabbing artifacts from https://artifacts.example.com/repository/maven/ 
works fine_
- _grabbing artifacts from anywhere fails due to firewall restrictions_

Let's begin:

My {{pom.xml}} has the following:
{code:xml}
...

...

org.springframework.boot
spring-boot-starter-web
2.0.0.RELEASE

...

...

...

central
Public
https://artifacts.example.com/repository/maven/

true


true


...

...
{code}
The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
{code:java}
+- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
|  +- 
org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
|  |  +- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
|  |  +- 
com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
|  |  \- 
com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
|  +- 
org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
|  |  \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
|  +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
|  |  +- javax.validation:validation-api:jar:2.0.1.Final:compile
|  |  +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
|  |  \- com.fasterxml:classmate:jar:1.3.1:compile
|  \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
{code}

How is it that the build fails as such:
{code:java}
...
Downloading: 
https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading: 
https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading: 
https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
Downloading: 
https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
...
[ERROR] Failed to execute goal on project maven-multi-module-demo-backend: 
Could not resolve dependencies for project 
com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed to 
collect dependencies at 
org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE -> 
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read 
artifact descriptor for 
org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not transfer 
artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to spring-milestone 
(https://repo.spring.io/milestone): Connection reset -> [Help 1]
...
{code}
when I did not even reference this repo {{spring-milestone 
([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?

When you go down the Spring Boot rabbit hole (go into the 
{{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom 
structure a few jumps) you'll eventually get to a parent-pom 
{{spring-boot-dependencies}} with this definition:
{code:xml}
...



false

spring-milestone
Spring Milestone
https://repo.spring.io/milestone



true

spring-snapshot
Spring Snapshot
https://repo.spring.io/snapshot



false

rabbit-milestone
Rabbit Milestone
https://dl.bintray.com/rabbitmq/maven-milestones


...
{code}
How is it that the Maven build does _not_ even attempt to reach out to 
[https://artifacts.example.com/repository/maven/] to try to find the missing 
dependency {{shrinkwrap-bom}}? and only reaches out to the above repos only and 
not the one defined in my own {{pom.xml}}?

*This seems like a transitive dependency resolution bug to me as the Maven 
build does not even make a single attempt at trying to get {{shrinkwrap-bom}} 
from the {{}} that I have explicitly defined in my {{pom.xml}}. The 
{{shrinkwrap-bom}} artifact does exist in 
[https://artifacts.example.com/repository/maven/] and can be fetched no problem 
if it is explicitly defined in my {{pom.xml}} but defining it explicitly would 
be a work-around and I cannot use this work-around in my situation.*

  was:
_*Note:* I am trying to do a build behind a firewall which means I cannot 
access the Internet, I can only access my internal Maven repository ins

[jira] [Commented] (SUREFIRE-1508) SurefireBooterForkException with Maven 3.5.3

2018-04-23 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448990#comment-16448990
 ] 

Tibor Digana commented on SUREFIRE-1508:


I tried {{ps -p 1}} but {{mvn test}} did not fail in either case however 
{{3.5.0-jdk-8-slim}} tells me that {{ps}} does not exist and 
{{maven:3.5.3-jdk-8-alpine}} found it.

> SurefireBooterForkException with Maven 3.5.3
> 
>
> Key: SUREFIRE-1508
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1508
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
> Environment: Docker Image maven:3.5.2-jdk-8
> SpringBoot Application testet with Spring Platform Versions Brussels-SR7 and 
> Brussels-SR3
>Reporter: Pertschy Simon
>Priority: Major
> Attachments: 2018-03-28T16-00-51_221-jvmRun1.dump, 
> failsafe-summary.xml
>
>
> Running junit integration tests with Maven 3.5.3 gives 
> org.apache.maven.surefire.booter.SurefireBooterForkException. 
> With Maven 3.5.2 everything runs fine.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:verify (default) on 
> project explosive: There are test failures.
> [ERROR] 
> [ERROR] Please refer to /usr/src/mymaven/target/failsafe-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] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> [ERROR] Command was /bin/sh -c cd /usr/src/mymaven && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Dfile.encoding=UTF-8 -jar 
> /usr/src/mymaven/target/surefire/surefirebooter8650244765410237450.jar 
> /usr/src/mymaven/target/surefire 2018-03-28T16-00-51_221-jvmRun1 
> surefire1685882686721224264tmp surefire_03464518048239249547tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main

[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448963#comment-16448963
 ] 

Hudson commented on MSITE-812:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #36

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/36/

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1508) SurefireBooterForkException with Maven 3.5.3

2018-04-23 Thread Andreas Gudian (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448903#comment-16448903
 ] 

Andreas Gudian commented on SUREFIRE-1508:
--

macOS and Debian Slim are not affected by the missing ps option.
Try using a plain openjdk 8 alpine image and run {{ps -p 1}}. That will fail. 
There are lots of users running Maven in Docker image based on Alpine but not 
on the „official“ Maven Docker image.
Anyway, I fully agree that it should not fail just because the -p option is not 
supported on the system.

> SurefireBooterForkException with Maven 3.5.3
> 
>
> Key: SUREFIRE-1508
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1508
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
> Environment: Docker Image maven:3.5.2-jdk-8
> SpringBoot Application testet with Spring Platform Versions Brussels-SR7 and 
> Brussels-SR3
>Reporter: Pertschy Simon
>Priority: Major
> Attachments: 2018-03-28T16-00-51_221-jvmRun1.dump, 
> failsafe-summary.xml
>
>
> Running junit integration tests with Maven 3.5.3 gives 
> org.apache.maven.surefire.booter.SurefireBooterForkException. 
> With Maven 3.5.2 everything runs fine.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:verify (default) on 
> project explosive: There are test failures.
> [ERROR] 
> [ERROR] Please refer to /usr/src/mymaven/target/failsafe-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] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> [ERROR] Command was /bin/sh -c cd /usr/src/mymaven && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Dfile.encoding=UTF-8 -jar 
> /usr/src/mymaven/target/surefire/surefirebooter8650244765410237450.jar 
> /usr/src/mymaven/target/surefire 2018-03-28T16-00-51_221-jvmRun1 
> surefire1685882686721224264tmp surefire_03464518048239249547tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.la

[jira] [Commented] (SUREFIRE-1508) SurefireBooterForkException with Maven 3.5.3

2018-04-23 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448873#comment-16448873
 ] 

Tibor Digana commented on SUREFIRE-1508:


[~agudian]
We should find the root cause and not to force the plugin to keep using {{ps}}. 
Even if the switch "-p" is not supported on OS/X the {{PpidChecker}} must not 
break {{ForkedBooter}} because this mechanism should be ignored and then the 
{{ForkedBooter}} should receive PING instead, which was in version 2.19 as well.
btw, I used {{3.5.0-jdk-8-slim}} on Ubuntu without any problem.

> SurefireBooterForkException with Maven 3.5.3
> 
>
> Key: SUREFIRE-1508
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1508
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
> Environment: Docker Image maven:3.5.2-jdk-8
> SpringBoot Application testet with Spring Platform Versions Brussels-SR7 and 
> Brussels-SR3
>Reporter: Pertschy Simon
>Priority: Major
> Attachments: 2018-03-28T16-00-51_221-jvmRun1.dump, 
> failsafe-summary.xml
>
>
> Running junit integration tests with Maven 3.5.3 gives 
> org.apache.maven.surefire.booter.SurefireBooterForkException. 
> With Maven 3.5.2 everything runs fine.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:verify (default) on 
> project explosive: There are test failures.
> [ERROR] 
> [ERROR] Please refer to /usr/src/mymaven/target/failsafe-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] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> [ERROR] Command was /bin/sh -c cd /usr/src/mymaven && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Dfile.encoding=UTF-8 -jar 
> /usr/src/mymaven/target/surefire/surefirebooter8650244765410237450.jar 
> /usr/src/mymaven/target/surefire 2018-03-28T16-00-51_221-jvmRun1 
> surefire1685882686721224264tmp surefire_03464518048239249547tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at 
> org.codehaus.plexus.classworl

[jira] [Updated] (MNG-6399) Lift JDK minimum to JDK 8

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MNG-6399:
-
Issue Type: Task  (was: Dependency upgrade)

> Lift JDK minimum to JDK 8
> -
>
> Key: MNG-6399
> URL: https://issues.apache.org/jira/browse/MNG-6399
> Project: Maven
>  Issue Type: Task
>Affects Versions: 3.6.0
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.6.0
>
>
> I would like to lift the minimum of Maven Core to JDK 8 (I think it's time)..



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MNG-6399) Lift JDK minimum to JDK 8

2018-04-23 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MNG-6399:


 Summary: Lift JDK minimum to JDK 8
 Key: MNG-6399
 URL: https://issues.apache.org/jira/browse/MNG-6399
 Project: Maven
  Issue Type: Dependency upgrade
Affects Versions: 3.6.0
Reporter: Karl Heinz Marbaise
 Fix For: 3.6.0


I would like to lift the minimum of Maven Core to JDK 8 (I think it's time)..



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRESOURCES-248) Add documentation information for GitHub

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRESOURCES-248.
--
Resolution: Done

Done in 
[2a1f6f8488414e2c4f493aa01a79faa6a4f366ed|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commitdiff;h=2a1f6f8488414e2c4f493aa01a79faa6a4f366ed]

> Add documentation information for GitHub
> 
>
> Key: MRESOURCES-248
> URL: https://issues.apache.org/jira/browse/MRESOURCES-248
> Project: Maven Resources Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOURCES-248) Add documentation information for GitHub

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448843#comment-16448843
 ] 

Hudson commented on MRESOURCES-248:
---

Build succeeded in Jenkins: Maven TLP » maven-resources-plugin » master #12

See 
https://builds.apache.org/job/maven-box/job/maven-resources-plugin/job/master/12/

> Add documentation information for GitHub
> 
>
> Key: MRESOURCES-248
> URL: https://issues.apache.org/jira/browse/MRESOURCES-248
> Project: Maven Resources Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6391) Printout version of last built module in reactor build

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448837#comment-16448837
 ] 

Karl Heinz Marbaise commented on MNG-6391:
--

So after thinking about this what about this and removing the version 
information from the reactor summary completely and add a supplemental line 
with the version information.
{code}
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] parent  SUCCESS [ 3.610 s]
[INFO] parent-lib  SUCCESS [ 0.492 s]
[INFO] commons ... SUCCESS [ 25.444 s]
[INFO] loadbalancer-starter .. SUCCESS [ 21.198 s]
[INFO] proxy-config-starter .. SUCCESS [ 7.496 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Version: 4.0.0-SNAPSHOT
[INFO] 
[INFO] Total time: 01:45 min
[INFO] Finished at: 2018-04-11T09:56:21+02:00
[INFO] 
{code}

For case where we have an aggregator we can add the version to each line in 
{{Reactor Summary}} that will also make clear we have an aggregator instead of 
a multi module build with the same version..WDYT ? 


> Printout version of last built module in reactor build
> --
>
> Key: MNG-6391
> URL: https://issues.apache.org/jira/browse/MNG-6391
> Project: Maven
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 3.5.3
>Reporter: Alexander Griesbaum
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.5.4
>
>
> MNG-6352 introduced printout of the version in a reactor build.
> If I build a multi-module project, not just the parent has the version 
> printout but also the last built module.
> {code:java}
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] parent 4.0.0-SNAPSHOT . SUCCESS [ 3.610 s]
> [INFO] parent-lib  SUCCESS [ 0.492 s]
> [INFO] commons ... SUCCESS [ 25.444 s]
> [INFO] loadbalancer-starter .. SUCCESS [ 21.198 s]
> [INFO] proxy-config-starter 4.0.0-SNAPSHOT ... SUCCESS [ 7.496 s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> {code}
> If I remove the "proxy-config-starter" module, "loadbalancer-starter" got the 
> version printout.
> Also this is not the order I configured the modules in the parent pom but I 
> think this could be something on my side.
> {code:java}
> 
> commons
> loadbalancer-starter
> parent-lib
> proxy-config-starter
> 
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOURCES-248) Add documentation information for GitHub

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448833#comment-16448833
 ] 

Hudson commented on MRESOURCES-248:
---

Build succeeded in Jenkins: Maven TLP » maven-resources-plugin » MRESOURCES-248 
#2

See 
https://builds.apache.org/job/maven-box/job/maven-resources-plugin/job/MRESOURCES-248/2/

> Add documentation information for GitHub
> 
>
> Key: MRESOURCES-248
> URL: https://issues.apache.org/jira/browse/MRESOURCES-248
> Project: Maven Resources Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.1.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRESOURCES-247) Improve WARNING message about encoding.

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRESOURCES-247.
--
Resolution: Done

Thanks Michel for your feedback and this is implemented.

Done in 
[c421c2f78a90392e9f5c49a1a8bf983c3addd52d|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commitdiff;h=c421c2f78a90392e9f5c49a1a8bf983c3addd52d]

> Improve WARNING message about encoding.
> ---
>
> Key: MRESOURCES-247
> URL: https://issues.apache.org/jira/browse/MRESOURCES-247
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Michel Barret
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.1.0
>
>
> When a maven display message like "File encoding has not been set", it can be 
> usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [WARNING] Maybe you should set the configuration: 
> project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOURCES-247) Improve WARNING message about encoding.

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448814#comment-16448814
 ] 

Hudson commented on MRESOURCES-247:
---

Build succeeded in Jenkins: Maven TLP » maven-resources-plugin » master #11

See 
https://builds.apache.org/job/maven-box/job/maven-resources-plugin/job/master/11/

> Improve WARNING message about encoding.
> ---
>
> Key: MRESOURCES-247
> URL: https://issues.apache.org/jira/browse/MRESOURCES-247
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Michel Barret
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.1.0
>
>
> When a maven display message like "File encoding has not been set", it can be 
> usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [WARNING] Maybe you should set the configuration: 
> project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MRESOURCES-248) Add documentation information for GitHub

2018-04-23 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MRESOURCES-248:
--

 Summary: Add documentation information for GitHub
 Key: MRESOURCES-248
 URL: https://issues.apache.org/jira/browse/MRESOURCES-248
 Project: Maven Resources Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.1.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.1.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6383) ProjectBuilder unnecessarily rebuilds modules with ci-friendly versions

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448808#comment-16448808
 ] 

Karl Heinz Marbaise commented on MNG-6383:
--

Have you analyzed that based on the code or do you have a project example ?

> ProjectBuilder unnecessarily rebuilds modules with ci-friendly versions
> ---
>
> Key: MNG-6383
> URL: https://issues.apache.org/jira/browse/MNG-6383
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.5.3
>Reporter: Christoph Kunze
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Consider a multi-module project that uses ci-friendly versions (i.e. the root 
> pom declares ${revision}).
> While "scanning for projects", the DefaultProjectBuilder (build:347) uses a 
> two-phase approach.
> 1) build:390 populates a set of interimResults and a projectIndex. The keys 
> of the projectIndex take the form groupId:artifactId:packaging:version and 
> the version always is the interpolated version (i.e. 1.0-SNAPSHOT rather than 
> ${revision}).
> 2) build:573 calls initProject which in line 638 attempts to retrieve the 
> previously constructed parent project from the projectIndex. However, the key 
> used here still contains the uninterpolated version (i.e. ${revision}) so 
> *the* *parent project is never found*. In line 652, the parent project is 
> therefore constructed anew:
> {code:java}
> parent = build( parentPomFile, projectBuildingRequest ).getProject();
> {code}
> This is not only ineffective but also causes problems, e.g. if the parent 
> imports a bom module from the same reactor, this leads to a warning "Failed 
> to build parent project" and potential follow-up problems. Also, the maven 
> assembly plugin seems to fail on such projects.
> *Details*
>  - The ModelBuildingResult created in the first phase contains a list of 
> modelIds. They key used to add an entry to the project index always 
> corresponds to the *first* item in this list:
> {code:java}
> // DefaultProjectBuilder:436
> projectIndex.put( result.getModelIds().get( 0 ), project )
> {code}
> However, the key used to retrieve the entry during the processing of its 
> child is the *second* element from the modelIds list:
> {code:java}
> // DefaultProjectBuilder:636
> String parentModelId = result.getModelIds().get( 1 );
> MavenProject parent = projects.get( parentModelId );
> {code}
> The list items are created by DefaultModelBuilder.build:244. First a 
> "lineage" of the current module is built. Then the first element of the 
> lineage, corresponding to the current module, gets interpolated. The other 
> lineage items *do not get interpolated*, i.e. they still contain the 
> placeholder version.
> The list of modelIds is then constructed from the lineage, leading to the 
> first element having an interpolated version whereas all other elements have 
> a placeholder version.
> {code:java}
> // DefaultModelBuilder:411
> for ( ModelData currentData : lineage )
> {
> String modelId = ( currentData != superData ) ? currentData.getId() : "";
> result.addModelId( modelId );
> {code}
> *Fix*
>  One way to fix the issue might be to interpolate all elements of the lineage 
> in DefaultModelBuilder.build:244, or to at least replace their versions.
> The following modification (hacky and probably faulty, for demonstration 
> purpose only) fixed the issue for my project:
> {code:java}
> // model interpolation
> resultModel = interpolateModel( resultModel, request, problems );
> resultData.setModel( resultModel );
> /* new code starts here */
> if ( resultModel.getParent() != null )
> {
> final ModelData parentData = lineage.get( 1 );
> final Model interpolatedParent = interpolateModel( parentData.getModel(), 
> request, problems );
> // parentData.setModel( interpolatedParent );
> parentData.setVersion( interpolatedParent.getVersion() );
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6383) ProjectBuilder unnecessarily rebuilds modules with ci-friendly versions

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MNG-6383:
-
Fix Version/s: 3.5.4-candidate

> ProjectBuilder unnecessarily rebuilds modules with ci-friendly versions
> ---
>
> Key: MNG-6383
> URL: https://issues.apache.org/jira/browse/MNG-6383
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.5.3
>Reporter: Christoph Kunze
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Consider a multi-module project that uses ci-friendly versions (i.e. the root 
> pom declares ${revision}).
> While "scanning for projects", the DefaultProjectBuilder (build:347) uses a 
> two-phase approach.
> 1) build:390 populates a set of interimResults and a projectIndex. The keys 
> of the projectIndex take the form groupId:artifactId:packaging:version and 
> the version always is the interpolated version (i.e. 1.0-SNAPSHOT rather than 
> ${revision}).
> 2) build:573 calls initProject which in line 638 attempts to retrieve the 
> previously constructed parent project from the projectIndex. However, the key 
> used here still contains the uninterpolated version (i.e. ${revision}) so 
> *the* *parent project is never found*. In line 652, the parent project is 
> therefore constructed anew:
> {code:java}
> parent = build( parentPomFile, projectBuildingRequest ).getProject();
> {code}
> This is not only ineffective but also causes problems, e.g. if the parent 
> imports a bom module from the same reactor, this leads to a warning "Failed 
> to build parent project" and potential follow-up problems. Also, the maven 
> assembly plugin seems to fail on such projects.
> *Details*
>  - The ModelBuildingResult created in the first phase contains a list of 
> modelIds. They key used to add an entry to the project index always 
> corresponds to the *first* item in this list:
> {code:java}
> // DefaultProjectBuilder:436
> projectIndex.put( result.getModelIds().get( 0 ), project )
> {code}
> However, the key used to retrieve the entry during the processing of its 
> child is the *second* element from the modelIds list:
> {code:java}
> // DefaultProjectBuilder:636
> String parentModelId = result.getModelIds().get( 1 );
> MavenProject parent = projects.get( parentModelId );
> {code}
> The list items are created by DefaultModelBuilder.build:244. First a 
> "lineage" of the current module is built. Then the first element of the 
> lineage, corresponding to the current module, gets interpolated. The other 
> lineage items *do not get interpolated*, i.e. they still contain the 
> placeholder version.
> The list of modelIds is then constructed from the lineage, leading to the 
> first element having an interpolated version whereas all other elements have 
> a placeholder version.
> {code:java}
> // DefaultModelBuilder:411
> for ( ModelData currentData : lineage )
> {
> String modelId = ( currentData != superData ) ? currentData.getId() : "";
> result.addModelId( modelId );
> {code}
> *Fix*
>  One way to fix the issue might be to interpolate all elements of the lineage 
> in DefaultModelBuilder.build:244, or to at least replace their versions.
> The following modification (hacky and probably faulty, for demonstration 
> purpose only) fixed the issue for my project:
> {code:java}
> // model interpolation
> resultModel = interpolateModel( resultModel, request, problems );
> resultData.setModel( resultModel );
> /* new code starts here */
> if ( resultModel.getParent() != null )
> {
> final ModelData parentData = lineage.get( 1 );
> final Model interpolatedParent = interpolateModel( parentData.getModel(), 
> request, problems );
> // parentData.setModel( interpolatedParent );
> parentData.setVersion( interpolatedParent.getVersion() );
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (MNG-6383) ProjectBuilder unnecessarily rebuilds modules with ci-friendly versions

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise reassigned MNG-6383:


Assignee: Karl Heinz Marbaise

> ProjectBuilder unnecessarily rebuilds modules with ci-friendly versions
> ---
>
> Key: MNG-6383
> URL: https://issues.apache.org/jira/browse/MNG-6383
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.5.3
>Reporter: Christoph Kunze
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.5.4-candidate
>
>
> Consider a multi-module project that uses ci-friendly versions (i.e. the root 
> pom declares ${revision}).
> While "scanning for projects", the DefaultProjectBuilder (build:347) uses a 
> two-phase approach.
> 1) build:390 populates a set of interimResults and a projectIndex. The keys 
> of the projectIndex take the form groupId:artifactId:packaging:version and 
> the version always is the interpolated version (i.e. 1.0-SNAPSHOT rather than 
> ${revision}).
> 2) build:573 calls initProject which in line 638 attempts to retrieve the 
> previously constructed parent project from the projectIndex. However, the key 
> used here still contains the uninterpolated version (i.e. ${revision}) so 
> *the* *parent project is never found*. In line 652, the parent project is 
> therefore constructed anew:
> {code:java}
> parent = build( parentPomFile, projectBuildingRequest ).getProject();
> {code}
> This is not only ineffective but also causes problems, e.g. if the parent 
> imports a bom module from the same reactor, this leads to a warning "Failed 
> to build parent project" and potential follow-up problems. Also, the maven 
> assembly plugin seems to fail on such projects.
> *Details*
>  - The ModelBuildingResult created in the first phase contains a list of 
> modelIds. They key used to add an entry to the project index always 
> corresponds to the *first* item in this list:
> {code:java}
> // DefaultProjectBuilder:436
> projectIndex.put( result.getModelIds().get( 0 ), project )
> {code}
> However, the key used to retrieve the entry during the processing of its 
> child is the *second* element from the modelIds list:
> {code:java}
> // DefaultProjectBuilder:636
> String parentModelId = result.getModelIds().get( 1 );
> MavenProject parent = projects.get( parentModelId );
> {code}
> The list items are created by DefaultModelBuilder.build:244. First a 
> "lineage" of the current module is built. Then the first element of the 
> lineage, corresponding to the current module, gets interpolated. The other 
> lineage items *do not get interpolated*, i.e. they still contain the 
> placeholder version.
> The list of modelIds is then constructed from the lineage, leading to the 
> first element having an interpolated version whereas all other elements have 
> a placeholder version.
> {code:java}
> // DefaultModelBuilder:411
> for ( ModelData currentData : lineage )
> {
> String modelId = ( currentData != superData ) ? currentData.getId() : "";
> result.addModelId( modelId );
> {code}
> *Fix*
>  One way to fix the issue might be to interpolate all elements of the lineage 
> in DefaultModelBuilder.build:244, or to at least replace their versions.
> The following modification (hacky and probably faulty, for demonstration 
> purpose only) fixed the issue for my project:
> {code:java}
> // model interpolation
> resultModel = interpolateModel( resultModel, request, problems );
> resultData.setModel( resultModel );
> /* new code starts here */
> if ( resultModel.getParent() != null )
> {
> final ModelData parentData = lineage.get( 1 );
> final Model interpolatedParent = interpolateModel( parentData.getModel(), 
> request, problems );
> // parentData.setModel( interpolatedParent );
> parentData.setVersion( interpolatedParent.getVersion() );
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MRESOURCES-247) Improve WARNING message about encoding.

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MRESOURCES-247:
---
Summary: Improve WARNING message about encoding.  (was: Improve message 
warning)

> Improve WARNING message about encoding.
> ---
>
> Key: MRESOURCES-247
> URL: https://issues.apache.org/jira/browse/MRESOURCES-247
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Michel Barret
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.1.0
>
>
> When a maven display message like "File encoding has not been set", it can be 
> usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [WARNING] Maybe you should set the configuration: 
> project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MRESOURCES-247) Improve message warning

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MRESOURCES-247:
---
Fix Version/s: 3.1.0

> Improve message warning
> ---
>
> Key: MRESOURCES-247
> URL: https://issues.apache.org/jira/browse/MRESOURCES-247
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Michel Barret
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 3.1.0
>
>
> When a maven display message like "File encoding has not been set", it can be 
> usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [WARNING] Maybe you should set the configuration: 
> project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (MRESOURCES-247) Improve message warning

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise reassigned MRESOURCES-247:
--

Assignee: Karl Heinz Marbaise

> Improve message warning
> ---
>
> Key: MRESOURCES-247
> URL: https://issues.apache.org/jira/browse/MRESOURCES-247
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Michel Barret
>Assignee: Karl Heinz Marbaise
>Priority: Trivial
>
> When a maven display message like "File encoding has not been set", it can be 
> usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [WARNING] Maybe you should set the configuration: 
> project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSITE-820) change localized output from language to full locale, like source

2018-04-23 Thread JIRA

Hervé Boutemy created MSITE-820:
---

 Summary: change localized output from language to full locale, 
like source
 Key: MSITE-820
 URL: https://issues.apache.org/jira/browse/MSITE-820
 Project: Maven Site Plugin
  Issue Type: Wish
  Components: localization
Affects Versions: 3.7, 3.0, 2.4
Reporter: Hervé Boutemy
 Fix For: backlog


while working on MSITE-818, having output html localized content using only 
language part of the locale is not really consistent
this is particularly visible for example with {{zh_CN}}: source is in {{zh_CN}} 
directory but output is in {{/zh/}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MSITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448764#comment-16448764
 ] 

Hervé Boutemy edited comment on MSITE-818 at 4/23/18 7:46 PM:
--

https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=d5c5bbdfb093e88fad05ee685942664e041fc957
https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=e2217464a61a4c21ac700f691a1d36a250994a6d


was (Author: hboutemy):
https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=d5c5bbdfb093e88fad05ee685942664e041fc957

> site:run fails to find locale when zh_CN is used
> 
>
> Key: MSITE-818
> URL: https://issues.apache.org/jira/browse/MSITE-818
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:run
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> as reported on maven-dev: 
> https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
> ManifoildCF has issue when using site:run with zh_CN locale: requesting 
> http://localhost:8080/zh/ gives
> {noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for 
> the locale zh_CN
> Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
> zh_CN at
> org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MSITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448764#comment-16448764
 ] 

Hervé Boutemy commented on MSITE-818:
-

https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=d5c5bbdfb093e88fad05ee685942664e041fc957

> site:run fails to find locale when zh_CN is used
> 
>
> Key: MSITE-818
> URL: https://issues.apache.org/jira/browse/MSITE-818
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:run
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> as reported on maven-dev: 
> https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
> ManifoildCF has issue when using site:run with zh_CN locale: requesting 
> http://localhost:8080/zh/ gives
> {noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for 
> the locale zh_CN
> Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
> zh_CN at
> org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6363) Remove secret thread configuration property from code

2018-04-23 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MNG-6363.

Resolution: Done

Done in 
[9c118d34c905a16dcc85ccf4252f16e8ceabd7a3|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=9c118d34c905a16dcc85ccf4252f16e8ceabd7a3]

> Remove secret thread configuration property from code
> -
>
> Key: MNG-6363
> URL: https://issues.apache.org/jira/browse/MNG-6363
> Project: Maven
>  Issue Type: Improvement
>  Components: Command Line
>Affects Versions: 3.5.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.5.4
>
>
> Currently the code of Maven core {{MavenCli}} contains something like this:
> {code:java}
>         final String threadConfiguration = commandLine.hasOption( 
> CLIManager.THREADS )
>             ? commandLine.getOptionValue( CLIManager.THREADS )
>             : request.getSystemProperties().getProperty(
>                 MavenCli.THREADS_DEPRECATED ); // TODO Remove this setting. 
> Note that the int-tests use it
> {code}
> We should remove the {{THREADS_DEPRECATED}} part here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6363) Remove secret thread configuration property from code

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448733#comment-16448733
 ] 

Hudson commented on MNG-6363:
-

Build succeeded in Jenkins: Maven TLP » maven » master #7

See https://builds.apache.org/job/maven-box/job/maven/job/master/7/

> Remove secret thread configuration property from code
> -
>
> Key: MNG-6363
> URL: https://issues.apache.org/jira/browse/MNG-6363
> Project: Maven
>  Issue Type: Improvement
>  Components: Command Line
>Affects Versions: 3.5.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.5.4
>
>
> Currently the code of Maven core {{MavenCli}} contains something like this:
> {code:java}
>         final String threadConfiguration = commandLine.hasOption( 
> CLIManager.THREADS )
>             ? commandLine.getOptionValue( CLIManager.THREADS )
>             : request.getSystemProperties().getProperty(
>                 MavenCli.THREADS_DEPRECATED ); // TODO Remove this setting. 
> Note that the int-tests use it
> {code}
> We should remove the {{THREADS_DEPRECATED}} part here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSITE-819) improve display of site rendering with locale info

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MSITE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MSITE-819.
---
Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=94dec935facf9260d348cc87780076bacde7f70c
https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=30557f51263e4d0c04f5147a3f69857eee3ae5cc
https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git&a=commit&h=379af9e217951abe70139cc1268d59956a5cb41c

> improve display of site rendering with locale info
> --
>
> Key: MSITE-819
> URL: https://issues.apache.org/jira/browse/MSITE-819
> Project: Maven Site Plugin
>  Issue Type: Improvement
>  Components: localization
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> after working on MSITE-818, displaying info on localized site rendering would 
> be useful
> Just adding an info at the beginning, like:
> {noformat}[INFO] Rendering localized site for Chinese (China) 
> (zh_CN){noformat}
> and for default locale:
> {noformat}[INFO] Rendering site with default locale English (en){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-819) improve display of site rendering with locale info

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448562#comment-16448562
 ] 

Hudson commented on MSITE-819:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #35

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/35/

> improve display of site rendering with locale info
> --
>
> Key: MSITE-819
> URL: https://issues.apache.org/jira/browse/MSITE-819
> Project: Maven Site Plugin
>  Issue Type: Improvement
>  Components: localization
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> after working on MSITE-818, displaying info on localized site rendering would 
> be useful
> Just adding an info at the beginning, like:
> {noformat}[INFO] Rendering localized site for Chinese (China) 
> (zh_CN){noformat}
> and for default locale:
> {noformat}[INFO] Rendering site with default locale English (en){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-819) improve display of site rendering with locale info

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448555#comment-16448555
 ] 

Hudson commented on MSITE-819:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #34

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/34/

> improve display of site rendering with locale info
> --
>
> Key: MSITE-819
> URL: https://issues.apache.org/jira/browse/MSITE-819
> Project: Maven Site Plugin
>  Issue Type: Improvement
>  Components: localization
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> after working on MSITE-818, displaying info on localized site rendering would 
> be useful
> Just adding an info at the beginning, like:
> {noformat}[INFO] Rendering localized site for Chinese (China) 
> (zh_CN){noformat}
> and for default locale:
> {noformat}[INFO] Rendering site with default locale English (en){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-819) improve display of site rendering with locale info

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448529#comment-16448529
 ] 

Hudson commented on MSITE-819:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #33

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/33/

> improve display of site rendering with locale info
> --
>
> Key: MSITE-819
> URL: https://issues.apache.org/jira/browse/MSITE-819
> Project: Maven Site Plugin
>  Issue Type: Improvement
>  Components: localization
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> after working on MSITE-818, displaying info on localized site rendering would 
> be useful
> Just adding an info at the beginning, like:
> {noformat}[INFO] Rendering localized site for Chinese (China) 
> (zh_CN){noformat}
> and for default locale:
> {noformat}[INFO] Rendering site with default locale English (en){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-819) improve display of site rendering with locale info

2018-04-23 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MSITE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448524#comment-16448524
 ] 

Hervé Boutemy commented on MSITE-819:
-

can also remove "for the English version" in
{noformat}[INFO] Skipped "About" report 
(maven-project-info-reports-plugin:2.9:index), file "index.html" already exists 
for the English version.{noformat}
since it causes more confusion than anything else: there is no cross locale 
rendering

> improve display of site rendering with locale info
> --
>
> Key: MSITE-819
> URL: https://issues.apache.org/jira/browse/MSITE-819
> Project: Maven Site Plugin
>  Issue Type: Improvement
>  Components: localization
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> after working on MSITE-818, displaying info on localized site rendering would 
> be useful
> Just adding an info at the beginning, like:
> {noformat}[INFO] Rendering localized site for Chinese (China) 
> (zh_CN){noformat}
> and for default locale:
> {noformat}[INFO] Rendering site with default locale English (en){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSITE-819) improve display of site rendering with locale info

2018-04-23 Thread JIRA

Hervé Boutemy created MSITE-819:
---

 Summary: improve display of site rendering with locale info
 Key: MSITE-819
 URL: https://issues.apache.org/jira/browse/MSITE-819
 Project: Maven Site Plugin
  Issue Type: Improvement
  Components: localization
Affects Versions: 3.7
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
 Fix For: 3.7.1


after working on MSITE-818, displaying info on localized site rendering would 
be useful
Just adding an info at the beginning, like:
{noformat}[INFO] Rendering localized site for Chinese (China) (zh_CN){noformat}

and for default locale:
{noformat}[INFO] Rendering site with default locale English (en){noformat}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MSITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MSITE-818.
---
Resolution: Fixed

> site:run fails to find locale when zh_CN is used
> 
>
> Key: MSITE-818
> URL: https://issues.apache.org/jira/browse/MSITE-818
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:run
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> as reported on maven-dev: 
> https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
> ManifoildCF has issue when using site:run with zh_CN locale: requesting 
> http://localhost:8080/zh/ gives
> {noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for 
> the locale zh_CN
> Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
> zh_CN at
> org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448461#comment-16448461
 ] 

Hudson commented on MSITE-818:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #32

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/32/

> site:run fails to find locale when zh_CN is used
> 
>
> Key: MSITE-818
> URL: https://issues.apache.org/jira/browse/MSITE-818
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:run
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> as reported on maven-dev: 
> https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
> ManifoildCF has issue when using site:run with zh_CN locale: requesting 
> http://localhost:8080/zh/ gives
> {noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for 
> the locale zh_CN
> Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
> zh_CN at
> org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448414#comment-16448414
 ] 

Hudson commented on MSITE-818:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #31

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/31/

> site:run fails to find locale when zh_CN is used
> 
>
> Key: MSITE-818
> URL: https://issues.apache.org/jira/browse/MSITE-818
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:run
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> as reported on maven-dev: 
> https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
> ManifoildCF has issue when using site:run with zh_CN locale: requesting 
> http://localhost:8080/zh/ gives
> {noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for 
> the locale zh_CN
> Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
> zh_CN at
> org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448413#comment-16448413
 ] 

Hudson commented on MSITE-812:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #31

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/31/

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MSITE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MSITE-818:

Description: 
as reported on maven-dev: 
https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
ManifoildCF has issue when using site:run with zh_CN locale: requesting 
http://localhost:8080/zh/ gives
{noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for the 
locale zh_CN
Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
zh_CN at
org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}


  was:
as reported on maven-dev: 
https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
ManifoildCF has issue when using site:run with zh_CN locale: requesting 
http://localhost:8080/zh/ gives
{noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for the
locale zh_CN
Caused by: javax.servlet.ServletException: No doxia bean found for the
locale zh_CN at
org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



> site:run fails to find locale when zh_CN is used
> 
>
> Key: MSITE-818
> URL: https://issues.apache.org/jira/browse/MSITE-818
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:run
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> as reported on maven-dev: 
> https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
> ManifoildCF has issue when using site:run with zh_CN locale: requesting 
> http://localhost:8080/zh/ gives
> {noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for 
> the locale zh_CN
> Caused by: javax.servlet.ServletException: No doxia bean found for the locale 
> zh_CN at
> org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSITE-818) site:run fails to find locale when zh_CN is used

2018-04-23 Thread JIRA

Hervé Boutemy created MSITE-818:
---

 Summary: site:run fails to find locale when zh_CN is used
 Key: MSITE-818
 URL: https://issues.apache.org/jira/browse/MSITE-818
 Project: Maven Site Plugin
  Issue Type: Bug
  Components: site:run
Affects Versions: 3.7
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
 Fix For: 3.7.1


as reported on maven-dev: 
https://lists.apache.org/thread.html/08ececda5c1e00a51d39ff3825c33026ccf7ad156293c9aa3f30eb83@%3Cdev.maven.apache.org%3E
ManifoildCF has issue when using site:run with zh_CN locale: requesting 
http://localhost:8080/zh/ gives
{noformat}Problem accessing /zh/index.html. Reason: No doxia bean found for the
locale zh_CN
Caused by: javax.servlet.ServletException: No doxia bean found for the
locale zh_CN at
org.apache.maven.plugins.site.run.DoxiaFilter.doFilter(DoxiaFilter.java:129){noformat}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1508) SurefireBooterForkException with Maven 3.5.3

2018-04-23 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448367#comment-16448367
 ] 

Tibor Digana commented on SUREFIRE-1508:


[~agudian]
[~simtschy]'s environment is already {{maven:3.5.2-jdk-8}} which is fixed as 
you said. Then why [~simtschy] reported a bug where is the fix.


> SurefireBooterForkException with Maven 3.5.3
> 
>
> Key: SUREFIRE-1508
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1508
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
> Environment: Docker Image maven:3.5.2-jdk-8
> SpringBoot Application testet with Spring Platform Versions Brussels-SR7 and 
> Brussels-SR3
>Reporter: Pertschy Simon
>Priority: Major
> Attachments: 2018-03-28T16-00-51_221-jvmRun1.dump, 
> failsafe-summary.xml
>
>
> Running junit integration tests with Maven 3.5.3 gives 
> org.apache.maven.surefire.booter.SurefireBooterForkException. 
> With Maven 3.5.2 everything runs fine.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:verify (default) on 
> project explosive: There are test failures.
> [ERROR] 
> [ERROR] Please refer to /usr/src/mymaven/target/failsafe-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] org.apache.maven.surefire.booter.SurefireBooterForkException: The 
> forked VM terminated without properly saying goodbye. VM crash or System.exit 
> called?
> [ERROR] Command was /bin/sh -c cd /usr/src/mymaven && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Dfile.encoding=UTF-8 -jar 
> /usr/src/mymaven/target/surefire/surefirebooter8650244765410237450.jar 
> /usr/src/mymaven/target/surefire 2018-03-28T16-00-51_221-jvmRun1 
> surefire1685882686721224264tmp surefire_03464518048239249547tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at 
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at 
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR] at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>

[jira] [Closed] (MINVOKER-236) improve display of setup jobs

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MINVOKER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MINVOKER-236.
--
Resolution: Fixed

> improve display of setup jobs
> -
>
> Key: MINVOKER-236
> URL: https://issues.apache.org/jira/browse/MINVOKER-236
> Project: Maven Invoker Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.0.2
>
>
> currently, there is an info message "Running Setup Jobs" then setup jobs 
> build, then normal (non-setup) jobs build: you don't know how many jobs were 
> part of the setup
> For example:
> {noformat}[INFO] --- maven-invoker-plugin:3.0.1:integration-test 
> (integration-test) @ maven-toolchains-plugin ---
> [INFO] Running Setup Jobs
> [INFO] Building: setup-custom-toolchain/pom.xml
> [INFO]   setup-custom-toolchain/pom.xml ... SUCCESS 
> (4.8 s)
> [INFO] Building: missing-toolchain/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]   missing-toolchain/pom.xml  SUCCESS 
> (1.6 s)
> [INFO] Building: use-custom-toolchain/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]   use-custom-toolchain/pom.xml . SUCCESS 
> (1.6 s){noformat}
> you need to guess that {{setup-custom-toolchain}} was the only setup job
> adding a simple message at the end of the setup will bring more clarity



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (WAGON-518) AbstractHttpClientWagon#putFromStream() reads entire content to memory

2018-04-23 Thread Chris Lott (JIRA)


[ 
https://issues.apache.org/jira/browse/WAGON-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448125#comment-16448125
 ] 

Chris Lott commented on WAGON-518:
--

Thanks for the quick response. Is there an automated test for this?

> AbstractHttpClientWagon#putFromStream() reads entire content to memory
> --
>
> Key: WAGON-518
> URL: https://issues.apache.org/jira/browse/WAGON-518
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-http
>Affects Versions: 2.12
>Reporter: Chris Lott
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.1.0
>
>
> Method putFromSteam in class AbstractHttpClientWagon seems to violate the 
> implied contract of working with streams.  It uses much memory because it 
> first consumes the input stream argument, then transfers that content.  The 
> code that consumes the stream is in the private class 
> RequestEntityImplementation ctor:
> {code:java}
>      byte[] bytes = IOUtil.toByteArray( stream );{code}
> Please revise it, if possible, to behave more like the superclass 
> StreamWagon's putFromStream method, which does the transfer straight from the 
> input stream.
> We are attempting to PUT some 150MB artifacts in a java microservice that 
> runs with rather sharp memory limits.  As a local workaround we increased the 
> JVM's -Xmx argument but that way lies madness.
> Thanks in advance for any suggestions or workarounds. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448064#comment-16448064
 ] 

Dorian Vallant commented on MNG-6394:
-

Here we go... [^test-projects.jar] 
for detailed instructions please see README.md inside jar

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MNG-6394) ${revision} and parent.releativePath

2018-04-23 Thread Dorian Vallant (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dorian Vallant updated MNG-6394:

Attachment: test-projects.jar

> ${revision} and parent.releativePath
> 
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
> Attachments: test-projects.jar
>
>
> If the CI friendly ${revision} property is used it seems maven does not 
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
>      pom.xml
>  child-project/
>      pom.xml
> parent-project/pom.xml:
> ...
>     my.group
>     parentArtifact
>     ${revision}
>     pom
> ...
> child-project/pom.xml:
>   
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>   
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f 
> child-project/pom.xml clean install' all works fine as long as the parent 
> project is present in the file system. But if you move the parent project to 
> another place, build & install it to your local repository and then try to 
> build the child project, maven tries to download the pom.xml of the parent 
> project but does not replace ${revision}. So maven complains about a missing 
> dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447910#comment-16447910
 ] 

Hervé Boutemy commented on MSITE-812:
-

as expected, I ran {{mvn -Prun-its verify}} on maven-site-plugin then {{grep 
'>>> to ' target/it/*/build.log}} and there are quite a few '//'
notice I also saw that a few lines after your fix, there is also the same issue 
on message for internationalized path

now working on a fix

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447901#comment-16447901
 ] 

Hervé Boutemy commented on MSITE-812:
-

seems reasonale: I merged your commit, thank you

then, just after merging, I found why I was not sure this was a good idea: for 
staging, your reasonment works perfectly
but this code is not only used for staging: it's used also for deploy, where 
the url is not to a file

I'll check and update the code

thank you for the report and help: it's always useful

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447894#comment-16447894
 ] 

ASF GitHub Bot commented on MSITE-812:
--

hboutemy closed pull request #1: [MSITE-812] Missing '/' in log when deploying 
documentation by site:stage
URL: https://github.com/apache/maven-site-plugin/pull/1
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java 
b/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java
index f3360e7..27c918d 100644
--- a/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java
+++ b/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java
@@ -447,7 +447,7 @@ else if ( proxyInfo == null && authenticationInfo != null )
 {
 // TODO: this also uploads the non-default locales,
 // is there a way to exclude directories in wagon?
-getLog().info( "   >>> to " + repository.getUrl() + 
relativeDir );
+getLog().info( "   >>> to " + repository.getUrl() + "/" + 
relativeDir );
 
 wagon.putDirectory( inputDirectory, relativeDir );
 }


 


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


> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOURCES-247) Improve message warning

2018-04-23 Thread Michel Barret (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447825#comment-16447825
 ] 

Michel Barret commented on MRESOURCES-247:
--

I'm Ok with it.

> Improve message warning
> ---
>
> Key: MRESOURCES-247
> URL: https://issues.apache.org/jira/browse/MRESOURCES-247
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Michel Barret
>Priority: Trivial
>
> When a maven display message like "File encoding has not been set", it can be 
> usefull to display what is the name of configuration to fix it. Instead:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> {code}
> we can have:
> {code}
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [WARNING] Maybe you should set the configuration: 
> project.reporting.outputEncoding
> {code}
>  
> {{It can be usefull!}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINVOKER-236) improve display of setup jobs

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MINVOKER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447753#comment-16447753
 ] 

Hudson commented on MINVOKER-236:
-

Build succeeded in Jenkins: Maven TLP » maven-invoker-plugin » master #15

See 
https://builds.apache.org/job/maven-box/job/maven-invoker-plugin/job/master/15/

> improve display of setup jobs
> -
>
> Key: MINVOKER-236
> URL: https://issues.apache.org/jira/browse/MINVOKER-236
> Project: Maven Invoker Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.0.2
>
>
> currently, there is an info message "Running Setup Jobs" then setup jobs 
> build, then normal (non-setup) jobs build: you don't know how many jobs were 
> part of the setup
> For example:
> {noformat}[INFO] --- maven-invoker-plugin:3.0.1:integration-test 
> (integration-test) @ maven-toolchains-plugin ---
> [INFO] Running Setup Jobs
> [INFO] Building: setup-custom-toolchain/pom.xml
> [INFO]   setup-custom-toolchain/pom.xml ... SUCCESS 
> (4.8 s)
> [INFO] Building: missing-toolchain/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]   missing-toolchain/pom.xml  SUCCESS 
> (1.6 s)
> [INFO] Building: use-custom-toolchain/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]   use-custom-toolchain/pom.xml . SUCCESS 
> (1.6 s){noformat}
> you need to guess that {{setup-custom-toolchain}} was the only setup job
> adding a simple message at the end of the setup will bring more clarity



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSITE-812) Missing '/' in log when deploying documentation by site:stage

2018-04-23 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/MSITE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy updated MSITE-812:

Fix Version/s: 3.7.1

> Missing '/' in log when deploying documentation by site:stage
> -
>
> Key: MSITE-812
> URL: https://issues.apache.org/jira/browse/MSITE-812
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: site:stage(-deploy)
>Affects Versions: 3.7
>Reporter: Akira Ajisaka
>Priority: Major
> Fix For: 3.7.1
>
>
> When running {{mvn site:stage -DstagingDirectory=/Users/ajisaka/YARN-7736}} 
> {noformat}
> [INFO] 
> 
> [INFO] Building Apache Hadoop Project POM 3.2.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-site-plugin:3.7:stage (default-cli) @ hadoop-project ---
> [INFO] Using this base directory for staging: /Users/ajisaka/YARN-7736
> [INFO] Pushing /Users/ajisaka/git/hadoop/hadoop-project/target/site
> [INFO]>>> to file:///Users/ajisaka/YARN-7736hadoop-project
> {noformat}
> '/' is missing between YARN-7736 and hadoop-project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSITE-817) inherit edit value in site.xml

2018-04-23 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447723#comment-16447723
 ] 

Hudson commented on MSITE-817:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #29

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/29/

> inherit edit value in site.xml
> --
>
> Key: MSITE-817
> URL: https://issues.apache.org/jira/browse/MSITE-817
> Project: Maven Site Plugin
>  Issue Type: Bug
>  Components: doxia integration
>Affects Versions: 3.7
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.7.1
>
>
> see DOXIASITETOOLS-187



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINVOKER-236) improve display of setup jobs

2018-04-23 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MINVOKER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447702#comment-16447702
 ] 

Hervé Boutemy commented on MINVOKER-236:


transformed to
{noformat}[INFO] --- maven-invoker-plugin:3.0.2-SNAPSHOT:integration-test 
(integration-test) @ maven-toolchains-plugin ---
[INFO] Running 1 setup job:
[INFO] Building: setup-custom-toolchain/pom.xml
[INFO]   setup-custom-toolchain/pom.xml ... SUCCESS 
(4.9 s)
[INFO] Setup done.
[INFO] Building: missing-toolchain/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   missing-toolchain/pom.xml  SUCCESS 
(1.6 s)
[INFO] Building: use-custom-toolchain/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   use-custom-toolchain/pom.xml . SUCCESS 
(1.7 s){noformat}

> improve display of setup jobs
> -
>
> Key: MINVOKER-236
> URL: https://issues.apache.org/jira/browse/MINVOKER-236
> Project: Maven Invoker Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.1
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.0.2
>
>
> currently, there is an info message "Running Setup Jobs" then setup jobs 
> build, then normal (non-setup) jobs build: you don't know how many jobs were 
> part of the setup
> For example:
> {noformat}[INFO] --- maven-invoker-plugin:3.0.1:integration-test 
> (integration-test) @ maven-toolchains-plugin ---
> [INFO] Running Setup Jobs
> [INFO] Building: setup-custom-toolchain/pom.xml
> [INFO]   setup-custom-toolchain/pom.xml ... SUCCESS 
> (4.8 s)
> [INFO] Building: missing-toolchain/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]   missing-toolchain/pom.xml  SUCCESS 
> (1.6 s)
> [INFO] Building: use-custom-toolchain/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]   use-custom-toolchain/pom.xml . SUCCESS 
> (1.6 s){noformat}
> you need to guess that {{setup-custom-toolchain}} was the only setup job
> adding a simple message at the end of the setup will bring more clarity



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MINVOKER-236) improve display of setup jobs

2018-04-23 Thread JIRA

Hervé Boutemy created MINVOKER-236:
--

 Summary: improve display of setup jobs
 Key: MINVOKER-236
 URL: https://issues.apache.org/jira/browse/MINVOKER-236
 Project: Maven Invoker Plugin
  Issue Type: Improvement
Affects Versions: 3.0.1
Reporter: Hervé Boutemy
Assignee: Hervé Boutemy
 Fix For: 3.0.2


currently, there is an info message "Running Setup Jobs" then setup jobs build, 
then normal (non-setup) jobs build: you don't know how many jobs were part of 
the setup

For example:
{noformat}[INFO] --- maven-invoker-plugin:3.0.1:integration-test 
(integration-test) @ maven-toolchains-plugin ---
[INFO] Running Setup Jobs
[INFO] Building: setup-custom-toolchain/pom.xml
[INFO]   setup-custom-toolchain/pom.xml ... SUCCESS 
(4.8 s)
[INFO] Building: missing-toolchain/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   missing-toolchain/pom.xml  SUCCESS 
(1.6 s)
[INFO] Building: use-custom-toolchain/pom.xml
[INFO] run post-build script verify.groovy
[INFO]   use-custom-toolchain/pom.xml . SUCCESS 
(1.6 s){noformat}

you need to guess that {{setup-custom-toolchain}} was the only setup job

adding a simple message at the end of the setup will bring more clarity





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

60 matches

Mail list logo