[jira] [Updated] (MNG-7468) Unsupported plugins parameters in configuration should be verified
[
https://issues.apache.org/jira/browse/MNG-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MNG-7468:
-
Summary: Unsupported plugins parameters in configuration should be verified
(was: Unsupported plugins parameters in configuration should break build)
> Unsupported plugins parameters in configuration should be verified
> --
>
> Key: MNG-7468
> URL: https://issues.apache.org/jira/browse/MNG-7468
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
>Reporter: Slawomir Jaranowski
>Priority: Major
>
> Currently we can provide any xml tags in plugin configuration even if plugin
> Mojo doesn't support specific parameters.
> eg we can have:
> {code:xml}
>
> example-maven-plugin
> 1.1.1
>
>
>
>
> {code}
> With example configuration Mojo is executed without any warning.
> Simply if parameters is not supported - build should break with some of
> invalid plugin configuration exception ...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (MNG-7468) Unsupported plugins parameters in configuration should be verified
[
https://issues.apache.org/jira/browse/MNG-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned MNG-7468:
Assignee: Slawomir Jaranowski
> Unsupported plugins parameters in configuration should be verified
> --
>
> Key: MNG-7468
> URL: https://issues.apache.org/jira/browse/MNG-7468
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
>
> Currently we can provide any xml tags in plugin configuration even if plugin
> Mojo doesn't support specific parameters.
> eg we can have:
> {code:xml}
>
> example-maven-plugin
> 1.1.1
>
>
>
>
> {code}
> With example configuration Mojo is executed without any warning.
> Simply if parameters is not supported - build should break with some of
> invalid plugin configuration exception ...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MNG-7468) Unsupported plugins parameters in configuration should be verified
[
https://issues.apache.org/jira/browse/MNG-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MNG-7468:
-
Fix Version/s: 3.9.0
4.0.0-alpha-1
4.0.0
> Unsupported plugins parameters in configuration should be verified
> --
>
> Key: MNG-7468
> URL: https://issues.apache.org/jira/browse/MNG-7468
> Project: Maven
> Issue Type: New Feature
> Components: Plugins and Lifecycle
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> Currently we can provide any xml tags in plugin configuration even if plugin
> Mojo doesn't support specific parameters.
> eg we can have:
> {code:xml}
>
> example-maven-plugin
> 1.1.1
>
>
>
>
> {code}
> With example configuration Mojo is executed without any warning.
> Simply if parameters is not supported - build should break with some of
> invalid plugin configuration exception ...
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-ear-plugin] dependabot[bot] opened a new pull request, #53: Bump maven-project-info-reports-plugin from 3.1.1 to 3.3.0
dependabot[bot] opened a new pull request, #53: URL: https://github.com/apache/maven-ear-plugin/pull/53 Bumps [maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin) from 3.1.1 to 3.3.0. Commits https://github.com/apache/maven-project-info-reports-plugin/commit/563a0b261722719f9bf6ead946f3d5e30ef611c8";>563a0b2 [maven-release-plugin] prepare release maven-project-info-reports-plugin-3.3.0 https://github.com/apache/maven-project-info-reports-plugin/commit/9549763fbbdea2ee504412b06c2df1d14c25cb4a";>9549763 [MPIR-416] Upgrade maven-dependency-tree to 3.1.0 https://github.com/apache/maven-project-info-reports-plugin/commit/eab4f24d5cfc44aa91f62bde51e5f8001b36334f";>eab4f24 [MPIR-417] Upgrade Parent to 36 https://github.com/apache/maven-project-info-reports-plugin/commit/3538a85109299b942b3feab5a76b93d6d86d2b5c";>3538a85 Bump project version for next release candidate https://github.com/apache/maven-project-info-reports-plugin/commit/634275979993b45426af278b0c1c886b32fa130a";>6342759 PR template https://github.com/apache/maven-project-info-reports-plugin/commit/8d7b024591e8a4dad675b6a97ebbfb5f86fd2668";>8d7b024 Use shared GitHub actions https://github.com/apache/maven-project-info-reports-plugin/commit/f784eef507716c789c2e05a93750c508ce8b9947";>f784eef [MPIR-399] Upgrade to Maven 3.2.5 https://github.com/apache/maven-project-info-reports-plugin/commit/62f490b101f01215e39a86f2810679a77249e024";>62f490b [MPIR-415] Wrong old goal name in "Incompatibility Notice" table in website https://github.com/apache/maven-project-info-reports-plugin/commit/5bb94e115426c59340db739c9fc3302480528c63";>5bb94e1 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-project-info-reports-plugin/commit/ca84755a9d1f58f6bd39e70457fb0d36ce3755c4";>ca84755 [maven-release-plugin] prepare release maven-project-info-reports-plugin-3.2.2 Additional commits viewable in https://github.com/apache/maven-project-info-reports-plugin/compare/maven-project-info-reports-plugin-3.1.1...maven-project-info-reports-plugin-3.3.0";>compare view [](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) -- 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-ear-plugin] dependabot[bot] commented on pull request #51: Bump maven-project-info-reports-plugin from 3.1.1 to 3.2.2
dependabot[bot] commented on PR #51: URL: https://github.com/apache/maven-ear-plugin/pull/51#issuecomment-1113124670 Superseded by #53. -- 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-ear-plugin] dependabot[bot] closed pull request #51: Bump maven-project-info-reports-plugin from 3.1.1 to 3.2.2
dependabot[bot] closed pull request #51: Bump maven-project-info-reports-plugin from 3.1.1 to 3.2.2 URL: https://github.com/apache/maven-ear-plugin/pull/51 -- 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] (MNG-7469) IBM Z (s390x) Support for Apache Maven Jenkins CI
snehal created MNG-7469: --- Summary: IBM Z (s390x) Support for Apache Maven Jenkins CI Key: MNG-7469 URL: https://issues.apache.org/jira/browse/MNG-7469 Project: Maven Issue Type: Improvement Reporter: snehal Hi, I would like to add support for IBM Z (s390x) into Apache Maven Jenkins CI. What is the process I should follow to add CI support for s390x? Happy to discuss and help with the process. Thanks. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MNG-7464) Warn about using read-only parameters for Mojo in configuration
[ https://issues.apache.org/jira/browse/MNG-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MNG-7464: - Fix Version/s: 3.9.0 4.0.0-alpha-1 4.0.0 > Warn about using read-only parameters for Mojo in configuration > --- > > Key: MNG-7464 > URL: https://issues.apache.org/jira/browse/MNG-7464 > Project: Maven > Issue Type: New Feature >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MSCMPUB-49) Update documentation examples for GitHub/gh-pages
Randall Wood created MSCMPUB-49: --- Summary: Update documentation examples for GitHub/gh-pages Key: MSCMPUB-49 URL: https://issues.apache.org/jira/browse/MSCMPUB-49 Project: Maven SCM Publish Plugin Issue Type: Bug Reporter: Randall Wood GitHub/gh-pages requires the use of Personal Access Tokens with scm-publish (at least if the account has 2FA configured). * Can the documentation mention that and outline the required permissions for the token (I think the repo permissions are the only permissions required)? * Can the documentation discuss how to store this token in a personal settings.xml file? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MNG-7469) IBM Z (s390x) Support for Apache Maven Jenkins CI
[ https://issues.apache.org/jira/browse/MNG-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] snehal updated MNG-7469: Description: Hi, I would like to add support for IBM Z (s390x) into Apache Maven Jenkins CI as Apache INFRA has access to s390x for CI. What is the process I should follow to add CI support for s390x? Happy to discuss and help with the process. Thanks. was: Hi, I would like to add support for IBM Z (s390x) into Apache Maven Jenkins CI. What is the process I should follow to add CI support for s390x? Happy to discuss and help with the process. Thanks. > IBM Z (s390x) Support for Apache Maven Jenkins CI > - > > Key: MNG-7469 > URL: https://issues.apache.org/jira/browse/MNG-7469 > Project: Maven > Issue Type: Improvement >Reporter: snehal >Priority: Major > > Hi, > I would like to add support for IBM Z (s390x) into Apache Maven Jenkins CI as > Apache INFRA has access to s390x for CI. > What is the process I should follow to add CI support for s390x? Happy to > discuss and help with the process. Thanks. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request, #55: Bump maven-project-info-reports-plugin from 3.2.2 to 3.3.0
dependabot[bot] opened a new pull request, #55: URL: https://github.com/apache/maven-antrun-plugin/pull/55 Bumps [maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin) from 3.2.2 to 3.3.0. Commits https://github.com/apache/maven-project-info-reports-plugin/commit/563a0b261722719f9bf6ead946f3d5e30ef611c8";>563a0b2 [maven-release-plugin] prepare release maven-project-info-reports-plugin-3.3.0 https://github.com/apache/maven-project-info-reports-plugin/commit/9549763fbbdea2ee504412b06c2df1d14c25cb4a";>9549763 [MPIR-416] Upgrade maven-dependency-tree to 3.1.0 https://github.com/apache/maven-project-info-reports-plugin/commit/eab4f24d5cfc44aa91f62bde51e5f8001b36334f";>eab4f24 [MPIR-417] Upgrade Parent to 36 https://github.com/apache/maven-project-info-reports-plugin/commit/3538a85109299b942b3feab5a76b93d6d86d2b5c";>3538a85 Bump project version for next release candidate https://github.com/apache/maven-project-info-reports-plugin/commit/634275979993b45426af278b0c1c886b32fa130a";>6342759 PR template https://github.com/apache/maven-project-info-reports-plugin/commit/8d7b024591e8a4dad675b6a97ebbfb5f86fd2668";>8d7b024 Use shared GitHub actions https://github.com/apache/maven-project-info-reports-plugin/commit/f784eef507716c789c2e05a93750c508ce8b9947";>f784eef [MPIR-399] Upgrade to Maven 3.2.5 https://github.com/apache/maven-project-info-reports-plugin/commit/62f490b101f01215e39a86f2810679a77249e024";>62f490b [MPIR-415] Wrong old goal name in "Incompatibility Notice" table in website https://github.com/apache/maven-project-info-reports-plugin/commit/5bb94e115426c59340db739c9fc3302480528c63";>5bb94e1 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/apache/maven-project-info-reports-plugin/compare/maven-project-info-reports-plugin-3.2.2...maven-project-info-reports-plugin-3.3.0";>compare view [](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) -- 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-release] cstamas opened a new pull request, #118: Catch up
cstamas opened a new pull request, #118: URL: https://github.com/apache/maven-release/pull/118 So, nudged the neglected plugin: * off plexus XML (it had _logic_ in there!), fully to JSR330 * off ancient sonatype mvn 3.0 packages to mvn 3.2.5 * off from Junit3 PlexusTestCase w/ XMLs to modern(er) Junit 4 and no XMLs * fixed all the "tweaks" happened in well hidden XML * reformat * cheers! All but two UTs pass that I cannot interpret: https://github.com/apache/maven-release/blob/85d973c87724aa2bc0698e6773dd9ce2a0fc8701/maven-release-manager/src/test/java/org/apache/maven/shared/release/versions/DefaultVersionInfoTest.java#L235-L239 https://github.com/apache/maven-release/blob/85d973c87724aa2bc0698e6773dd9ce2a0fc8701/maven-release-manager/src/test/java/org/apache/maven/shared/release/phase/GenerateReleasePomsPhaseTest.java Former currently does not even run (maven version != 3.0), while latter is most probably due bad diff, probably diff logic in UT needs more "no change" detection. All but one IT pass: [INFO] Building: projects/prepare/oddeven-policy/pom.xml [INFO] The build exited with code 1. See /home/cstamas/Worx/apache-maven/maven-release/maven-release-plugin/target/it/projects/prepare/oddeven-policy/build.log for details. [INFO] projects/prepare/oddeven-policy/pom.xml .. FAILED (1.2 s) But this is due aether-util missing from classpath, will be fixed. -- 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] (MSCMPUB-49) Update documentation examples for GitHub/gh-pages
[ https://issues.apache.org/jira/browse/MSCMPUB-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530035#comment-17530035 ] Michael Osipov commented on MSCMPUB-49: --- PRs welcome > Update documentation examples for GitHub/gh-pages > - > > Key: MSCMPUB-49 > URL: https://issues.apache.org/jira/browse/MSCMPUB-49 > Project: Maven SCM Publish Plugin > Issue Type: Bug >Reporter: Randall Wood >Priority: Major > > GitHub/gh-pages requires the use of Personal Access Tokens with scm-publish > (at least if the account has 2FA configured). > * Can the documentation mention that and outline the required permissions > for the token (I think the repo permissions are the only permissions > required)? > * Can the documentation discuss how to store this token in a personal > settings.xml file? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MRELEASE-839) Unable to supply tag to release for release:perform
[ https://issues.apache.org/jira/browse/MRELEASE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530057#comment-17530057 ] Vilius Šumskas commented on MRELEASE-839: - Almost 10 year later this is still not fixed :( Can we at least have MRELEASE-796 reverted, so we continue using release:perform on a git tag? These changes didn't add any real value and just broke everything. > Unable to supply tag to release for release:perform > --- > > Key: MRELEASE-839 > URL: https://issues.apache.org/jira/browse/MRELEASE-839 > Project: Maven Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.4.1 >Reporter: Tuure Laurinolli >Priority: Major > > The documentation at > http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html > and > http://maven.apache.org/maven-release/maven-release-plugin/plugin-info.html > claims that releases can be ma de of a specific tag, but no mechanism for > this is specified. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-javadoc-plugin] pzygielo closed pull request #127: [MJAVADOC-710] Break the build if replaced or removed property is used
pzygielo closed pull request #127: [MJAVADOC-710] Break the build if replaced or removed property is used URL: https://github.com/apache/maven-javadoc-plugin/pull/127 -- 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] (MCOMPILER-495) createMissingPackageInfoClasses fails in packages that only contain a package-info.java
Jeff Maxwell created MCOMPILER-495:
--
Summary: createMissingPackageInfoClasses fails in packages that
only contain a package-info.java
Key: MCOMPILER-495
URL: https://issues.apache.org/jira/browse/MCOMPILER-495
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.10.1, 3.10.0
Environment: java 17.0.3
MVN 3.8.5
OS Various
Reporter: Jeff Maxwell
createMissingPackageInfoClasses fails in packages that only contain a
package-info.java as the parent path may not be created.
{code:java}
Warning: Error creating missing package info classes
java.nio.file.NoSuchFileException:
/home/runner/work/spring/spring/security/crypto/spring-boot-security-crypto/target/classes/com/myorg/spring/boot/security/crypto/web/server/embedded/package-info.class
at sun.nio.fs.UnixException.translateToIOException (UnixException.java:92)
at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:106)
at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
at sun.nio.fs.UnixFileSystemProvider.newByteChannel
(UnixFileSystemProvider.java:218) at
java.nio.file.spi.FileSystemProvider.newOutputStream
(FileSystemProvider.java:484) at java.nio.file.Files.newOutputStream
(Files.java:228) at java.nio.file.Files.write (Files.java:3512) at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.createMissingPackageInfoClasses
(AbstractCompilerMojo.java:1364) at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
(AbstractCompilerMojo.java:1229) at
org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:198)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137) at
org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:301) at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:211) at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:165) at
org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:157) at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:121) at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:210) at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:195) at java.util.concurrent.FutureTask.run
(FutureTask.java:264) at
java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:539) at
java.util.concurrent.FutureTask.run (FutureTask.java:264) at
java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1136) at
java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:635) at java.lang.Thread.run (Thread.java:833)
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-compiler-plugin] jmax01 opened a new pull request, #121: MCOMPILER-495 - Fixes missing dirs in createMissingPackageInfoClasses
jmax01 opened a new pull request, #121: URL: https://github.com/apache/maven-compiler-plugin/pull/121 In `createMissingPackageInfoClasses` if the `target` directory does not contain the parent path of a `package-info.class` file create the directories before attempting to write the `package-info.class file` Following this checklist to help us incorporate your contribution quickly and easily: - [ X] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MCOMPILER) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [X ] Each commit in the pull request should have a meaningful subject line and body. - [X] Format the pull request title like `[MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MCOMPILER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [X] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [X] You have run the integration tests successfully (`mvn -Prun-its clean verify`). To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [X] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [X] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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] sbabcoc commented on pull request #528: SUREFIRE-2075: Only set thread count if specified in configuration
sbabcoc commented on PR #528: URL: https://github.com/apache/maven-surefire/pull/528#issuecomment-1113684066 @slawekjaranowski I've added the JIRA to the commit message as requested, and all tests (unit + integration) run successfully. -- 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-sitetools] dependabot[bot] opened a new pull request, #37: Bump plexus-velocity from 1.2 to 1.3
dependabot[bot] opened a new pull request, #37: URL: https://github.com/apache/maven-doxia-sitetools/pull/37 Bumps [plexus-velocity](https://github.com/codehaus-plexus/plexus-velocity) from 1.2 to 1.3. Release notes Sourced from https://github.com/codehaus-plexus/plexus-velocity/releases";>plexus-velocity's releases. plexus-velocity-1.3 Upgrade to Velocity Engine 2.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-velocity/issues/11";>#11) https://github.com/slachiewicz";>@slachiewicz Bump commons-collections from 3.1 to 3.2.2 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-velocity/issues/8";>#8) https://github.com/dependabot";>@dependabot Commits https://github.com/codehaus-plexus/plexus-velocity/commit/a9e943c79fffcc4e16e97131612525494ce9513e";>a9e943c [maven-release-plugin] prepare release plexus-velocity-1.3 https://github.com/codehaus-plexus/plexus-velocity/commit/f69c3f067576f3dd95d5edd54663c9a249717233";>f69c3f0 (doc) run CI also with Java 16/17-ea https://github.com/codehaus-plexus/plexus-velocity/commit/771f324ee090103d0f73869d108f6ae301d20b52";>771f324 Upgrade to Velocity Engine 2.0 https://github.com/codehaus-plexus/plexus-velocity/commit/d39abbfec089d759cbfbe4ff31fefde3f0b9ab22";>d39abbf Bump actions/cache from 2.1.5 to 2.1.6 https://github.com/codehaus-plexus/plexus-velocity/commit/4c44349e302a0e2a17038db926bebd12c27e6696";>4c44349 Bump actions/checkout from 2 to 2.3.4 https://github.com/codehaus-plexus/plexus-velocity/commit/8d1928a589636f8fdcd3fd5c90fc746bc5a4015f";>8d1928a cleanup https://github.com/codehaus-plexus/plexus-velocity/commit/4a3b37e50970c3e54f0eb7e08b4b8c31123caffa";>4a3b37e fix javadoc https://github.com/codehaus-plexus/plexus-velocity/commit/5d0e765515ea37eebe15633048334d432ffb7d57";>5d0e765 add ghaction, dependabot and release drafter https://github.com/codehaus-plexus/plexus-velocity/commit/fa4a96eda39ddf43647c7697ed6949a60f517d05";>fa4a96e Create codeql-analysis.yml https://github.com/codehaus-plexus/plexus-velocity/commit/42b272a7ccc7498ec64a14b9d13fe0405029f3db";>42b272a Bump commons-collections from 3.1 to 3.2.2 Additional commits viewable in https://github.com/codehaus-plexus/plexus-velocity/compare/plexus-velocity-1.2...plexus-velocity-1.3";>compare view [](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) -- 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-sitetools] dependabot[bot] opened a new pull request, #38: Bump maven-project-info-reports-plugin from 3.1.2 to 3.3.0
dependabot[bot] opened a new pull request, #38: URL: https://github.com/apache/maven-doxia-sitetools/pull/38 Bumps [maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin) from 3.1.2 to 3.3.0. Commits https://github.com/apache/maven-project-info-reports-plugin/commit/563a0b261722719f9bf6ead946f3d5e30ef611c8";>563a0b2 [maven-release-plugin] prepare release maven-project-info-reports-plugin-3.3.0 https://github.com/apache/maven-project-info-reports-plugin/commit/9549763fbbdea2ee504412b06c2df1d14c25cb4a";>9549763 [MPIR-416] Upgrade maven-dependency-tree to 3.1.0 https://github.com/apache/maven-project-info-reports-plugin/commit/eab4f24d5cfc44aa91f62bde51e5f8001b36334f";>eab4f24 [MPIR-417] Upgrade Parent to 36 https://github.com/apache/maven-project-info-reports-plugin/commit/3538a85109299b942b3feab5a76b93d6d86d2b5c";>3538a85 Bump project version for next release candidate https://github.com/apache/maven-project-info-reports-plugin/commit/634275979993b45426af278b0c1c886b32fa130a";>6342759 PR template https://github.com/apache/maven-project-info-reports-plugin/commit/8d7b024591e8a4dad675b6a97ebbfb5f86fd2668";>8d7b024 Use shared GitHub actions https://github.com/apache/maven-project-info-reports-plugin/commit/f784eef507716c789c2e05a93750c508ce8b9947";>f784eef [MPIR-399] Upgrade to Maven 3.2.5 https://github.com/apache/maven-project-info-reports-plugin/commit/62f490b101f01215e39a86f2810679a77249e024";>62f490b [MPIR-415] Wrong old goal name in "Incompatibility Notice" table in website https://github.com/apache/maven-project-info-reports-plugin/commit/5bb94e115426c59340db739c9fc3302480528c63";>5bb94e1 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-project-info-reports-plugin/commit/ca84755a9d1f58f6bd39e70457fb0d36ce3755c4";>ca84755 [maven-release-plugin] prepare release maven-project-info-reports-plugin-3.2.2 Additional commits viewable in https://github.com/apache/maven-project-info-reports-plugin/compare/maven-project-info-reports-plugin-3.1.2...maven-project-info-reports-plugin-3.3.0";>compare view [](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) -- 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-sitetools] dependabot[bot] commented on pull request #35: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2
dependabot[bot] commented on PR #35: URL: https://github.com/apache/maven-doxia-sitetools/pull/35#issuecomment-1113863687 Superseded by #38. -- 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-sitetools] dependabot[bot] closed pull request #35: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2
dependabot[bot] closed pull request #35: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2 URL: https://github.com/apache/maven-doxia-sitetools/pull/35 -- 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
