[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other
[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523615#comment-17523615 ] Michael Osipov commented on MNG-7433: - Can we summarize what was the issue for otherf if or when they trip over? > [REGRESSION] Multiple maven instances working on same source tree can lock > each other > - > > Key: MNG-7433 > URL: https://issues.apache.org/jira/browse/MNG-7433 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Dan Tran >Priority: Major > > I have a large multi modules java maven build where: > * phase 1 - basic build + unit tests + jacoco - 40 min > * phase 2 - sonar:sonar 20 min > * phase 3 - final packaging and basic smoke-test - 20 min > To take advantage of Maven multi-threaded build, during the reactor build, > one of our maven module spins another instance of Maven to run sonar:sonar > goal right after the basic build is done. > This means our phase 2 and phase 3 run in parallel sharing the same source > tree, same local maven repo (where sonar:sonar should have all needed > dependencies at the share local maven repo to run its task) > With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked > until phase 2 is done. > I am able to trace it to https://github.com/apache/maven/pull/628 where the > locking started the happen > How does the lock mechanic work? there must be a local file where both Maven > instances are watching each other. Is there an option to disable this lock? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other
[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523616#comment-17523616 ] Dan Tran commented on MNG-7433: --- basically, all running mojo executions in a reactor multi-thread build must be non-aggregator mojos > [REGRESSION] Multiple maven instances working on same source tree can lock > each other > - > > Key: MNG-7433 > URL: https://issues.apache.org/jira/browse/MNG-7433 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Dan Tran >Priority: Major > > I have a large multi modules java maven build where: > * phase 1 - basic build + unit tests + jacoco - 40 min > * phase 2 - sonar:sonar 20 min > * phase 3 - final packaging and basic smoke-test - 20 min > To take advantage of Maven multi-threaded build, during the reactor build, > one of our maven module spins another instance of Maven to run sonar:sonar > goal right after the basic build is done. > This means our phase 2 and phase 3 run in parallel sharing the same source > tree, same local maven repo (where sonar:sonar should have all needed > dependencies at the share local maven repo to run its task) > With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked > until phase 2 is done. > I am able to trace it to https://github.com/apache/maven/pull/628 where the > locking started the happen > How does the lock mechanic work? there must be a local file where both Maven > instances are watching each other. Is there an option to disable this lock? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-6276) Support Reproducible Builds (https://reproducible-builds.org)
[ https://issues.apache.org/jira/browse/MNG-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523622#comment-17523622 ] Herve Boutemy commented on MNG-6276: Reproducible Builds is now considered done: - user documentation: https://maven.apache.org/guides/mini/guide-reproducible-builds.html - artifact:check-buildplan to track plugins with issues: https://maven.apache.org/plugins/maven-artifact-plugin/plugin-issues.html > Support Reproducible Builds (https://reproducible-builds.org) > - > > Key: MNG-6276 > URL: https://issues.apache.org/jira/browse/MNG-6276 > Project: Maven > Issue Type: New Feature > Components: Core, General >Reporter: Paolo Sacconier >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > A venerable build system like Maven should support full build reproducibilty > (i.e. producing bit a bit identical binaries from the same source). > As initiatives like https://reproducible-builds.org gain traction and the > news of the recent Debian policy change to mandate this build behavior (see > https://reproducible.alioth.debian.org/blog/posts/121/), this seems a feature > that needs to be considered for inclusion into Maven core & core plugins. > There is an independent ongoing effort to support this feature and the author > stated that he has found interest from maven project to integrate his work: > https://github.com/Zlika/reproducible-build-maven-plugin/issues/6#issuecomment-325005883 > I hope this issue helps kickstart the effort. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MNG-6276) Support Reproducible Builds (https://reproducible-builds.org)
[ https://issues.apache.org/jira/browse/MNG-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-6276. -- Assignee: Herve Boutemy Resolution: Fixed > Support Reproducible Builds (https://reproducible-builds.org) > - > > Key: MNG-6276 > URL: https://issues.apache.org/jira/browse/MNG-6276 > Project: Maven > Issue Type: New Feature > Components: Core, General >Reporter: Paolo Sacconier >Assignee: Herve Boutemy >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > A venerable build system like Maven should support full build reproducibilty > (i.e. producing bit a bit identical binaries from the same source). > As initiatives like https://reproducible-builds.org gain traction and the > news of the recent Debian policy change to mandate this build behavior (see > https://reproducible.alioth.debian.org/blog/posts/121/), this seems a feature > that needs to be considered for inclusion into Maven core & core plugins. > There is an independent ongoing effort to support this feature and the author > stated that he has found interest from maven project to integrate his work: > https://github.com/Zlika/reproducible-build-maven-plugin/issues/6#issuecomment-325005883 > I hope this issue helps kickstart the effort. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other
[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523627#comment-17523627 ] Michael Osipov commented on MNG-7433: - But this would also affect some of our plugins, like Javadoc. [~gnodet], I haven't followed the discussion sharply, but there is no way to avoid this? Alternatively, can be log a warning about this? > [REGRESSION] Multiple maven instances working on same source tree can lock > each other > - > > Key: MNG-7433 > URL: https://issues.apache.org/jira/browse/MNG-7433 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Dan Tran >Priority: Major > > I have a large multi modules java maven build where: > * phase 1 - basic build + unit tests + jacoco - 40 min > * phase 2 - sonar:sonar 20 min > * phase 3 - final packaging and basic smoke-test - 20 min > To take advantage of Maven multi-threaded build, during the reactor build, > one of our maven module spins another instance of Maven to run sonar:sonar > goal right after the basic build is done. > This means our phase 2 and phase 3 run in parallel sharing the same source > tree, same local maven repo (where sonar:sonar should have all needed > dependencies at the share local maven repo to run its task) > With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked > until phase 2 is done. > I am able to trace it to https://github.com/apache/maven/pull/628 where the > locking started the happen > How does the lock mechanic work? there must be a local file where both Maven > instances are watching each other. Is there an option to disable this lock? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-doxia-converter] slachiewicz merged pull request #23: Bump doxia-tools from 34 to 35
slachiewicz merged PR #23: URL: https://github.com/apache/maven-doxia-converter/pull/23 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-doxia-converter] slachiewicz merged pull request #24: Bump icu4j from 70.1 to 71.1
slachiewicz merged PR #24: URL: https://github.com/apache/maven-doxia-converter/pull/24 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MPDF-100) Remove remains of org.codehaus.doxia.sink.Sink
Michael Osipov created MPDF-100: --- Summary: Remove remains of org.codehaus.doxia.sink.Sink Key: MPDF-100 URL: https://issues.apache.org/jira/browse/MPDF-100 Project: Maven PDF Plugin Issue Type: Task Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 1.6.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MPDF-101) Upgrade Maven to 3.2.5
Michael Osipov created MPDF-101: --- Summary: Upgrade Maven to 3.2.5 Key: MPDF-101 URL: https://issues.apache.org/jira/browse/MPDF-101 Project: Maven PDF Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 1.6.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MPDF-102) Upgrade Maven Plugin Plugin to 3.6.4
Michael Osipov created MPDF-102: --- Summary: Upgrade Maven Plugin Plugin to 3.6.4 Key: MPDF-102 URL: https://issues.apache.org/jira/browse/MPDF-102 Project: Maven PDF Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 1.6.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MJAVADOC-713) Skipping Javadoc reportset leaves empty Javadoc link in site
[ https://issues.apache.org/jira/browse/MJAVADOC-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua updated MJAVADOC-713: Attachment: sampleproject.zip > Skipping Javadoc reportset leaves empty Javadoc link in site > > > Key: MJAVADOC-713 > URL: https://issues.apache.org/jira/browse/MJAVADOC-713 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Joshua >Priority: Major > Fix For: waiting-for-feedback > > Attachments: image-2022-04-15-17-47-49-771.png, sampleproject.zip > > > I am trying to skip a reportset that is inherited from a parent pom > This is what the report plugin looks like in the parent pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > javadoc-no-fork > > javadoc-no-fork > > > > test-javadoc-no-fork > > test-javadoc-no-fork > > > package > > > > > I don't want the test-javadoc-no-fork report in my project > > If I do this in my pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > test-javadoc-no-fork > > true > > > > > > It will skip the Javadoc generation but still adds a link to site and when > you click on the link you get a 404 since the test Javadoc wasn't inherited. > !image-2022-04-15-17-47-49-771.png! > I logged this as a defect because I would think skip would prevent the > Javadoc generation and NOT add a link to the site for a report set that > wasn't generated. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MJAVADOC-713) Skipping Javadoc reportset leaves empty Javadoc link in site
[ https://issues.apache.org/jira/browse/MJAVADOC-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523671#comment-17523671 ] Joshua commented on MJAVADOC-713: - Added. Just run mvn clean verify site. I included the target folder in case you didn't want to run "mvn clean verify site" To simplify the example I didn't use the parent pom. In my use case a parent pom is involved but I can reproduce the same issue without it. > Skipping Javadoc reportset leaves empty Javadoc link in site > > > Key: MJAVADOC-713 > URL: https://issues.apache.org/jira/browse/MJAVADOC-713 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Joshua >Priority: Major > Fix For: waiting-for-feedback > > Attachments: image-2022-04-15-17-47-49-771.png, sampleproject.zip > > > I am trying to skip a reportset that is inherited from a parent pom > This is what the report plugin looks like in the parent pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > javadoc-no-fork > > javadoc-no-fork > > > > test-javadoc-no-fork > > test-javadoc-no-fork > > > package > > > > > I don't want the test-javadoc-no-fork report in my project > > If I do this in my pom > > org.apache.maven.plugins > maven-javadoc-plugin > > > test-javadoc-no-fork > > true > > > > > > It will skip the Javadoc generation but still adds a link to site and when > you click on the link you get a 404 since the test Javadoc wasn't inherited. > !image-2022-04-15-17-47-49-771.png! > I logged this as a defect because I would think skip would prevent the > Javadoc generation and NOT add a link to the site for a report set that > wasn't generated. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MPDF-103) Upgrade plugins in ITs
Michael Osipov created MPDF-103: --- Summary: Upgrade plugins in ITs Key: MPDF-103 URL: https://issues.apache.org/jira/browse/MPDF-103 Project: Maven PDF Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 1.6.0 * Maven Clean Plugin to 3.2.0 * Maven Project Info Reports Plugin to 3.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MPDF-102) Upgrade Maven Plugin Plugin to 3.6.4
[ https://issues.apache.org/jira/browse/MPDF-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPDF-102. --- Resolution: Fixed Fixed with [f9c3095ddee783de18da3ff0ee230ebd8b09ba06|https://gitbox.apache.org/repos/asf?p=maven-pdf-plugin.git;a=commit;h=f9c3095ddee783de18da3ff0ee230ebd8b09ba06]. > Upgrade Maven Plugin Plugin to 3.6.4 > > > Key: MPDF-102 > URL: https://issues.apache.org/jira/browse/MPDF-102 > Project: Maven PDF Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MPDF-100) Remove remains of org.codehaus.doxia.sink.Sink
[ https://issues.apache.org/jira/browse/MPDF-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPDF-100. --- Resolution: Fixed Fixed with [8f89c50d3144b49401f94607f6ea19c30878eb97|https://gitbox.apache.org/repos/asf?p=maven-pdf-plugin.git;a=commit;h=8f89c50d3144b49401f94607f6ea19c30878eb97]. > Remove remains of org.codehaus.doxia.sink.Sink > -- > > Key: MPDF-100 > URL: https://issues.apache.org/jira/browse/MPDF-100 > Project: Maven PDF Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MPDF-101) Upgrade Maven to 3.2.5
[ https://issues.apache.org/jira/browse/MPDF-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPDF-101. --- Resolution: Fixed Fixed with [633df598fec78fbaf6281f6ac8add33957032090|https://gitbox.apache.org/repos/asf?p=maven-pdf-plugin.git;a=commit;h=633df598fec78fbaf6281f6ac8add33957032090]. > Upgrade Maven to 3.2.5 > -- > > Key: MPDF-101 > URL: https://issues.apache.org/jira/browse/MPDF-101 > Project: Maven PDF Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MPDF-103) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MPDF-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MPDF-103. --- Resolution: Fixed Fixed with [80eaf0ede5ad96ea77b8ce12400ca9dda77c4142|https://gitbox.apache.org/repos/asf?p=maven-pdf-plugin.git;a=commit;h=80eaf0ede5ad96ea77b8ce12400ca9dda77c4142]. > Upgrade plugins in ITs > -- > > Key: MPDF-103 > URL: https://issues.apache.org/jira/browse/MPDF-103 > Project: Maven PDF Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > > * Maven Clean Plugin to 3.2.0 > * Maven Project Info Reports Plugin to 3.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MPDF-102) Upgrade Maven Plugin Plugin to 3.6.4
[ https://issues.apache.org/jira/browse/MPDF-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523682#comment-17523682 ] Hudson commented on MPDF-102: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pdf-plugin » master #9 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pdf-plugin/job/master/9/ > Upgrade Maven Plugin Plugin to 3.6.4 > > > Key: MPDF-102 > URL: https://issues.apache.org/jira/browse/MPDF-102 > Project: Maven PDF Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MPDF-101) Upgrade Maven to 3.2.5
[ https://issues.apache.org/jira/browse/MPDF-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523681#comment-17523681 ] Hudson commented on MPDF-101: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pdf-plugin » master #9 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pdf-plugin/job/master/9/ > Upgrade Maven to 3.2.5 > -- > > Key: MPDF-101 > URL: https://issues.apache.org/jira/browse/MPDF-101 > Project: Maven PDF Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MPDF-103) Upgrade plugins in ITs
[ https://issues.apache.org/jira/browse/MPDF-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523683#comment-17523683 ] Hudson commented on MPDF-103: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pdf-plugin » master #9 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pdf-plugin/job/master/9/ > Upgrade plugins in ITs > -- > > Key: MPDF-103 > URL: https://issues.apache.org/jira/browse/MPDF-103 > Project: Maven PDF Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > > * Maven Clean Plugin to 3.2.0 > * Maven Project Info Reports Plugin to 3.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MPDF-100) Remove remains of org.codehaus.doxia.sink.Sink
[ https://issues.apache.org/jira/browse/MPDF-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523680#comment-17523680 ] Hudson commented on MPDF-100: - Build succeeded in Jenkins: Maven » Maven TLP » maven-pdf-plugin » master #9 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pdf-plugin/job/master/9/ > Remove remains of org.codehaus.doxia.sink.Sink > -- > > Key: MPDF-100 > URL: https://issues.apache.org/jira/browse/MPDF-100 > Project: Maven PDF Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.6.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-pdf-plugin] dependabot[bot] commented on pull request #21: Bump mavenVersion from 3.1.1 to 3.8.5
dependabot[bot] commented on PR #21: URL: https://github.com/apache/maven-pdf-plugin/pull/21#issuecomment-1101394028 Looks like these dependencies are updatable in another way, so this is no longer needed. -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pdf-plugin] dependabot[bot] closed pull request #21: Bump mavenVersion from 3.1.1 to 3.8.5
dependabot[bot] closed pull request #21: Bump mavenVersion from 3.1.1 to 3.8.5 URL: https://github.com/apache/maven-pdf-plugin/pull/21 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pdf-plugin] dependabot[bot] opened a new pull request, #23: Bump mavenVersion from 3.2.5 to 3.8.5
dependabot[bot] opened a new pull request, #23: URL: https://github.com/apache/maven-pdf-plugin/pull/23 Bumps `mavenVersion` from 3.2.5 to 3.8.5. Updates `maven-core` from 3.2.5 to 3.8.5 Release notes Sourced from https://github.com/apache/maven/releases";>maven-core's releases. 3.8.5 What's Changed [3.8.x][MNG-7156][MNG-7285] Add locking in MojoExecutor by https://github.com/gnodet";>@gnodet in https://github-redirect.dependabot.com/apache/maven/pull/628";>apache/maven#628 [MNG-6326] Make the build fail if core extensions can not be loaded by https://github.com/gnodet";>@gnodet in https://github-redirect.dependabot.com/apache/maven/pull/648";>apache/maven#648 [3.8.x][MNG-7347] SessionScoped beans should be singletons for a given session by https://github.com/gnodet";>@gnodet in https://github-redirect.dependabot.com/apache/maven/pull/653";>apache/maven#653 [3.8.x][MNG-7386] Make sure the ModelMerger$MergingList can be serialized by https://github.com/gnodet";>@gnodet in https://github-redirect.dependabot.com/apache/maven/pull/656";>apache/maven#656 [3.8.x][MNG-7349] Limit relocation warning message to direct dependencies only by https://github.com/gnodet";>@gnodet in https://github-redirect.dependabot.com/apache/maven/pull/657";>apache/maven#657 [3.8.x][MNG-6727] Changed expression check to project.version and project.parent.version by https://github.com/gnodet";>@gnodet in https://github-redirect.dependabot.com/apache/maven/pull/670";>apache/maven#670 [3.8.x][MNG-7395] - Support system-properties in extension.xml by https://github.com/laeubi";>@laeubi in https://github-redirect.dependabot.com/apache/maven/pull/673";>apache/maven#673 New Contributors https://github.com/laeubi";>@laeubi made their first contribution in https://github-redirect.dependabot.com/apache/maven/pull/673";>apache/maven#673 Full Changelog: https://github.com/apache/maven/compare/maven-3.8.4...maven-3.8.5";>https://github.com/apache/maven/compare/maven-3.8.4...maven-3.8.5 3.8.4 What's Changed [MNG-6302] logging the module count by https://github.com/rmannibucau";>@rmannibucau in https://github-redirect.dependabot.com/apache/maven/pull/136";>apache/maven#136 [MNG-6424] - Upgrade plexus-interpolation to 1.25 by https://github.com/shemic87";>@shemic87 in https://github-redirect.dependabot.com/apache/maven/pull/172";>apache/maven#172 Update Jenkins build to use Maven 3.5.4 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/179";>apache/maven#179 [MNG-6473] Update Mockito to 2.21.0 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/181";>apache/maven#181 MNG-6414 Add more Apache license headers to skip downloading license … by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/167";>apache/maven#167 [MNG-6479] Upgrade XMLUnit to 2.2.1 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/183";>apache/maven#183 Fixed typo in exception logging by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/170";>apache/maven#170 [MNG-6490] Maven fails reporting circular dependency when the depende… by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/188";>apache/maven#188 [MNG-6261] - using java File api to compare by https://github.com/fabcipriano";>@fabcipriano in https://github-redirect.dependabot.com/apache/maven/pull/192";>apache/maven#192 MNG-6529 - ProjectBuild.build(projectsList, ...) ignores request.isResolveDependencies() by https://github.com/mickaelistria";>@mickaelistria in https://github-redirect.dependabot.com/apache/maven/pull/193";>apache/maven#193 [MNG-6559] Fix mailing list URL by https://github.com/johnlinp";>@johnlinp in https://github-redirect.dependabot.com/apache/maven/pull/230";>apache/maven#230 [MNG-6611] Update animal-sniffer-maven-plugin to version 1.17 by https://github.com/slachiewicz";>@slachiewicz in https://github-redirect.dependabot.com/apache/maven/pull/237";>apache/maven#237 [MNG-6405] Fix basedir in MavenProject.deepCopy by https://github.com/jglick";>@jglick in https://github-redirect.dependabot.com/apache/maven/pull/225";>apache/maven#225 [MNG-6655] Add support for "release" qualifier by https://github.com/michael-o";>@michael-o in https://github-redirect.dependabot.com/apache/maven/pull/249";>apache/maven#249 Always deploy snapshot from master by https://github.com/mickaelistria";>@mickaelistria in https://github-redirect.dependabot.com/apache/maven/pull/250";>apache/maven#250 [MNG-6665] toolchain.xml file should support environment variables by https://github.com/MartinKanters";>@MartinKanters in https://github-
[jira] [Created] (MPLUGINTESTING-71) Require Java 8
Sylwester Lachiewicz created MPLUGINTESTING-71: -- Summary: Require Java 8 Key: MPLUGINTESTING-71 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-71 Project: Maven Plugin Testing Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-pdf-plugin] dependabot[bot] commented on pull request #23: Bump mavenVersion from 3.2.5 to 3.8.5
dependabot[bot] commented on PR #23: URL: https://github.com/apache/maven-pdf-plugin/pull/23#issuecomment-1101443614 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pdf-plugin] asfgit closed pull request #23: Bump mavenVersion from 3.2.5 to 3.8.5
asfgit closed pull request #23: Bump mavenVersion from 3.2.5 to 3.8.5 URL: https://github.com/apache/maven-pdf-plugin/pull/23 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pdf-plugin] slachiewicz commented on pull request #20: Bump maven-plugins from 34 to 35
slachiewicz commented on PR #20: URL: https://github.com/apache/maven-pdf-plugin/pull/20#issuecomment-1101453530 @dependabot rebase -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523785#comment-17523785
]
Daniel Subelman commented on SUREFIRE-2063:
---
[~tibordigana], thanks for the explanation and for helping to fix the issue.
Any plan to release this fix soon?
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523819#comment-17523819
]
Tibor Digana commented on SUREFIRE-2063:
[~dsubel]
We have also our internal needs. It is very difficult to explain.
Unfortunatelly non-Maven guys cannot see the release backlog, it's the Jira
issue, therefore we have published the roadmap on the Surefire site.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ARCHETYPE-606) There is no way to include .gitignore files for the jar goal
[
https://issues.apache.org/jira/browse/ARCHETYPE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523823#comment-17523823
]
Felipe Jaekel commented on ARCHETYPE-606:
-
{{What about when mvn archetype:create-from-project is used?}}
> There is no way to include .gitignore files for the jar goal
>
>
> Key: ARCHETYPE-606
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-606
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.2.0
> Environment: CentOS 7 64bits, OpenJDK 11.0.7, Maven 3.6.3, Maven
> Archetype Plugin 3.2.0
>Reporter: Joël Royer
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.2.1
>
>
> In a Maven archetype, I'm using the resource plugin to copy some files like a
> .gitignore template. But this file is not copied when I generate a project
> from this artefact.
> Here is my config for the resource plugin in my artefact:
> {code:java}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 3.1.0
>
>
>
> false
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MEJB-131) Upgrade Maven to 3.2.5
[ https://issues.apache.org/jira/browse/MEJB-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MEJB-131: Summary: Upgrade Maven to 3.2.5 (was: Update plugin (requires Maven 3.2.5+)) > Upgrade Maven to 3.2.5 > -- > > Key: MEJB-131 > URL: https://issues.apache.org/jira/browse/MEJB-131 > Project: Maven EJB Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.2.0 > > > Update plugin changes: > * set required Maven version to 3.2.5 > * make maven bits provided scope > * update dependencies -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-ejb-plugin] asfgit closed pull request #16: [MEJB-131] Update plugin (requires Maven 3.2.5+)
asfgit closed pull request #16: [MEJB-131] Update plugin (requires Maven 3.2.5+) URL: https://github.com/apache/maven-ejb-plugin/pull/16 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MEJB-131) Upgrade Maven to 3.2.5
[ https://issues.apache.org/jira/browse/MEJB-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MEJB-131. --- Resolution: Fixed Fixed with [a9989595406327579d2ade71607dae383ed2e188|https://gitbox.apache.org/repos/asf?p=maven-ejb-plugin.git;a=commit;h=a9989595406327579d2ade71607dae383ed2e188]. > Upgrade Maven to 3.2.5 > -- > > Key: MEJB-131 > URL: https://issues.apache.org/jira/browse/MEJB-131 > Project: Maven EJB Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.2.0 > > > Update plugin changes: > * set required Maven version to 3.2.5 > * make maven bits provided scope > * update dependencies -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-surefire] mthmulders commented on pull request #523: [SUREFIRE-2063] Remove tabs in forked JVM arguments
mthmulders commented on PR #523: URL: https://github.com/apache/maven-surefire/pull/523#issuecomment-1101635910 > Is it possible to find very similar and existing IT with argLine and make such addons with white spaces? Looking into that. Strange thing: when I wrote the IT, I made sure it failed without the change in `DefaultForkConfiguration` - but now it seems that change has no effect and the test fails for another reason. **This change is definitely not mergeable yet!** -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MEJB-131) Upgrade Maven to 3.2.5
[ https://issues.apache.org/jira/browse/MEJB-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523829#comment-17523829 ] Hudson commented on MEJB-131: - Build failed in Jenkins: Maven » Maven TLP » maven-ejb-plugin » master #5 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-ejb-plugin/job/master/5/ > Upgrade Maven to 3.2.5 > -- > > Key: MEJB-131 > URL: https://issues.apache.org/jira/browse/MEJB-131 > Project: Maven EJB Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.2.0 > > > Update plugin changes: > * set required Maven version to 3.2.5 > * make maven bits provided scope > * update dependencies -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523819#comment-17523819
]
Tibor Digana edited comment on SUREFIRE-2063 at 4/18/22 6:36 PM:
-
[~dsubel]
We have also our internal needs. Difficult to explain in short. Unfortunatelly
non-Maven guys cannot see the release backlog, it's the Jira issue, therefore
we have published the roadmap on the Surefire site.
was (Author: tibor17):
[~dsubel]
We have also our internal needs. It is very difficult to explain.
Unfortunatelly non-Maven guys cannot see the release backlog, it's the Jira
issue, therefore we have published the roadmap on the Surefire site.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (SUREFIRE-2063) Adding configuration using with --add-opens or --add-exports fails
[
https://issues.apache.org/jira/browse/SUREFIRE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523819#comment-17523819
]
Tibor Digana edited comment on SUREFIRE-2063 at 4/18/22 6:38 PM:
-
[~dsubel]
We have also our internal needs. Difficult to explain briefly. Unfortunatelly
non-Maven guys cannot see the release backlog, it's the Jira issue, therefore
we have published the roadmap on the Surefire site.
was (Author: tibor17):
[~dsubel]
We have also our internal needs. Difficult to explain in short. Unfortunatelly
non-Maven guys cannot see the release backlog, it's the Jira issue, therefore
we have published the roadmap on the Surefire site.
> Adding configuration using with --add-opens or --add-exports fails
>
>
> Key: SUREFIRE-2063
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2063
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Daniel Subelman
>Priority: Blocker
>
> Since v3.3.0-M6 fails when using to export or open a package. The
> failure is produced when using --add-opens or --add-exports in .
> The execution doesn't fail with v3.3.0-M5 or earlier.
> As an example, it fails when using the following :
> {code:java}
>
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
> --add-opens
> org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED
>
> {code}
> The failure log:
> {code:java}
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (dev) @ testing ---
> [INFO] Using auto detected provider
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> WARNING: Unknown module: org.junit.platform.commons specified to --add-opens
> Error: Could not find or load main class --add-opens
> Caused by: java.lang.ClassNotFoundException: --add-opens
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 9.157 s
> [INFO] Finished at: 2022-04-06T16:28:23-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (dev) on project
> testing:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (MEJB-133) Upgrade to Java 8
Michael Osipov created MEJB-133: --- Summary: Upgrade to Java 8 Key: MEJB-133 URL: https://issues.apache.org/jira/browse/MEJB-133 Project: Maven EJB Plugin Issue Type: Task Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-ejb-plugin] dependabot[bot] opened a new pull request, #17: Bump commons-io from 2.6 to 2.7
dependabot[bot] opened a new pull request, #17: URL: https://github.com/apache/maven-ejb-plugin/pull/17 Bumps commons-io from 2.6 to 2.7. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-ejb-plugin/network/alerts). -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MEJB-133) Upgrade to Java 8
[ https://issues.apache.org/jira/browse/MEJB-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MEJB-133. --- Resolution: Fixed Fixed with [fdb287fa8d3f677d4cc23a89e2802cc78d5dd998|https://gitbox.apache.org/repos/asf?p=maven-ejb-plugin.git;a=commit;h=fdb287fa8d3f677d4cc23a89e2802cc78d5dd998]. > Upgrade to Java 8 > - > > Key: MEJB-133 > URL: https://issues.apache.org/jira/browse/MEJB-133 > Project: Maven EJB Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MEJB-133) Upgrade to Java 8
[ https://issues.apache.org/jira/browse/MEJB-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523839#comment-17523839 ] Hudson commented on MEJB-133: - Build failed in Jenkins: Maven » Maven TLP » maven-ejb-plugin » master #6 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-ejb-plugin/job/master/6/ > Upgrade to Java 8 > - > > Key: MEJB-133 > URL: https://issues.apache.org/jira/browse/MEJB-133 > Project: Maven EJB Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MEJB-133) Upgrade to Java 8
[ https://issues.apache.org/jira/browse/MEJB-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523840#comment-17523840 ] Hudson commented on MEJB-133: - Build failed in Jenkins: Maven » Maven TLP » maven-ejb-plugin » master #7 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-ejb-plugin/job/master/7/ > Upgrade to Java 8 > - > > Key: MEJB-133 > URL: https://issues.apache.org/jira/browse/MEJB-133 > Project: Maven EJB Plugin > Issue Type: Task >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-ear-plugin] michael-o commented on pull request #46: [MEAR-304] Update plugin dependencies
michael-o commented on PR #46: URL: https://github.com/apache/maven-ear-plugin/pull/46#issuecomment-1101668002 @cstamas Can you rework this for Maven 3.2.5? I would then finalize the release. -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MANTRUN-232) Upgrade Maven to 3.2.5
[ https://issues.apache.org/jira/browse/MANTRUN-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MANTRUN-232: --- Summary: Upgrade Maven to 3.2.5 (was: Update plugin (requires Maven 3.2.5+)) > Upgrade Maven to 3.2.5 > -- > > Key: MANTRUN-232 > URL: https://issues.apache.org/jira/browse/MANTRUN-232 > Project: Maven Antrun Plugin > Issue Type: Task >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.1.0 > > > Update dependencies: > * up required Maven version to 3.2.5+ > * set maven bits to provided scope -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (MANTRUN-236) Upgrade Maven Plugin Plugin to 3.6.4
Michael Osipov created MANTRUN-236: -- Summary: Upgrade Maven Plugin Plugin to 3.6.4 Key: MANTRUN-236 URL: https://issues.apache.org/jira/browse/MANTRUN-236 Project: Maven Antrun Plugin Issue Type: Dependency upgrade Reporter: Michael Osipov Assignee: Michael Osipov Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MANTRUN-235) File permissions are missing
[ https://issues.apache.org/jira/browse/MANTRUN-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523852#comment-17523852 ] Michael Osipov commented on MANTRUN-235: Please provide more information otherwise this will be closed. > File permissions are missing > > > Key: MANTRUN-235 > URL: https://issues.apache.org/jira/browse/MANTRUN-235 > Project: Maven Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 >Reporter: whh >Priority: Major > Fix For: waiting-for-feedback > > > Source file permissions 775 exist, but to zip or tar.gz permissions change > 644. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MANTRUN-235) File permissions are missing
[ https://issues.apache.org/jira/browse/MANTRUN-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MANTRUN-235: --- Fix Version/s: waiting-for-feedback > File permissions are missing > > > Key: MANTRUN-235 > URL: https://issues.apache.org/jira/browse/MANTRUN-235 > Project: Maven Antrun Plugin > Issue Type: Bug >Affects Versions: 1.3 >Reporter: whh >Priority: Major > Fix For: waiting-for-feedback > > > Source file permissions 775 exist, but to zip or tar.gz permissions change > 644. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MANTRUN-233) "Usage page" link is broken
[ https://issues.apache.org/jira/browse/MANTRUN-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MANTRUN-233. -- Resolution: Invalid This is Maven Antrun Plugin and its https://maven.apache.org/plugins/maven-antrun-plugin/usage.html is fully working. > "Usage page" link is broken > --- > > Key: MANTRUN-233 > URL: https://issues.apache.org/jira/browse/MANTRUN-233 > Project: Maven Antrun Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Alessio Cecchin >Priority: Major > Labels: link, site > > *Usage Page*'s link on the Main Page of the project is broken. > Land on https://maven.apache.org/plugins/maven-scripting-plugin/usage.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MANTRUN-229) exec target output has newlines converted corrupting binary information
[
https://issues.apache.org/jira/browse/MANTRUN-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MANTRUN-229.
--
Resolution: Incomplete
Whatever happens inside {{gzip(1)}} is out of our control. It if is broken in
Ant, then you need to talk to the Ant devs. I see no bug in this plugin.
> exec target output has newlines converted corrupting binary information
> ---
>
> Key: MANTRUN-229
> URL: https://issues.apache.org/jira/browse/MANTRUN-229
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.8, 3.0.0
>Reporter: Gray
>Priority: Minor
>
> I was trying to use the gzip task but it doesn't support level so I switched
> to using the exec task like the following:
> {noformat}
>
>
>
>
> {noformat}
> Unfortunately, this produced corrupted gzip output. In examining at the
> magic.gz file, I determined that any line end characters that happened to be
> in the binary such as \r were being converted to the platform EOL. The
> output from that command should be binary clean IMO.
> I think I saw it with both the 3.0.0 and 1.8 versions. It may be a failure
> of the underlying ant target code.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (MANTRUN-236) Upgrade Maven Plugin Plugin to 3.6.4
[ https://issues.apache.org/jira/browse/MANTRUN-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MANTRUN-236. -- Resolution: Fixed Fixed with [4e899c4314aa9e1d8ee0e6b17844c849359c42ce|https://gitbox.apache.org/repos/asf?p=maven-antrun-plugin.git;a=commit;h=4e899c4314aa9e1d8ee0e6b17844c849359c42ce]. > Upgrade Maven Plugin Plugin to 3.6.4 > > > Key: MANTRUN-236 > URL: https://issues.apache.org/jira/browse/MANTRUN-236 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request, #47: Bump ant from 1.10.10 to 1.10.11 in /src/it/filesets-test
dependabot[bot] opened a new pull request, #47: URL: https://github.com/apache/maven-antrun-plugin/pull/47 Bumps ant from 1.10.10 to 1.10.11. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-antrun-plugin/network/alerts). -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz commented on pull request #46: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2
slachiewicz commented on PR #46: URL: https://github.com/apache/maven-antrun-plugin/pull/46#issuecomment-1101688481 @dependabot rebase -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz commented on pull request #45: Bump maven-javadoc-plugin from 3.3.1 to 3.3.2
slachiewicz commented on PR #45: URL: https://github.com/apache/maven-antrun-plugin/pull/45#issuecomment-1101688662 @dependabot rebase -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz commented on pull request #41: Bump maven-plugin-plugin from 3.6.2 to 3.6.4
slachiewicz commented on PR #41: URL: https://github.com/apache/maven-antrun-plugin/pull/41#issuecomment-1101688906 @dependabot rebase -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz commented on pull request #43: Bump xmlunit-core from 2.8.4 to 2.9.0
slachiewicz commented on PR #43: URL: https://github.com/apache/maven-antrun-plugin/pull/43#issuecomment-1101689094 @dependabot rebase -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz commented on pull request #40: Bump xmlunit-matchers from 2.8.4 to 2.9.0
slachiewicz commented on PR #40: URL: https://github.com/apache/maven-antrun-plugin/pull/40#issuecomment-1101689265 @dependabot rebase -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] commented on pull request #41: Bump maven-plugin-plugin from 3.6.2 to 3.6.4
dependabot[bot] commented on PR #41: URL: https://github.com/apache/maven-antrun-plugin/pull/41#issuecomment-1101694249 Looks like org.apache.maven.plugins:maven-plugin-plugin is up-to-date now, so this is no longer needed. -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] closed pull request #41: Bump maven-plugin-plugin from 3.6.2 to 3.6.4
dependabot[bot] closed pull request #41: Bump maven-plugin-plugin from 3.6.2 to 3.6.4 URL: https://github.com/apache/maven-antrun-plugin/pull/41 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] mthmulders commented on pull request #523: [SUREFIRE-2063] Remove tabs in forked JVM arguments
mthmulders commented on PR #523: URL: https://github.com/apache/maven-surefire/pull/523#issuecomment-1101695153 > > Is it possible to find very similar and existing IT with argLine and make such addons with white spaces? > > Looking into that. Strange thing: when I wrote the IT, I made sure it failed without the change in `DefaultForkConfiguration` - but now it seems that change has no effect and the test fails for another reason. **This change is definitely not mergeable yet!** Of course. It's always tabs vs. spaces. Replacing spaces with tabs makes the test consistently fail again. I'll get back to this PR later this week! -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MANTRUN-223) Bad links in JavaDoc
[
https://issues.apache.org/jira/browse/MANTRUN-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523869#comment-17523869
]
Michael Osipov commented on MANTRUN-223:
No {{package-list}} anymore:
https://svn.apache.org/repos/asf/ant/site/ant/production/manual/api/
If it is not a misconfiguration on Ant build side, generating on Java 9+ side
with release set to 8 {{package-list}} is not generated, but only
{{element-list}}. Thus, the warning.
Tried to generate Javadoc on Ant with Java 11: Failed with an error.
> Bad links in JavaDoc
>
>
> Key: MANTRUN-223
> URL: https://issues.apache.org/jira/browse/MANTRUN-223
> Project: Maven Antrun Plugin
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> [WARNING] Error fetching link: http://ant.apache.org/apidocs/package-list.
> Ignored it.
> [WARNING] Error fetching link: http://junit.org/apidocs/package-list. Ignored
> it.
> [WARNING] Error fetching link: https://www.xmlunit.org/apidocs/package-list.
> Ignored it.
> [WARNING] Error fetching link: https://www.xmlunit.org/apidocs/package-list.
> Ignored it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (MANTRUN-236) Upgrade Maven Plugin Plugin to 3.6.4
[ https://issues.apache.org/jira/browse/MANTRUN-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523870#comment-17523870 ] Hudson commented on MANTRUN-236: Build succeeded in Jenkins: Maven » Maven TLP » maven-antrun-plugin » master #5 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-antrun-plugin/job/master/5/ > Upgrade Maven Plugin Plugin to 3.6.4 > > > Key: MANTRUN-236 > URL: https://issues.apache.org/jira/browse/MANTRUN-236 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MANTRUN-223) Bad links in Javadoc
[ https://issues.apache.org/jira/browse/MANTRUN-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MANTRUN-223: --- Summary: Bad links in Javadoc (was: Bad links in JavaDoc) > Bad links in Javadoc > > > Key: MANTRUN-223 > URL: https://issues.apache.org/jira/browse/MANTRUN-223 > Project: Maven Antrun Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > [WARNING] Error fetching link: http://ant.apache.org/apidocs/package-list. > Ignored it. > [WARNING] Error fetching link: http://junit.org/apidocs/package-list. Ignored > it. > [WARNING] Error fetching link: https://www.xmlunit.org/apidocs/package-list. > Ignored it. > [WARNING] Error fetching link: https://www.xmlunit.org/apidocs/package-list. > Ignored it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MANTRUN-223) Bad links in JavaDoc
[ https://issues.apache.org/jira/browse/MANTRUN-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523871#comment-17523871 ] Michael Osipov commented on MANTRUN-223: Given that my bug reports with Ant are being ignored for 10 years, I won't file anything. > Bad links in JavaDoc > > > Key: MANTRUN-223 > URL: https://issues.apache.org/jira/browse/MANTRUN-223 > Project: Maven Antrun Plugin > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Elliotte Rusty Harold >Priority: Minor > > [WARNING] Error fetching link: http://ant.apache.org/apidocs/package-list. > Ignored it. > [WARNING] Error fetching link: http://junit.org/apidocs/package-list. Ignored > it. > [WARNING] Error fetching link: https://www.xmlunit.org/apidocs/package-list. > Ignored it. > [WARNING] Error fetching link: https://www.xmlunit.org/apidocs/package-list. > Ignored it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-antrun-plugin] slachiewicz merged pull request #46: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2
slachiewicz merged PR #46: URL: https://github.com/apache/maven-antrun-plugin/pull/46 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz merged pull request #45: Bump maven-javadoc-plugin from 3.3.1 to 3.3.2
slachiewicz merged PR #45: URL: https://github.com/apache/maven-antrun-plugin/pull/45 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz merged pull request #43: Bump xmlunit-core from 2.8.4 to 2.9.0
slachiewicz merged PR #43: URL: https://github.com/apache/maven-antrun-plugin/pull/43 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] slachiewicz merged pull request #40: Bump xmlunit-matchers from 2.8.4 to 2.9.0
slachiewicz merged PR #40: URL: https://github.com/apache/maven-antrun-plugin/pull/40 -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MSOURCES-107) documentation of configuration
[ https://issues.apache.org/jira/browse/MSOURCES-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSOURCES-107. --- Resolution: Incomplete No response for years. > documentation of configuration > --- > > Key: MSOURCES-107 > URL: https://issues.apache.org/jira/browse/MSOURCES-107 > Project: Maven Source Plugin > Issue Type: Bug >Affects Versions: 3.0.1 >Reporter: Ernst Reissner >Priority: Minor > > Seems as if includes also work. So the documentation for the plugin is > incomplete. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [maven-surefire] Tibor17 commented on pull request #523: [SUREFIRE-2063] Remove tabs in forked JVM arguments
Tibor17 commented on PR #523: URL: https://github.com/apache/maven-surefire/pull/523#issuecomment-1101729057 @mthmulders Did you use JDK1.8 on your PC when you tested the IT? Look at the GH CI results. All JDKs fail except 1.8. Is this the reason? -- 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 the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 commented on a diff in pull request #517: [SUREFIRE-2064] Allow all supported values of [parallel] option
Tibor17 commented on code in PR #517:
URL: https://github.com/apache/maven-surefire/pull/517#discussion_r852447504
##
surefire-providers/surefire-testng/src/main/java/org/apache/maven/surefire/testng/conf/TestNG740Configurator.java:
##
@@ -37,33 +36,77 @@
*
* @since 3.0.0-M6
*/
-public class TestNG740Configurator extends TestNG60Configurator
+public class TestNG740Configurator
+extends TestNG60Configurator
{
+/**
+ * Convert and apply the value of the [threadcount] option.
+ *
+ * @param suite TestNG {@link XmlSuite} object
+ * @param options Surefire plugin configuration options
+ * @throws TestSetFailedException if unable to convert specified
[threadcount] setting
+ */
@Override
-public void configure( XmlSuite suite, Map options )
+protected void configureThreadCount( XmlSuite suite, Map
options )
throws TestSetFailedException
{
-String threadCountAsString = options.get( THREADCOUNT_PROP );
-int threadCount = threadCountAsString == null ? 1 : parseInt(
threadCountAsString );
-suite.setThreadCount( threadCount );
-
-String parallel = options.get( PARALLEL_PROP );
-if ( parallel != null )
+String threadCount = options.get( THREADCOUNT_PROP );
+// if [threadcount] spec'd
+if ( threadCount != null )
{
-if ( !"methods".equalsIgnoreCase( parallel ) &&
!"classes".equalsIgnoreCase( parallel ) )
+try
{
-throw new TestSetFailedException( "Unsupported TestNG parallel
setting: "
-+ parallel + " ( only METHODS or CLASSES supported )" );
+// convert and apply [threadcount] setting
+suite.setThreadCount( Integer.parseInt( threadCount ) );
Review Comment:
We should not change behavior in this PR. We are only aiming for the fix
regarding configuration with the parameter `parallel`.
Speaking apart of thie PR, I would say that `5` is a kind of Bulgarian value
in IT. The other frameworks do not use arbitrary values like TestNG does. The
surefire providers should behave similar and so the `surefire-junit47` has
fallback value `0`. The developer who wrote the documentation obviously had a
problem with `5`. Not sure if TestNG would have a problem with `0` (main
Thread) and if `1` is a singleton non-main Thread. Feel free to check it out.
--
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 the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other
[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523970#comment-17523970 ] Dan Tran commented on MNG-7433: --- Actually, I firmly believe it has something to do with one of my reactor modules spinning another maven instance/JVM, after that, all other aggregating mojos running at other threads are blocked and again, so far I have no luck reproducing this scenario in a simple way and yes, it would be helpful to print a warning > [REGRESSION] Multiple maven instances working on same source tree can lock > each other > - > > Key: MNG-7433 > URL: https://issues.apache.org/jira/browse/MNG-7433 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Dan Tran >Priority: Major > > I have a large multi modules java maven build where: > * phase 1 - basic build + unit tests + jacoco - 40 min > * phase 2 - sonar:sonar 20 min > * phase 3 - final packaging and basic smoke-test - 20 min > To take advantage of Maven multi-threaded build, during the reactor build, > one of our maven module spins another instance of Maven to run sonar:sonar > goal right after the basic build is done. > This means our phase 2 and phase 3 run in parallel sharing the same source > tree, same local maven repo (where sonar:sonar should have all needed > dependencies at the share local maven repo to run its task) > With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked > until phase 2 is done. > I am able to trace it to https://github.com/apache/maven/pull/628 where the > locking started the happen > How does the lock mechanic work? there must be a local file where both Maven > instances are watching each other. Is there an option to disable this lock? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other
[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523970#comment-17523970 ] Dan Tran edited comment on MNG-7433 at 4/19/22 1:15 AM: Actually, I firmly believe it has something to do with one of my reactor modules spinning another maven instance/JVM, after that, all other aggregating mojos running at other threads are blocked and again, so far I have no luck reproducing this scenario in a simple way and yes, it would be helpful to print a warning showing why it is blocked was (Author: dantran): Actually, I firmly believe it has something to do with one of my reactor modules spinning another maven instance/JVM, after that, all other aggregating mojos running at other threads are blocked and again, so far I have no luck reproducing this scenario in a simple way and yes, it would be helpful to print a warning > [REGRESSION] Multiple maven instances working on same source tree can lock > each other > - > > Key: MNG-7433 > URL: https://issues.apache.org/jira/browse/MNG-7433 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Dan Tran >Priority: Major > > I have a large multi modules java maven build where: > * phase 1 - basic build + unit tests + jacoco - 40 min > * phase 2 - sonar:sonar 20 min > * phase 3 - final packaging and basic smoke-test - 20 min > To take advantage of Maven multi-threaded build, during the reactor build, > one of our maven module spins another instance of Maven to run sonar:sonar > goal right after the basic build is done. > This means our phase 2 and phase 3 run in parallel sharing the same source > tree, same local maven repo (where sonar:sonar should have all needed > dependencies at the share local maven repo to run its task) > With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked > until phase 2 is done. > I am able to trace it to https://github.com/apache/maven/pull/628 where the > locking started the happen > How does the lock mechanic work? there must be a local file where both Maven > instances are watching each other. Is there an option to disable this lock? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (MNG-7433) [REGRESSION] Multiple maven instances working on same source tree can lock each other
[ https://issues.apache.org/jira/browse/MNG-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523970#comment-17523970 ] Dan Tran edited comment on MNG-7433 at 4/19/22 1:16 AM: Actually, I firmly believe it has something to do with one of my reactor modules spinning another maven instance/JVM, after that, all other aggregating mojos running at other threads are blocked and again, so far I have no luck reproducing this scenario in a simple way and yes, it would be helpful to print a warning showing why an mojo-execution is blocked was (Author: dantran): Actually, I firmly believe it has something to do with one of my reactor modules spinning another maven instance/JVM, after that, all other aggregating mojos running at other threads are blocked and again, so far I have no luck reproducing this scenario in a simple way and yes, it would be helpful to print a warning showing why it is blocked > [REGRESSION] Multiple maven instances working on same source tree can lock > each other > - > > Key: MNG-7433 > URL: https://issues.apache.org/jira/browse/MNG-7433 > Project: Maven > Issue Type: Bug >Affects Versions: 3.8.5 >Reporter: Dan Tran >Priority: Major > > I have a large multi modules java maven build where: > * phase 1 - basic build + unit tests + jacoco - 40 min > * phase 2 - sonar:sonar 20 min > * phase 3 - final packaging and basic smoke-test - 20 min > To take advantage of Maven multi-threaded build, during the reactor build, > one of our maven module spins another instance of Maven to run sonar:sonar > goal right after the basic build is done. > This means our phase 2 and phase 3 run in parallel sharing the same source > tree, same local maven repo (where sonar:sonar should have all needed > dependencies at the share local maven repo to run its task) > With maven-3.8.5, parallelization is no longer possible, phase 3 is blocked > until phase 2 is done. > I am able to trace it to https://github.com/apache/maven/pull/628 where the > locking started the happen > How does the lock mechanic work? there must be a local file where both Maven > instances are watching each other. Is there an option to disable this lock? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (MPIR-400) mvn -pl . clean site site:stage fails when extensions are part of pom.xml
[
https://issues.apache.org/jira/browse/MPIR-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-400.
---
Fix Version/s: (was: waiting-for-feedback)
(was: wontfix-candidate)
Resolution: Incomplete
Information provided, no reaction for almost a year.
> mvn -pl . clean site site:stage fails when extensions are part of pom.xml
> -
>
> Key: MPIR-400
> URL: https://issues.apache.org/jira/browse/MPIR-400
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: index, modules
>Affects Versions: 3.0.0, 3.1.0, 3.1.1
> Environment: Apache Maven Version: 3.6.3
> Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_251\jre
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Marwa Khabbaz
>Priority: Major
> Attachments: error_log.txt, example.zip, pom_aggregator.xml,
> pom_sub-module.xml
>
>
> I have a project consisting of an aggregator and a submodule, which inherits
> directly from the aggregator. I have the following scenarios:
> * When I execute {{mvn clean site site:stage}} (without {{-pl .}}), the
> build is successful.
> * When I leave out the extensions out of the {{pom.xml}}-file of my
> aggregator and execute the {{mvn -pl . clean site site:stage}}, the build is
> successful.
> * When I put in extensions to the {{pom.xml}}-file of my aggregator but
> leave out the reports for {{index}} and {{modules}} (the only sites that
> refer to my submodule) by explicitly defining the report set in the
> {{pom.xml}}-file of the aggregator, the build is successful.
> * As soon as I put extensions into the {{pom.xml}}-file of my aggregator and
> leave in the reports for {{index}} and {{modules}}, then execute the build
> {{mvn -pl . clean site site:stage}} for the aggregator, the build fails with
> a {{NullPointerException}}.
> I attached the error log of the last scenario and the {{pom.xml}} of the
> aggregator and its submodule to this ticket. This has never been a problem
> until the release of {{maven-project-info-reports-plugin 3.0.0}}.
> Hopefully I managed to understandably describe my issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (MPIR-415) Wrong old goal name in "Incompatibility Notice" table in website
[ https://issues.apache.org/jira/browse/MPIR-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-415: Fix Version/s: 3.3.0 > Wrong old goal name in "Incompatibility Notice" table in website > > > Key: MPIR-415 > URL: https://issues.apache.org/jira/browse/MPIR-415 > Project: Maven Project Info Reports Plugin > Issue Type: Bug >Reporter: Tilman Hausherr >Priority: Trivial > Fix For: 3.3.0 > > > https://maven.apache.org/plugins/maven-project-info-reports-plugin/ > The "Incompatibility Notice" table has "issue-management" twice. I suspect > the left one should have been "issue-tracking". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (MPIR-415) Wrong old goal name in "Incompatibility Notice" table in website
[ https://issues.apache.org/jira/browse/MPIR-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-415: --- Assignee: Michael Osipov > Wrong old goal name in "Incompatibility Notice" table in website > > > Key: MPIR-415 > URL: https://issues.apache.org/jira/browse/MPIR-415 > Project: Maven Project Info Reports Plugin > Issue Type: Bug >Reporter: Tilman Hausherr >Assignee: Michael Osipov >Priority: Trivial > Fix For: 3.3.0 > > > https://maven.apache.org/plugins/maven-project-info-reports-plugin/ > The "Incompatibility Notice" table has "issue-management" twice. I suspect > the left one should have been "issue-tracking". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (MPIR-399) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MPIR-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-399: --- Assignee: Tamás Cservenák (was: Michael Osipov) > Upgrade to Maven 3.2.5 > -- > > Key: MPIR-399 > URL: https://issues.apache.org/jira/browse/MPIR-399 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (MPIR-399) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MPIR-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MPIR-399: --- Assignee: Michael Osipov > Upgrade to Maven 3.2.5 > -- > > Key: MPIR-399 > URL: https://issues.apache.org/jira/browse/MPIR-399 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (MPIR-399) Upgrade to Maven 3.2.5
[ https://issues.apache.org/jira/browse/MPIR-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPIR-399: Fix Version/s: 3.3.0 > Upgrade to Maven 3.2.5 > -- > > Key: MPIR-399 > URL: https://issues.apache.org/jira/browse/MPIR-399 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Michael Osipov >Priority: Major > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
