[jira] [Commented] (MNG-5781) resolution of nested import scoped dependencies causes maven to reach out to external central repo

[ https://issues.apache.org/jira/browse/MNG-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300990#comment-17300990 ] Michael Osipov commented on MNG-5781: - Either way, can you confirm that both issues are describing the

[jira] [Commented] (MNG-7114) Publish XSDs as artifact to Central

[ https://issues.apache.org/jira/browse/MNG-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300987#comment-17300987 ] Michael Osipov commented on MNG-7114: - I wonder whether those projects could use MASSEMBLY to create a

[jira] [Commented] (MNG-7110) Different behavior of extensions

[ https://issues.apache.org/jira/browse/MNG-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300984#comment-17300984 ] Hudson commented on MNG-7110: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.6.x #6 See

[jira] [Commented] (MNG-7051) Optionally skip non-existing profiles

[ https://issues.apache.org/jira/browse/MNG-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300983#comment-17300983 ] Hudson commented on MNG-7051: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.6.x #6 See

[jira] [Commented] (MNG-7046) Revert MNG-5639 and make repo config static only

[ https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300985#comment-17300985 ] Hudson commented on MNG-7046: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.6.x #6 See

[jira] [Commented] (MNG-5639) Support resolution of Import Scope POMs from Repo that contains a ${parameter}

[ https://issues.apache.org/jira/browse/MNG-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300986#comment-17300986 ] Hudson commented on MNG-5639: - Build failed in Jenkins: Maven » Maven TLP » maven » maven-3.6.x #6 See

[jira] [Commented] (MNG-5781) resolution of nested import scoped dependencies causes maven to reach out to external central repo

[ https://issues.apache.org/jira/browse/MNG-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300981#comment-17300981 ] Ravi Sanwal commented on MNG-5781: -- Thanks Michael. I hope you meant the other way around. The other

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

[ https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300979#comment-17300979 ] Hudson commented on MNG-6399: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #119 See

[jira] [Updated] (MNG-5552) Classified artifacts are missing from ${project.artifactMap}

[ https://issues.apache.org/jira/browse/MNG-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-5552: Fix Version/s: (was: 4.x / Backlog) 4.0.x-candidate > Classified artifacts

[GitHub] [maven-compiler-plugin] mthmulders merged pull request #42: Grammar on 'Compiling Sources Using A Different JDK' page

mthmulders merged pull request #42: URL: https://github.com/apache/maven-compiler-plugin/pull/42 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[GitHub] [maven-compiler-plugin] mthmulders commented on pull request #42: Grammar on 'Compiling Sources Using A Different JDK' page

mthmulders commented on pull request #42: URL: https://github.com/apache/maven-compiler-plugin/pull/42#issuecomment-798775494 Thank you! This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [maven-compiler-plugin] mthmulders opened a new pull request #42: Grammar on 'Compiling Sources Using A Different JDK' page

mthmulders opened a new pull request #42: URL: https://github.com/apache/maven-compiler-plugin/pull/42 @elharo You're a native speaker, could you please verify? This is an automated message from the Apache Git

[jira] [Closed] (MNG-6012) Missing profile is only notified at the end of a run

[ https://issues.apache.org/jira/browse/MNG-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders closed MNG-6012. Assignee: Maarten Mulders > Missing profile is only notified at the end of a run >

[jira] [Resolved] (MNG-6012) Missing profile is only notified at the end of a run

[ https://issues.apache.org/jira/browse/MNG-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders resolved MNG-6012. -- Fix Version/s: (was: 4.0.x-candidate) (was:

[jira] [Commented] (MNG-6012) Missing profile is only notified at the end of a run

[ https://issues.apache.org/jira/browse/MNG-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300959#comment-17300959 ] Maarten Mulders commented on MNG-6012: -- {quote}[~mthmulders], I consider this resolved. WDYT? {quote}

[GitHub] [maven] michael-o commented on pull request #448: [MNG-7102] The child modules of excluded projects are now excluded

michael-o commented on pull request #448: URL: https://github.com/apache/maven/pull/448#issuecomment-798762538 I agree with @rfscholte that order should not matter because this would make it much more complex. According to his explanation exclusion should win? If so, I am fine with that.

[jira] [Assigned] (MNG-6075) Increase the model validation level to the next minor level version

[ https://issues.apache.org/jira/browse/MNG-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MNG-6075: --- Assignee: Michael Osipov > Increase the model validation level to the next minor level

[GitHub] [maven] MartinKanters commented on pull request #448: [MNG-7102] The child modules of excluded projects are now excluded

MartinKanters commented on pull request #448: URL: https://github.com/apache/maven/pull/448#issuecomment-798743205 I interpreted @michael-o 's suggestion as that the more specific project would win. But anyway, I guess if selection then exclusion is a hard rule, then that makes sense

[jira] [Commented] (MNG-5781) resolution of nested import scoped dependencies causes maven to reach out to external central repo

[ https://issues.apache.org/jira/browse/MNG-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300955#comment-17300955 ] Michael Osipov commented on MNG-5781: - This is basically a duplicate of MNG-6772 depicting the same

[jira] [Commented] (MNG-6012) Missing profile is only notified at the end of a run

[ https://issues.apache.org/jira/browse/MNG-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300956#comment-17300956 ] Michael Osipov commented on MNG-6012: - [~mthmulders], I consider this resolved. WDYT? > Missing

[jira] [Updated] (MNG-6075) Increase the model validation level to the next minor level version

[ https://issues.apache.org/jira/browse/MNG-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6075: Summary: Increase the model validation level to the next minor level version (was: Increase the

[jira] [Commented] (MNG-4347) import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml

[ https://issues.apache.org/jira/browse/MNG-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300944#comment-17300944 ] Michael Osipov commented on MNG-4347: - I believe this is related to MNG-6772 and may be resolved when

[jira] [Commented] (MNG-5639) Support resolution of Import Scope POMs from Repo that contains a ${parameter}

[ https://issues.apache.org/jira/browse/MNG-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300929#comment-17300929 ] Hudson commented on MNG-5639: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #118 See

[jira] [Commented] (MNG-7046) Revert MNG-5639 and make repo config static only

[ https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300928#comment-17300928 ] Hudson commented on MNG-7046: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #118 See

[jira] [Commented] (MNG-6772) Super POM overwrites remapped central repository in nested import POMs

[ https://issues.apache.org/jira/browse/MNG-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300924#comment-17300924 ] Michael Osipov commented on MNG-6772: - An update on the matter: We (me, [~rfscholte], [~hboutemy]) are

[jira] [Updated] (MNG-7094) Assure in an IT that reactor repository definitions are not used when Model Builder downloads dependencies with scope import

[ https://issues.apache.org/jira/browse/MNG-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7094: Description: Based on several discussions (MNG-6772, MNG-6397) the topic of repo scoping causes a

[jira] [Updated] (MNG-7059) Add profile-free repository support in Maven Settings model

[ https://issues.apache.org/jira/browse/MNG-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7059: Fix Version/s: 4.0.x-candidate > Add profile-free repository support in Maven Settings model >

[jira] [Reopened] (MNG-7046) Revert MNG-5639 and make repo config static only

[ https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MNG-7046: - The fix will be reverted because it is incomplete. It causes issues with MNG-6772_2 branch. Also this

[jira] [Updated] (MNG-7046) Revert MNG-5639 and make repo config static only

[ https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-7046: Fix Version/s: (was: 4.0.0-alpha-1) (was: 4.0.0)

[jira] [Commented] (MNG-7110) Different behavior of extensions

[ https://issues.apache.org/jira/browse/MNG-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300866#comment-17300866 ] Hudson commented on MNG-7110: - Build unstable in Jenkins: Maven » Maven TLP » maven » MRESOLVER-157 #7 See

[jira] [Commented] (MNG-7051) Optionally skip non-existing profiles

[ https://issues.apache.org/jira/browse/MNG-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300865#comment-17300865 ] Hudson commented on MNG-7051: - Build unstable in Jenkins: Maven » Maven TLP » maven » MRESOLVER-157 #7 See

[jira] [Assigned] (MNG-7087) Maven 4 can't build itself with Java 11

[ https://issues.apache.org/jira/browse/MNG-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders reassigned MNG-7087: Assignee: Robert Scholte > Maven 4 can't build itself with Java 11 >

[jira] [Closed] (MNG-7087) Maven 4 can't build itself with Java 11

[ https://issues.apache.org/jira/browse/MNG-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders closed MNG-7087. > Maven 4 can't build itself with Java 11 > --- > >

[jira] [Resolved] (MNG-7087) Maven 4 can't build itself with Java 11

[ https://issues.apache.org/jira/browse/MNG-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Mulders resolved MNG-7087. -- Fix Version/s: (was: 4.0.x-candidate) 4.0.0-alpha-1

[jira] [Commented] (MNG-7087) Maven 4 can't build itself with Java 11

[ https://issues.apache.org/jira/browse/MNG-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300822#comment-17300822 ] Maarten Mulders commented on MNG-7087: -- Can confirm the issue is fixed with {code:java} Apache Maven

[jira] [Commented] (MNG-7087) Maven 4 can't build itself with Java 11

[ https://issues.apache.org/jira/browse/MNG-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300807#comment-17300807 ] Robert Scholte commented on MNG-7087: - I've merged MNG-7111, now I cannot reproduce this issue anymore.

[jira] [Commented] (MNG-7111) Deadlock when reading pom

[ https://issues.apache.org/jira/browse/MNG-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300804#comment-17300804 ] Hudson commented on MNG-7111: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #117 See

[GitHub] [maven] rfscholte closed pull request #442: [MNG-7111] Fix maven parallel builds

rfscholte closed pull request #442: URL: https://github.com/apache/maven/pull/442 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[GitHub] [maven] rfscholte commented on pull request #442: [MNG-7111] Fix maven parallel builds

rfscholte commented on pull request #442: URL: https://github.com/apache/maven/pull/442#issuecomment-798157524 Merged with https://github.com/apache/maven/commit/9e19b57c720d226b0b30992535819f700a665d14 Thanks for this PR!

[jira] [Closed] (MNG-7111) Deadlock when reading pom

[ https://issues.apache.org/jira/browse/MNG-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-7111. --- Fix Version/s: 4.0.0-alpha-1 4.0.0 Assignee: Robert Scholte

[GitHub] [maven-surefire] rmannibucau commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified

rmannibucau commented on a change in pull request #340: URL: https://github.com/apache/maven-surefire/pull/340#discussion_r593720594 ## File path: maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java ## @@ -3623,9 +3623,20 @@ public

[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified

Tibor17 commented on a change in pull request #340: URL: https://github.com/apache/maven-surefire/pull/340#discussion_r593718690 ## File path: maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java ## @@ -3623,9 +3623,20 @@ public void

[GitHub] [maven-surefire] Tibor17 commented on a change in pull request #340: [SUREFIRE-1892] ensure systemPropertyVariables values are stringified

Tibor17 commented on a change in pull request #340: URL: https://github.com/apache/maven-surefire/pull/340#discussion_r593718690 ## File path: maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java ## @@ -3623,9 +3623,20 @@ public void