[GitHub] rmannibucau edited a comment on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

rmannibucau edited a comment on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419234709 Out of my mind i was thinking to the same way LoggingSupport is done: string.format with all po

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606708#comment-16606708 ] ASF GitHub Bot commented on MNG-6471: - rmannibucau edited a comment on issue #177: [MNG

[jira] [Created] (SUREFIRE-1565) Surefire should support parameterized reportsDirectory

Tibor Digana created SUREFIRE-1565: -- Summary: Surefire should support parameterized reportsDirectory Key: SUREFIRE-1565 URL: https://issues.apache.org/jira/browse/SUREFIRE-1565 Project: Maven Surefire

[jira] [Commented] (MNG-6469) Upload to Nexus hangs

[ https://issues.apache.org/jira/browse/MNG-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606494#comment-16606494 ] Haotian Wu commented on MNG-6469: - I pasted whatever printed on my terminal and the command

[jira] [Comment Edited] (MNG-6469) Upload to Nexus hangs

[ https://issues.apache.org/jira/browse/MNG-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606486#comment-16606486 ] Haotian Wu edited comment on MNG-6469 at 9/6/18 10:50 PM: -- [INFO]

[jira] [Commented] (MNG-6469) Upload to Nexus hangs

[ https://issues.apache.org/jira/browse/MNG-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606486#comment-16606486 ] Haotian Wu commented on MNG-6469: - [INFO] Using alternate deployment repository sonatype-n

[jira] [Commented] (SUREFIRE-1564) Can't override platform version through project/plugin dependencies

[ https://issues.apache.org/jira/browse/SUREFIRE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606434#comment-16606434 ] ASF GitHub Bot commented on SUREFIRE-1564: -- Tibor17 commented on issue #193:

[GitHub] Tibor17 commented on issue #193: [SUREFIRE-1564] ensure provider dependencies can be overriden

Tibor17 commented on issue #193: [SUREFIRE-1564] ensure provider dependencies can be overriden URL: https://github.com/apache/maven-surefire/pull/193#issuecomment-419253353 The solution is to understand the root cause after the analysis has been done. We should start with observing class

[jira] [Commented] (MNG-6469) Upload to Nexus hangs

[ https://issues.apache.org/jira/browse/MNG-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606429#comment-16606429 ] Michael Osipov commented on MNG-6469: - https://github.com/apache/maven/blob/master/apac

[jira] [Commented] (MNG-6469) Upload to Nexus hangs

[ https://issues.apache.org/jira/browse/MNG-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606425#comment-16606425 ] Haotian Wu commented on MNG-6469: - [~michael-o] just want to confirm you are talking about

[GitHub] sormuras commented on issue #193: [SUREFIRE-1564] ensure provider dependencies can be overriden

sormuras commented on issue #193: [SUREFIRE-1564] ensure provider dependencies can be overriden URL: https://github.com/apache/maven-surefire/pull/193#issuecomment-419250240 @mureinik reported a side-effect with `reuseForks=false` over at https://github.com/junit-team/junit5/issues/1579 --

[jira] [Commented] (SUREFIRE-1564) Can't override platform version through project/plugin dependencies

[ https://issues.apache.org/jira/browse/SUREFIRE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606421#comment-16606421 ] ASF GitHub Bot commented on SUREFIRE-1564: -- sormuras commented on issue #193:

[GitHub] Tibor17 commented on issue #112: Adding support for externally passed random seed and printing used seed on console

Tibor17 commented on issue #112: Adding support for externally passed random seed and printing used seed on console URL: https://github.com/apache/maven-surefire/pull/112#issuecomment-419247207 Sorry, I had to work on making stable build with Java 11 and issues which came up after accept

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606370#comment-16606370 ] ASF GitHub Bot commented on MNG-6471: - rmannibucau commented on issue #177: [MNG-6471]

[GitHub] rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419234709 Out of my mind i was thinking to the same way LoggingSupport is done: string.format with all possible

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606369#comment-16606369 ] ASF GitHub Bot commented on MNG-6471: - michael-o commented on issue #177: [MNG-6471] du

[GitHub] michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419234207 I wonder how you would recommend make it configurable? -

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606340#comment-16606340 ] ASF GitHub Bot commented on MNG-6471: - rmannibucau commented on issue #177: [MNG-6471]

[GitHub] rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419224177 The point was that all the additional info you can use to enrich the line are on other lines if you fi

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606325#comment-16606325 ] ASF GitHub Bot commented on MNG-6471: - michael-o commented on issue #177: [MNG-6471] du

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606324#comment-16606324 ] ASF GitHub Bot commented on MNG-6471: - michael-o edited a comment on issue #177: [MNG-6

[GitHub] michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419219385 GitHub swallowed some text. Please recheck.

[GitHub] michael-o edited a comment on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

michael-o edited a comment on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419197100 I think we can do better because if we abstract from MAven the pure artifact id as thread name is

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606319#comment-16606319 ] ASF GitHub Bot commented on MNG-6471: - rmannibucau commented on issue #177: [MNG-6471]

[GitHub] rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419218432 Not sure. "Building" wouldnt bring any info if hardcoded - as today you have BuildThread. We could set

[jira] [Closed] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MCHANGES-395. --- Resolution: Invalid Not an issue. > JIRA password security > -- > >

[jira] [Commented] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606277#comment-16606277 ] Stefan Wendelmann commented on MCHANGES-395: [~michael-o] Thanks a lot, tha

[jira] [Commented] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606264#comment-16606264 ] Michael Osipov commented on MCHANGES-395: - The password is expanded at runtime.

[jira] [Commented] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606257#comment-16606257 ] Stefan Wendelmann commented on MCHANGES-395: Thanks for clearing this out

[jira] [Commented] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606236#comment-16606236 ] Michael Osipov commented on MCHANGES-395: - Well, there is one short coming, the

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606230#comment-16606230 ] ASF GitHub Bot commented on MNG-6471: - michael-o commented on issue #177: [MNG-6471] du

[GitHub] michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419197100 I think we can do better because if we abstract from MAven the pure artifact id as thread name is too si

[jira] [Commented] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605877#comment-16605877 ] Stefan Wendelmann commented on MCHANGES-395: Maybe i understand smth wrong.

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605848#comment-16605848 ] ASF GitHub Bot commented on MNG-6471: - rmannibucau commented on issue #177: [MNG-6471]

[GitHub] rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId

rmannibucau commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the artifactId URL: https://github.com/apache/maven/pull/177#issuecomment-419115915 Yes, name is too variable to be reliable but artifactId works great, here is some output:

[jira] [Commented] (MCHANGES-395) JIRA password security

[ https://issues.apache.org/jira/browse/MCHANGES-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605838#comment-16605838 ] Michael Osipov commented on MCHANGES-395: - I don't userstand what you problem i

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605837#comment-16605837 ] ASF GitHub Bot commented on MNG-6471: - michael-o commented on issue #177: [MNG-6471] du

[GitHub] michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the module name

michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the module name URL: https://github.com/apache/maven/pull/177#issuecomment-419110503 Your change does not correspond to the issue title. You do not set the module name, but the artifact id

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605835#comment-16605835 ] ASF GitHub Bot commented on MNG-6471: - michael-o commented on issue #177: [MNG-6471] du

[GitHub] michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the module name

michael-o commented on issue #177: [MNG-6471] during parallel build, ensure to set the thread name to the module name URL: https://github.com/apache/maven/pull/177#issuecomment-419110109 Nice idea, now do the threads look like now? --

[jira] [Commented] (MCOMPILER-278) Incremental build does not track inter-module dependencies.

[ https://issues.apache.org/jira/browse/MCOMPILER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605706#comment-16605706 ] Darraz commented on MCOMPILER-278: -- Hello, Is there any news regarding this issue?

[jira] [Created] (MCHANGES-395) JIRA password security

Stefan Wendelmann created MCHANGES-395: -- Summary: JIRA password security Key: MCHANGES-395 URL: https://issues.apache.org/jira/browse/MCHANGES-395 Project: Maven Changes Plugin Issue Typ

[jira] [Commented] (MNG-5984) Maven core extension resolution ignores repositories from activeByDefault profiles in settings.xml

[ https://issues.apache.org/jira/browse/MNG-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605546#comment-16605546 ] Francois MAROT commented on MNG-5984: - I can confirm the problem is still in Maven 3.5.

[jira] [Created] (MSHARED-759) Upgrade parent to version 32

Karl Heinz Marbaise created MSHARED-759: --- Summary: Upgrade parent to version 32 Key: MSHARED-759 URL: https://issues.apache.org/jira/browse/MSHARED-759 Project: Maven Shared Components

[jira] [Created] (MNG-6471) Parallel builder should use as thread name the module name

Romain Manni-Bucau created MNG-6471: --- Summary: Parallel builder should use as thread name the module name Key: MNG-6471 URL: https://issues.apache.org/jira/browse/MNG-6471 Project: Maven Is

[jira] [Commented] (MNG-6471) Parallel builder should use as thread name the module name

[ https://issues.apache.org/jira/browse/MNG-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605498#comment-16605498 ] ASF GitHub Bot commented on MNG-6471: - rmannibucau opened a new pull request #177: [MNG

[GitHub] rmannibucau opened a new pull request #177: [MNG-6471] during parallel build, ensure to set the thread name to the module name

rmannibucau opened a new pull request #177: [MNG-6471] during parallel build, ensure to set the thread name to the module name URL: https://github.com/apache/maven/pull/177 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure

[jira] [Commented] (MNG-5588) Scope import in pluginManagement

[ https://issues.apache.org/jira/browse/MNG-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605433#comment-16605433 ] Dmitry Ovchinnikov commented on MNG-5588: - The dependency version importing is a ki