[jira] [Commented] (MBUILDCACHE-86) Bugfix and enhancements with the restoration of outputs on disk
[ https://issues.apache.org/jira/browse/MBUILDCACHE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841337#comment-17841337 ] ASF GitHub Bot commented on MBUILDCACHE-86: --- kbuntrock commented on PR #104: URL: https://github.com/apache/maven-build-cache-extension/pull/104#issuecomment-2079914284 Alright, javadoc generation should be fixed > Bugfix and enhancements with the restoration of outputs on disk > --- > > Key: MBUILDCACHE-86 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-86 > Project: Maven Build Cache Extension > Issue Type: Improvement >Reporter: Kevin Buntrock >Priority: Major > Labels: pull-request-available > > *Fixes :* > * Files containing an underscore in their name can't be restored in the > cache directory correctly (not in the same directory location). > * The cache is able to extract/restore files in locations outside the > project. I guess the extraction part is not a vulnerability since someone > with commit permissions can guess other ways to extract data. But the > possibility of restoring at any place on the disk looks pretty dangerous to > me if a remote cache server is compromised. > *Enhancements :* > * Possibility to restore artefacts on disk, with a dedicated property : > maven.build.cache.restoreOnDiskArtefacts (default to true). Meaning in the > project directory, as opposed to the cache directory. > ** IDE integration and use of the cache locally in developement is way > easier. It is now possible to retrieve a cached jar in the "target" directory. > * Introduce "globs" to filter extra attached outputs by filenames. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MBUILDCACHE-86] bugfix / enhancements restoration of outputs on disk [maven-build-cache-extension]
kbuntrock commented on PR #104: URL: https://github.com/apache/maven-build-cache-extension/pull/104#issuecomment-2079914284 Alright, javadoc generation should 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] [Assigned] (MNG-8109) Resolver 1.9.20
[ https://issues.apache.org/jira/browse/MNG-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8109: Assignee: Tamas Cservenak > Resolver 1.9.20 > --- > > Key: MNG-8109 > URL: https://issues.apache.org/jira/browse/MNG-8109 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Upgrade resolver to 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8081) default profile activation should consider available system and user properties
[
https://issues.apache.org/jira/browse/MNG-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841329#comment-17841329
]
ASF GitHub Bot commented on MNG-8081:
-
gnodet commented on PR #1446:
URL: https://github.com/apache/maven/pull/1446#issuecomment-2079833746
> hi @gnodet ... so with the implementation having been largely duplicated
from model-builder into api-impl, would the similar code remain in both places
indefinitely, or will the model-builder code eventually point directly to
api-impl?
The code in model-builder should be deprecated, it will be kept for
compatibility with 3.x plugins for some time, and then removed. Not sure about
the exact dates though. The point is that model-builder is not really used
anymore in beta-1.
> default profile activation should consider available system and user
> properties
> ---
>
> Key: MNG-8081
> URL: https://issues.apache.org/jira/browse/MNG-8081
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 3.9.6, 4.0.0
>Reporter: Matthew Jason Benson
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 3.9.7, 4.0.0, 4.0.0-beta-1
>
>
> As discussed in my open PR, my use case is to compare between environment
> variables e.g.:
> {code:java}
>
>
> env.FOO
> ${env.BAR}
>
> {code}
> Limiting the interpolation to user/system properties means that there is no
> mindf*ck resulting from profile activation order, etc., and keeps this
> request nonthreatening.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8109) Resolver 1.9.20
[ https://issues.apache.org/jira/browse/MNG-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841328#comment-17841328 ] ASF GitHub Bot commented on MNG-8109: - cstamas opened a new pull request, #1490: URL: https://github.com/apache/maven/pull/1490 Update resolver to latest. --- https://issues.apache.org/jira/browse/MNG-8109 > Resolver 1.9.20 > --- > > Key: MNG-8109 > URL: https://issues.apache.org/jira/browse/MNG-8109 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.7 > > > Upgrade resolver to 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8081] interpolate available properties during default profile selection (Maven 4.x) [maven]
gnodet commented on PR #1446: URL: https://github.com/apache/maven/pull/1446#issuecomment-2079833746 > hi @gnodet ... so with the implementation having been largely duplicated from model-builder into api-impl, would the similar code remain in both places indefinitely, or will the model-builder code eventually point directly to api-impl? The code in model-builder should be deprecated, it will be kept for compatibility with 3.x plugins for some time, and then removed. Not sure about the exact dates though. The point is that model-builder is not really used anymore in beta-1. -- 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-8109) Resolver 1.9.20
Tamas Cservenak created MNG-8109: Summary: Resolver 1.9.20 Key: MNG-8109 URL: https://issues.apache.org/jira/browse/MNG-8109 Project: Maven Issue Type: Dependency upgrade Components: Artifacts and Repositories Reporter: Tamas Cservenak Fix For: 3.9.7 Upgrade resolver to 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
michael-o commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079743348 > @michael-o if you look at failed CI jobs, they are due msite plugin wanting stuff that is actually removed (maven-compat). Am interested could you -- maybe even within this PR -- set up M versions that hopefully does not depends on maven-compat? Ok, I see what you are after. Will look into this. -- 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-8108) Failure to create the consumer POM
Guillaume Nodet created MNG-8108:
Summary: Failure to create the consumer POM
Key: MNG-8108
URL: https://issues.apache.org/jira/browse/MNG-8108
Project: Maven
Issue Type: Bug
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
Fix For: 4.0.0-beta-1
{code}
[INFO] Camel :: Integration Tests
...
SKIPPED
[INFO] Camel :: Docs
SKIPPED
[INFO] Camel :: Assembly
SKIPPED
[INFO]
--
[INFO] BUILD FAILURE
[INFO]
--
[INFO] Total time: 02:53 min
[INFO] Finished at: 2024-04-26T15:34:00+02:00
[INFO]
--
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
on project camel-debezium-common-parent: Execution default-install of goal
org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: 2 problems
were encountered while building the effective model for
/Users/gnodet/work/git/camel/components/camel-debezium/camel-debezium-common/target/camel-debezium-common-parent-4.6.0-SNAPSHOT.pom
[ERROR] - [WARNING] 'parent.relativePath' points at
org.apache.camel:camel-debezium-common-parent instead of
org.apache.camel:camel-debezium-parent, please verify your project structure @
line 22, column 3
[ERROR] - [FATAL] Non-parseable POM
org.apache.camel:camel-debezium-parent:4.6.0-SNAPSHOT: Unable to read model: Is
a directory
[ERROR] -> [Help 1]org.apache.maven.lifecycle.LifecycleExecutionException:
Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
on project camel-debezium-common-parent: Execution default-install of goal
org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: 2 problems
were encountered while building the effective model for
/Users/gnodet/work/git/camel/components/camel-debezium/camel-debezium-common/target/camel-debezium-common-parent-4.6.0-SNAPSHOT.pom
- [WARNING] 'parent.relativePath' points at
org.apache.camel:camel-debezium-common-parent instead of
org.apache.camel:camel-debezium-parent, please verify your project structure @
line 22, column 3
- [FATAL] Non-parseable POM
org.apache.camel:camel-debezium-parent:4.6.0-SNAPSHOT: Unable to read model: Is
a directory
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -r
➜ camel git:(code-cleanup)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEPLOY-314) Include artifactId in messages of DeployMojo#processProject
[
https://issues.apache.org/jira/browse/MDEPLOY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841289#comment-17841289
]
ASF GitHub Bot commented on MDEPLOY-314:
hboutemy commented on code in PR #45:
URL:
https://github.com/apache/maven-deploy-plugin/pull/45#discussion_r1581254551
##
src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java:
##
@@ -299,18 +300,19 @@ private void processProject(final MavenProject project,
DeployRequest request) t
} else if (!project.getAttachedArtifacts().isEmpty()) {
if (allowIncompleteProjects) {
getLog().warn("");
-getLog().warn("The packaging plugin for this project did
not assign");
+getLog().warn("The packaging plugin for project " +
project.getArtifactId() + " did not assign");
Review Comment:
same "packaging plugin" issue
> Include artifactId in messages of DeployMojo#processProject
> ---
>
> Key: MDEPLOY-314
> URL: https://issues.apache.org/jira/browse/MDEPLOY-314
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy
>Affects Versions: 3.1.1
>Reporter: András Péteri
>Assignee: Tamas Cservenak
>Priority: Minor
> Fix For: 3.1.2
>
>
> In "deploy all at once" mode a single project does the heavy lifting for all
> reactor projects once it is determined that others have already been marked
> with an instance of the {{State}} enum earlier.
> As mentioned in a
> [comment|https://github.com/apache/maven-deploy-plugin/pull/39/files/327e65c5dd5e5ed92910858d4cf66ce946e22bbe#r1398970349]
> on PR #39, if a warning is written to the log or an exception is thrown at
> this point, the issue can be falsely attributed to the current project, and
> the real culprit can only be determined by temporarily switching back to
> eager deploy mode.
> It would be nice to display which project is being processed, making this
> investigation easier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MDEPLOY-314] Include artifactId in DeployMojo#processProject messages [maven-deploy-plugin]
hboutemy commented on code in PR #45:
URL:
https://github.com/apache/maven-deploy-plugin/pull/45#discussion_r1581254551
##
src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java:
##
@@ -299,18 +300,19 @@ private void processProject(final MavenProject project,
DeployRequest request) t
} else if (!project.getAttachedArtifacts().isEmpty()) {
if (allowIncompleteProjects) {
getLog().warn("");
-getLog().warn("The packaging plugin for this project did
not assign");
+getLog().warn("The packaging plugin for project " +
project.getArtifactId() + " did not assign");
Review Comment:
same "packaging plugin" issue
--
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] (MDEPLOY-314) Include artifactId in messages of DeployMojo#processProject
[
https://issues.apache.org/jira/browse/MDEPLOY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841287#comment-17841287
]
ASF GitHub Bot commented on MDEPLOY-314:
hboutemy commented on code in PR #45:
URL:
https://github.com/apache/maven-deploy-plugin/pull/45#discussion_r1581253605
##
src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java:
##
@@ -299,18 +300,19 @@ private void processProject(final MavenProject project,
DeployRequest request) t
} else if (!project.getAttachedArtifacts().isEmpty()) {
if (allowIncompleteProjects) {
getLog().warn("");
-getLog().warn("The packaging plugin for this project did
not assign");
+getLog().warn("The packaging plugin for project " +
project.getArtifactId() + " did not assign");
getLog().warn("a main file to the project but it has
attachments. Change packaging to 'pom'.");
getLog().warn("");
getLog().warn("Incomplete projects like this will fail in
future Maven versions!");
getLog().warn("");
} else {
-throw new MojoExecutionException("The packaging plugin for
this project did not assign "
-+ "a main file to the project but it has
attachments. Change packaging to 'pom'.");
+throw new MojoExecutionException("The packaging plugin for
project " + project.getArtifactId()
++ " did not assign a main file to the project but
it has attachments. Change packaging"
++ " to 'pom'.");
}
} else {
-throw new MojoExecutionException(
-"The packaging for this project did not assign a file
to the build artifact");
+throw new MojoExecutionException("The packaging plugin for
project " + project.getArtifactId()
Review Comment:
"packaging plugin"?
there is no packaging plugin, just packaging
> Include artifactId in messages of DeployMojo#processProject
> ---
>
> Key: MDEPLOY-314
> URL: https://issues.apache.org/jira/browse/MDEPLOY-314
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy
>Affects Versions: 3.1.1
>Reporter: András Péteri
>Assignee: Tamas Cservenak
>Priority: Minor
> Fix For: 3.1.2
>
>
> In "deploy all at once" mode a single project does the heavy lifting for all
> reactor projects once it is determined that others have already been marked
> with an instance of the {{State}} enum earlier.
> As mentioned in a
> [comment|https://github.com/apache/maven-deploy-plugin/pull/39/files/327e65c5dd5e5ed92910858d4cf66ce946e22bbe#r1398970349]
> on PR #39, if a warning is written to the log or an exception is thrown at
> this point, the issue can be falsely attributed to the current project, and
> the real culprit can only be determined by temporarily switching back to
> eager deploy mode.
> It would be nice to display which project is being processed, making this
> investigation easier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MDEPLOY-314] Include artifactId in DeployMojo#processProject messages [maven-deploy-plugin]
hboutemy commented on code in PR #45:
URL:
https://github.com/apache/maven-deploy-plugin/pull/45#discussion_r1581253605
##
src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java:
##
@@ -299,18 +300,19 @@ private void processProject(final MavenProject project,
DeployRequest request) t
} else if (!project.getAttachedArtifacts().isEmpty()) {
if (allowIncompleteProjects) {
getLog().warn("");
-getLog().warn("The packaging plugin for this project did
not assign");
+getLog().warn("The packaging plugin for project " +
project.getArtifactId() + " did not assign");
getLog().warn("a main file to the project but it has
attachments. Change packaging to 'pom'.");
getLog().warn("");
getLog().warn("Incomplete projects like this will fail in
future Maven versions!");
getLog().warn("");
} else {
-throw new MojoExecutionException("The packaging plugin for
this project did not assign "
-+ "a main file to the project but it has
attachments. Change packaging to 'pom'.");
+throw new MojoExecutionException("The packaging plugin for
project " + project.getArtifactId()
++ " did not assign a main file to the project but
it has attachments. Change packaging"
++ " to 'pom'.");
}
} else {
-throw new MojoExecutionException(
-"The packaging for this project did not assign a file
to the build artifact");
+throw new MojoExecutionException("The packaging plugin for
project " + project.getArtifactId()
Review Comment:
"packaging plugin"?
there is no packaging plugin, just packaging
--
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-8081) default profile activation should consider available system and user properties
[
https://issues.apache.org/jira/browse/MNG-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841284#comment-17841284
]
ASF GitHub Bot commented on MNG-8081:
-
mbenson commented on PR #1447:
URL: https://github.com/apache/maven/pull/1447#issuecomment-2079676825
Sounds like this approach would keep the v3/v4 impls more similar. I'll work
on this.
> default profile activation should consider available system and user
> properties
> ---
>
> Key: MNG-8081
> URL: https://issues.apache.org/jira/browse/MNG-8081
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 3.9.6, 4.0.0
>Reporter: Matthew Jason Benson
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 3.9.7, 4.0.0, 4.0.0-beta-1
>
>
> As discussed in my open PR, my use case is to compare between environment
> variables e.g.:
> {code:java}
>
>
> env.FOO
> ${env.BAR}
>
> {code}
> Limiting the interpolation to user/system properties means that there is no
> mindf*ck resulting from profile activation order, etc., and keeps this
> request nonthreatening.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8081] interpolate available properties during default profile selection (Maven 3.9.x) [maven]
mbenson commented on PR #1447: URL: https://github.com/apache/maven/pull/1447#issuecomment-2079676825 Sounds like this approach would keep the v3/v4 impls more similar. I'll work on this. -- 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-8081) default profile activation should consider available system and user properties
[
https://issues.apache.org/jira/browse/MNG-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841282#comment-17841282
]
ASF GitHub Bot commented on MNG-8081:
-
mbenson commented on PR #1446:
URL: https://github.com/apache/maven/pull/1446#issuecomment-2079675232
hi @gnodet ... so with the implementation having been largely duplicated
from model-builder into api-impl, would the similar code remain in both places
indefinitely, or will the model-builder code eventually point directly to
api-impl?
> default profile activation should consider available system and user
> properties
> ---
>
> Key: MNG-8081
> URL: https://issues.apache.org/jira/browse/MNG-8081
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 3.9.6, 4.0.0
>Reporter: Matthew Jason Benson
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 3.9.7, 4.0.0, 4.0.0-beta-1
>
>
> As discussed in my open PR, my use case is to compare between environment
> variables e.g.:
> {code:java}
>
>
> env.FOO
> ${env.BAR}
>
> {code}
> Limiting the interpolation to user/system properties means that there is no
> mindf*ck resulting from profile activation order, etc., and keeps this
> request nonthreatening.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8081] interpolate available properties during default profile selection (Maven 4.x) [maven]
mbenson commented on PR #1446: URL: https://github.com/apache/maven/pull/1446#issuecomment-2079675232 hi @gnodet ... so with the implementation having been largely duplicated from model-builder into api-impl, would the similar code remain in both places indefinitely, or will the model-builder code eventually point directly to api-impl? -- 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
Re: [PR] [MNG-7266] Remove maven-compat [maven]
cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079652561 @michael-o if you look at failed CI jobs, they are due msite plugin wanting stuff that is actually removed (maven-compat). Am interested could you -- maybe even within this PR -- set up M versions that hopefully does not depends on maven-compat? -- 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
Re: [PR] Bump org.eclipse.aether:aether-api from 1.0.0.v20140518 to 1.1.0 [maven-reporting-impl]
slachiewicz closed pull request #36: Bump org.eclipse.aether:aether-api from 1.0.0.v20140518 to 1.1.0 URL: https://github.com/apache/maven-reporting-impl/pull/36 -- 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
Re: [PR] Bump org.eclipse.aether:aether-api from 1.0.0.v20140518 to 1.1.0 [maven-reporting-impl]
dependabot[bot] commented on PR #36: URL: https://github.com/apache/maven-reporting-impl/pull/36#issuecomment-2079620986 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. 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
[PR] Simplified redundant judgment [maven]
CrazyHZM opened a new pull request, #1489: URL: https://github.com/apache/maven/pull/1489 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG) 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. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. - [ ] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`. Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. 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. - [ ] 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) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- 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-8073) Generated XSD files needs to have AL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841263#comment-17841263 ] Tamas Cservenak commented on MNG-8073: -- Created [https://github.com/codehaus-plexus/modello/pull/437] Basically to have it done in simplest way. > Generated XSD files needs to have AL2.0 license headers > --- > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8073) Generated XSD files needs to have ASL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8073: - Summary: Generated XSD files needs to have ASL2.0 license headers (was: Generated XSD files needs to have AL2.0 license headers) > Generated XSD files needs to have ASL2.0 license headers > > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.maven.reporting:maven-reporting-api from 4.0.0-M9 to 4.0.0-M11 [maven-reporting-impl]
dependabot[bot] closed pull request #39: Bump org.apache.maven.reporting:maven-reporting-api from 4.0.0-M9 to 4.0.0-M11 URL: https://github.com/apache/maven-reporting-impl/pull/39 -- 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
Re: [PR] Bump org.apache.maven.reporting:maven-reporting-api from 4.0.0-M9 to 4.0.0-M11 [maven-reporting-impl]
dependabot[bot] commented on PR #39: URL: https://github.com/apache/maven-reporting-impl/pull/39#issuecomment-2079541187 Looks like org.apache.maven.reporting:maven-reporting-api 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
Re: [PR] Bump doxiaVersion from 2.0.0-M8 to 2.0.0-M10 [maven-reporting-impl]
dependabot[bot] closed pull request #37: Bump doxiaVersion from 2.0.0-M8 to 2.0.0-M10 URL: https://github.com/apache/maven-reporting-impl/pull/37 -- 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
Re: [PR] Bump doxiaVersion from 2.0.0-M8 to 2.0.0-M10 [maven-reporting-impl]
dependabot[bot] commented on PR #37: URL: https://github.com/apache/maven-reporting-impl/pull/37#issuecomment-2079541058 Looks like these dependencies are 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
[jira] [Closed] (MSHARED-1361) Upgrade plugins and components (in ITs) (2)
[ https://issues.apache.org/jira/browse/MSHARED-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1361. --- Resolution: Fixed Fixed with [153df38982c10061eb8d004066bb2d521f8cc608|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=153df38982c10061eb8d004066bb2d521f8cc608]. > Upgrade plugins and components (in ITs) (2) > --- > > Key: MSHARED-1361 > URL: https://issues.apache.org/jira/browse/MSHARED-1361 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-impl >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0, > maven-reporting-impl-4.0.0-M14 > > > * Upgrade to Doxia 2.0.0-M10 > * Upgrade to Doxia Sitetools 2.0.0-M18 > * Upgrade to Maven Reporting API 4.0.0-M11 > * Upgrade to Maven Plugin Tools 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [I] Hang with SpotBugs plugin and fork=false [maven-mvnd]
rovarga commented on issue #979: URL: https://github.com/apache/maven-mvnd/issues/979#issuecomment-2079480796 full jstack output: [spotbugs_deadlock.txt](https://github.com/apache/maven-mvnd/files/15131670/spotbugs_deadlock.txt) -- 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
Re: [PR] Bump pmdVersion from 7.0.0 to 7.1.0 [maven-pmd-plugin]
dependabot[bot] commented on PR #149: URL: https://github.com/apache/maven-pmd-plugin/pull/149#issuecomment-2079464688 OK, I won't notify you about version 7.x.x again, unless you re-open this PR. -- 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
Re: [PR] Bump pmdVersion from 7.0.0 to 7.1.0 [maven-pmd-plugin]
dependabot[bot] closed pull request #149: Bump pmdVersion from 7.0.0 to 7.1.0 URL: https://github.com/apache/maven-pmd-plugin/pull/149 -- 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
Re: [PR] Bump pmdVersion from 7.0.0 to 7.1.0 [maven-pmd-plugin]
adangel commented on PR #149: URL: https://github.com/apache/maven-pmd-plugin/pull/149#issuecomment-2079464593 @dependabot ignore this major version -- 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
[I] Hang with SpotBugs plugin and fork=false [maven-mvnd]
rovarga opened a new issue, #979: URL: https://github.com/apache/maven-mvnd/issues/979 A parallel build invoking spotbugs-maven-plugin without forking ends up hanging build sometimes. A thread dump shows two build tasks attempting to lock a monitor: ``` "BuilderThread 3" #52 [174264] prio=5 os_prio=0 cpu=4139,05ms elapsed=2286,53s tid=0x7fd300a2ab80 nid=174264 waiting for monitor entry [0x7fd4361fb000] java.lang.Thread.State: BLOCKED (on object monitor) at org.apache.tools.ant.taskdefs.Redirector.complete(Redirector.java:971) - waiting to lock <0x00043380> (a java.lang.Object) at org.apache.tools.ant.taskdefs.Java.run(Java.java:893) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:232) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:136) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:109) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299) at java.lang.invoke.LambdaForm$DMH/0x7fd3e01fc000.invokeVirtual(java.base@21.0.2/LambdaForm$DMH) at java.lang.invoke.LambdaForm$MH/0x7fd3e1498c00.invoke(java.base@21.0.2/LambdaForm$MH) at java.lang.invoke.Invokers$Holder.invokeExact_MT(java.base@21.0.2/Invokers$Holder) at jdk.internal.reflect.DirectMethodHandleAccessor.invokeImpl(java.base@21.0.2/DirectMethodHandleAccessor.java:153) at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(java.base@21.0.2/DirectMethodHandleAccessor.java:103) at java.lang.reflect.Method.invoke(java.base@21.0.2/Method.java:580) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at groovy.ant.AntBuilder.performTask(AntBuilder.java:347) at groovy.ant.AntBuilder.nodeCompleted(AntBuilder.java:286) at groovy.util.BuilderSupport.doInvokeMethod(BuilderSupport.java:161) at groovy.ant.AntBuilder.doInvokeMethod(AntBuilder.java:219) at groovy.util.BuilderSupport.invokeMethod(BuilderSupport.java:75) at org.codehaus.groovy.vmplugin.v8.IndyGuardsFiltersAndSignatures.invokeGroovyObjectInvoker(IndyGuardsFiltersAndSignatures.java:151) ``` and ``` "BuilderThread 11" #60 [174272] prio=5 os_prio=0 cpu=3370,14ms elapsed=2286,53s tid=0x7fd300a3a340 nid=174272 waiting for monitor entry [0x7fd4359fb000] java.lang.Thread.State: BLOCKED (on object monitor) at org.apache.tools.ant.taskdefs.Redirector.complete(Redirector.java:971) - waiting to lock <0x000433828660> (a java.lang.Object) at org.apache.tools.ant.taskdefs.Java.run(Java.java:893) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:232) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:136) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:109) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299) at java.lang.invoke.LambdaForm$DMH/0x7fd3e01fc000.invokeVirtual(java.base@21.0.2/LambdaForm$DMH) at java.lang.invoke.LambdaForm$MH/0x7fd3e1498c00.invoke(java.base@21.0.2/LambdaForm$MH) at java.lang.invoke.Invokers$Holder.invokeExact_MT(java.base@21.0.2/Invokers$Holder) at jdk.internal.reflect.DirectMethodHandleAccessor.invokeImpl(java.base@21.0.2/DirectMethodHandleAccessor.java:153) at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(java.base@21.0.2/DirectMethodHandleAccessor.java:103) at java.lang.reflect.Method.invoke(java.base@21.0.2/Method.java:580) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at groovy.ant.AntBuilder.performTask(AntBuilder.java:347) at groovy.ant.AntBuilder.nodeCompleted(AntBuilder.java:286) at groovy.util.BuilderSupport.doInvokeMethod(BuilderSupport.java:161) at groovy.ant.AntBuilder.doInvokeMethod(AntBuilder.java:219) at groovy.util.BuilderSupport.invokeMethod(BuilderSupport.java:75) at org.codehaus.groovy.vmplugin.v8.IndyGuardsFiltersAndSignatures.invokeGroovyObjectInvoker(IndyGuardsFiltersAndSignatures.java:151) ``` both objects mentioned are held in this context: ``` "In pipe (disconnected)" #109 [174409] daemon prio=5 os_prio=0 cpu=0,25ms elapsed=2277,97s tid=0x7fd1f00059f0 nid=174409 in Object.wait() [0x7fd42bbfe000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait0(java.base@21.0.2/Native Method) - waiting on <0x0007ff2284e0> (a java.util.LinkedList) at java.lang.Object.wait(java.base@21.0.2/Object.java:366) at java.lang.Object.wait(java.base@21.0.2/Object.java:339) at org.mvndaemon.mvnd.daemon.Server$DaemonInputStream.read(Server.java:714) - locked <0x0007ff2284e0> (a java.util.LinkedList) at java.io.InputStream.read(java.base@21.0.2/InputStream.java:287) at
[jira] [Assigned] (MNG-8070) Document Maven Runtime Requirement for Java 17
[ https://issues.apache.org/jira/browse/MNG-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8070: Assignee: Tamas Cservenak > Document Maven Runtime Requirement for Java 17 > -- > > Key: MNG-8070 > URL: https://issues.apache.org/jira/browse/MNG-8070 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Followup for MNG-8061 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8070) Document Maven Runtime Requirement for Java 17
[ https://issues.apache.org/jira/browse/MNG-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841251#comment-17841251 ] ASF GitHub Bot commented on MNG-8070: - cstamas opened a new pull request, #516: URL: https://github.com/apache/maven-site/pull/516 Unsure where else? --- https://issues.apache.org/jira/browse/MNG-8070 > Document Maven Runtime Requirement for Java 17 > -- > > Key: MNG-8070 > URL: https://issues.apache.org/jira/browse/MNG-8070 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Followup for MNG-8061 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8070) Document Maven Runtime Requirement for Java 17
[ https://issues.apache.org/jira/browse/MNG-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8070: - Fix Version/s: 4.0.0 > Document Maven Runtime Requirement for Java 17 > -- > > Key: MNG-8070 > URL: https://issues.apache.org/jira/browse/MNG-8070 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Followup for MNG-8061 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8038) Model builder API
[
https://issues.apache.org/jira/browse/MNG-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8038:
-
Fix Version/s: 4.0.0
> Model builder API
> -
>
> Key: MNG-8038
> URL: https://issues.apache.org/jira/browse/MNG-8038
> Project: Maven
> Issue Type: Improvement
> Components: API
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-1
>
>
> In some cases, it may be needed to access the _raw_ or the _effective_ model
> of artifacts downloaded from repositories (usually dependencies of the
> current project). The file model can already be read using the
> {{ModelXmlFactory}} but that's quite limited in scope.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8084) Make the v4 api usable outside the Maven runtime
[ https://issues.apache.org/jira/browse/MNG-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8084: - Fix Version/s: 4.0.0 > Make the v4 api usable outside the Maven runtime > > > Key: MNG-8084 > URL: https://issues.apache.org/jira/browse/MNG-8084 > Project: Maven > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841246#comment-17841246 ] ASF GitHub Bot commented on MNG-7266: - michael-o commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079429030 > @michael-o can we have a taste on new Ms from site suite? You want to me run the entire test setup of Doxia/MSITE w/o depending on maven-compat or with with PR of Maven 4? > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8082) Exceptions of proxied SessionScoped components are not working correctly
[
https://issues.apache.org/jira/browse/MNG-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8082:
-
Fix Version/s: 4.0.0
> Exceptions of proxied SessionScoped components are not working correctly
>
>
> Key: MNG-8082
> URL: https://issues.apache.org/jira/browse/MNG-8082
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-13
>Reporter: Jonas Rutishauser
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-1
>
>
> As the {{InvocationTargetException}} is not handled in the proxy a runtime
> exception will be wrapped by an {{InvocationTargetException}} and an
> application exception is additional wrapped by an
> {{UndeclaredThrowableException}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8106) Maven Metadata corruption if repository directory role overlaps
[
https://issues.apache.org/jira/browse/MNG-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8106:
-
Fix Version/s: 4.0.0
> Maven Metadata corruption if repository directory role overlaps
> ---
>
> Key: MNG-8106
> URL: https://issues.apache.org/jira/browse/MNG-8106
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6,
> 4.0.0-alpha-2, 4.0.0-alpha-3, 4.0.0-alpha-4, 4.0.0-alpha-5, 4.0.0-alpha-7,
> 4.0.0-alpha-8, 4.0.0-alpha-9, 4.0.0-alpha-10, 4.0.0-alpha-12, 4.0.0-alpha-13
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 3.9.7, 4.0.0, 4.0.0-beta-1
>
>
> In case certain directory role in repository is manifold (which IS against
> best practices), data loss occurs. Metadata will contain this or that, but
> not both data.
> Example: consider project producing these artifacts
> * org.foo:bar:1.0
> * org.foo.bar:baz:1.0
> In this case, the local (and remote) repository path {{org/foo/bar}} that is
> a directory, will overlap in a way, it is G level for one artifact, and A
> level for another. Now, if org.foo.bar:baz is a Maven Plugin, the G level
> should contain plugin related (G level) metadata. At the same time, due
> org.foo:bar this directory should contain A level metadata (list of
> versions). Affected maven versions will simply drop "the other" metadata (so
> if last deployed using this directory as G, the A data will be missing, and
> other way around).
> Have to note that doing this kind of naming is against "best practices", but
> still, can occur, for example in case of some refactoring/renaming of long
> running project modules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
michael-o commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079429030 > @michael-o can we have a taste on new Ms from site suite? You want to me run the entire test setup of Doxia/MSITE w/o depending on maven-compat or with with PR of Maven 4? -- 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] (MNG-8073) Generated XSD files needs to have AL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8073: - Fix Version/s: 4.0.0 > Generated XSD files needs to have AL2.0 license headers > --- > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841236#comment-17841236 ] ASF GitHub Bot commented on MNG-7266: - cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079391628 I think wagon-provider-api is a must as it is used in Maven3 plugins as well... so only compat is the one that is getting booted > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-5693) Change logging of MojoExceptions to console
[
https://issues.apache.org/jira/browse/MNG-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841240#comment-17841240
]
Juul Hobert commented on MNG-5693:
--
[~rfscholte] I think it's a really good idea to give plugins the ability to
provide additional information to be logged to console. I see that there has
been an attempt in the past. Would it still make sense to work on this ticket?
> Change logging of MojoExceptions to console
> ---
>
> Key: MNG-5693
> URL: https://issues.apache.org/jira/browse/MNG-5693
> Project: Maven
> Issue Type: Improvement
> Components: FDPFC, Plugin API
>Reporter: Robert Scholte
>Priority: Major
> Fix For: 4.0.x-candidate
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If a plugin fails for any reason, a general message is logged with a
> reference to a wiki page, which never contains the real reason why the plugin
> failed.
> For new users this is very confusing. Even when we teach them to read, and
> they finally see a link, it's quite frustrating for them that they still
> don't know what happened.
> {{MojoExecutionException}} and {{MojoFailureException}} should never refer to
> a wikipage anymore.
> Plugin writers should get more control over the message written to the
> console.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841223#comment-17841223 ] ASF GitHub Bot commented on MNG-7266: - Giovds commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079380222 I've noticed in the .svg that the `compat` module sits between `core` and `wagon-provider-api`. What is the next step for the `wagon-provider-api`? Does this mean we remove the `wagon-provider-api` as well, or do we link `core` with `wagon-provider-api`, or is there another path we should take? > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
Giovds commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079380222 I've noticed in the .svg that the `compat` module sits between `core` and `wagon-provider-api`. What is the next step for the `wagon-provider-api`? Does this mean we remove the `wagon-provider-api` as well, or do we link `core` with `wagon-provider-api`, or is there another path we should take? -- 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] (MNG-8107) Upgrade to Resolver 2.0.0-alpha-11
[ https://issues.apache.org/jira/browse/MNG-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8107. Resolution: Fixed > Upgrade to Resolver 2.0.0-alpha-11 > -- > > Key: MNG-8107 > URL: https://issues.apache.org/jira/browse/MNG-8107 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079366763 @michael-o can we have a taste on new Ms from site suite? -- 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-8107) Upgrade to Resolver 2.0.0-alpha-11
[ https://issues.apache.org/jira/browse/MNG-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841219#comment-17841219 ] ASF GitHub Bot commented on MNG-8107: - cstamas merged PR #1488: URL: https://github.com/apache/maven/pull/1488 > Upgrade to Resolver 2.0.0-alpha-11 > -- > > Key: MNG-8107 > URL: https://issues.apache.org/jira/browse/MNG-8107 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8107] Update Resolver 2.0.0-alpha-11 [maven]
cstamas merged PR #1488: URL: https://github.com/apache/maven/pull/1488 -- 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-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841218#comment-17841218 ] ASF GitHub Bot commented on MNG-7266: - cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079366763 @michael-o can we have a taste on new Ms from site suite? > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841217#comment-17841217 ] ASF GitHub Bot commented on MNG-7266: - cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079366084 maven-site plugin is still maven2 dependant... > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7266] Remove maven-compat [maven]
cstamas commented on PR #1487: URL: https://github.com/apache/maven/pull/1487#issuecomment-2079366084 maven-site plugin is still maven2 dependant... -- 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-8107) Upgrade to Resolver 2.0.0-alpha-11
[ https://issues.apache.org/jira/browse/MNG-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841199#comment-17841199 ] ASF GitHub Bot commented on MNG-8107: - cstamas opened a new pull request, #1488: URL: https://github.com/apache/maven/pull/1488 And restore renamed class. --- https://issues.apache.org/jira/browse/MNG-8107 > Upgrade to Resolver 2.0.0-alpha-11 > -- > > Key: MNG-8107 > URL: https://issues.apache.org/jira/browse/MNG-8107 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8107) Upgrade to Resolver 2.0.0-alpha-11
[ https://issues.apache.org/jira/browse/MNG-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8107: Assignee: Tamas Cservenak > Upgrade to Resolver 2.0.0-alpha-11 > -- > > Key: MNG-8107 > URL: https://issues.apache.org/jira/browse/MNG-8107 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8107) Upgrade to Resolver 2.0.0-alpha-11
Tamas Cservenak created MNG-8107: Summary: Upgrade to Resolver 2.0.0-alpha-11 Key: MNG-8107 URL: https://issues.apache.org/jira/browse/MNG-8107 Project: Maven Issue Type: Dependency upgrade Components: Artifacts and Repositories Reporter: Tamas Cservenak Fix For: 4.0.0, 4.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNG-7122) Require specific Maven compatibility version for plugins
[ https://issues.apache.org/jira/browse/MNG-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841190#comment-17841190 ] Tamas Cservenak edited comment on MNG-7122 at 4/26/24 12:10 PM: maven-compat is about to be removed from Maven4, so Maven2 plugins will just break. was (Author: cstamas): maven-compat is about to be removed from Maven4, so they will just break. > Require specific Maven compatibility version for plugins > > > Key: MNG-7122 > URL: https://issues.apache.org/jira/browse/MNG-7122 > Project: Maven > Issue Type: New Feature > Components: Plugins and Lifecycle >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.x-candidate > > > By removing the WagonExcluder (MNG-7020) it could mean that plugins that rely > on Maven2 dependencies might leak an old wagon-version onto the classpath. > Plugins can already define a prerequisite for the Maven version, but we also > need a mechanism to do it the other way around: plugins should at least > require maven dependencies of version x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7122) Require specific Maven compatibility version for plugins
[ https://issues.apache.org/jira/browse/MNG-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841190#comment-17841190 ] Tamas Cservenak commented on MNG-7122: -- maven-compat is about to be removed from Maven4, so they will just break. > Require specific Maven compatibility version for plugins > > > Key: MNG-7122 > URL: https://issues.apache.org/jira/browse/MNG-7122 > Project: Maven > Issue Type: New Feature > Components: Plugins and Lifecycle >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.x-candidate > > > By removing the WagonExcluder (MNG-7020) it could mean that plugins that rely > on Maven2 dependencies might leak an old wagon-version onto the classpath. > Plugins can already define a prerequisite for the Maven version, but we also > need a mechanism to do it the other way around: plugins should at least > require maven dependencies of version x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.8 [maven-resolver]
slachiewicz commented on PR #457: URL: https://github.com/apache/maven-resolver/pull/457#issuecomment-2079257214 @dependabot ignore this major version -- 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
Re: [PR] Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.8 [maven-resolver]
dependabot[bot] closed pull request #457: Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.8 URL: https://github.com/apache/maven-resolver/pull/457 -- 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
Re: [PR] Bump org.eclipse.jetty:jetty-bom from 10.0.20 to 12.0.8 [maven-resolver]
dependabot[bot] commented on PR #457: URL: https://github.com/apache/maven-resolver/pull/457#issuecomment-2079257296 OK, I won't notify you about version 12.x.x again, unless you re-open this PR. -- 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-7122) Require specific Maven compatibility version for plugins
[ https://issues.apache.org/jira/browse/MNG-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841181#comment-17841181 ] Juul Hobert commented on MNG-7122: -- #MNG-7754 already reports when a Maven 2.x dependency is used in a plugin. Does this ticket still describe useful functionality? It looks to me that MNG-7754 already covers enough so that the described functionality in this ticket is not useful anymore. [~rfscholte] and [~cstamas] can you give your vision on this? > Require specific Maven compatibility version for plugins > > > Key: MNG-7122 > URL: https://issues.apache.org/jira/browse/MNG-7122 > Project: Maven > Issue Type: New Feature > Components: Plugins and Lifecycle >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 4.0.x-candidate > > > By removing the WagonExcluder (MNG-7020) it could mean that plugins that rely > on Maven2 dependencies might leak an old wagon-version onto the classpath. > Plugins can already define a prerequisite for the Maven version, but we also > need a mechanism to do it the other way around: plugins should at least > require maven dependencies of version x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-59) Accommodate Maven CI-friendly versions
[
https://issues.apache.org/jira/browse/MBUILDCACHE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841177#comment-17841177
]
Marquis Wang commented on MBUILDCACHE-59:
-
Actually [~ralaoui] [~bverp] I've discovered that maven-compiler-plugin 3.12.0
and higher make the version field optional in {{annotationProcessorPaths}}:
https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#annotationProcessorPaths
{code}
1.2.3
{code}
> Accommodate Maven CI-friendly versions
> --
>
> Key: MBUILDCACHE-59
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-59
> Project: Maven Build Cache Extension
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bas van Erp
>Priority: Major
>
> I would argue that the Maven Build Cache Extension (MBCE) can provide the
> greatest value for users that utilize large multi-module (mono-)repositories,
> since those projects tend to have large amounts of "stable" code which isn't
> modified frequently.
> Speeding up the build of these multi-module projects using the MBCE would be
> totally awesome!
> But for my particular project (200K LOC, 400 modules, mono-repo) our initial
> trials with the MBCE have proven somewhat troublesome.
> It has to do with our use of [https://maven.apache.org/maven-ci-friendly.html]
> h2. Example setup
> {{repo/.mvn/maven.config}}
> {code:java}
> -Drevision=0.0.0-local-SNAPSHOT {code}
> {{repo/pom.xml}}
> {code:java}
> com.corp
> parent
> ${revision}
> pom {code}
> {{repo/moduleX/pom.xml}}
> {code:java}
>
> com.corp
> parent
> ${revision}
> ../pom.xml
>
> moduleX
> jar{code}
> {{repo/moduleY/pom.xml}}
> {code:java}
>
> com.corp
> parent
> ${revision}
> ../pom.xml
>
> moduleY
> jar
>
>
> com.corp
> moduleX
> ${revision}
>
> {code}
> {{repo/Jenkinsfile}}
> {code:java}
> mvn clean deploy -Drevision=$(git describe){code}
> h2. Effect
> This setup effectively means that while all our 150 developers might
> theoretically get decent cache hit % since they are all always using version
> {{0.0.0-local-SNAPSHOT}} for every single POM for every single build, our CI
> pipelines are out of luck.
> Since the effective-POMs will change radically with each new Git commit, the
> hashes will virtually never collide.
> h2. Solution?
> I'm very new to the MBCE so I might be way off the mark, but I think
> accommodating this setup will not be trivial to implement. It would probably
> require parsing the effective-POM for every module picked-up by the reactor
> and then removing all clauses of the module, the parent, and each
> dependency and plugin which are part of the reactor build.
> Doesn't sound easy to me. But perhaps I'm missing something.
>
> p.s. Congrats on the v1.0.0 release :). I'm enjoying experimenting with it.
> But the documentation could use some love. It's pretty hard to read. Some
> paragraphs are confusing, terse or lacking in detail, are clearly written by
> non-English-native writers (like myself), or even stop mid-sentence.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOLVER-526) Import Eclipse Aether wiki content to Maven Site
[
https://issues.apache.org/jira/browse/MRESOLVER-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-526:
--
Fix Version/s: 2.0.0
2.0.0-beta-1
> Import Eclipse Aether wiki content to Maven Site
>
>
> Key: MRESOLVER-526
> URL: https://issues.apache.org/jira/browse/MRESOLVER-526
> Project: Maven Resolver
> Issue Type: Task
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
> Attachments: EclipseAetherWikiExportAsMD.zip,
> Eclipsepedia-20240410130147.xml
>
>
> As the Eclipse wiki is gonna be shutdown soon the content currently only
> available on https://wiki.eclipse.org/Aether (and other pages with category
> {{Aether}}) should be migrated to the resolver site.
> The steps for exporting and converting to Markdown are outlined at
> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-Move-FAQ.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump pmdVersion from 7.0.0 to 7.1.0 [maven-pmd-plugin]
dependabot[bot] opened a new pull request, #149: URL: https://github.com/apache/maven-pmd-plugin/pull/149 Bumps `pmdVersion` from 7.0.0 to 7.1.0. Updates `net.sourceforge.pmd:pmd-core` from 7.0.0 to 7.1.0 Release notes Sourced from https://github.com/pmd/pmd/releases;>net.sourceforge.pmd:pmd-core's releases. PMD 7.1.0 (26-April-2024) 26-April-2024 - 7.1.0 The PMD team is pleased to announce PMD 7.1.0. This is a minor release. Table Of Contents https://github.com/pmd/pmd/blob/HEAD/#new-and-noteworthy;> New and noteworthy https://github.com/pmd/pmd/blob/HEAD/#more-robust-cpd-reports;>More robust CPD reports https://github.com/pmd/pmd/blob/HEAD/#new-rules;>✨ New Rules https://github.com/pmd/pmd/blob/HEAD/#rule-changes;> Rule Changes https://github.com/pmd/pmd/blob/HEAD/#fixed-issues;> Fixed Issues https://github.com/pmd/pmd/blob/HEAD/#api-changes;> API Changes https://github.com/pmd/pmd/blob/HEAD/#deprecated-methods;>Deprecated methods https://github.com/pmd/pmd/blob/HEAD/#external-contributions;>✨ External Contributions https://github.com/pmd/pmd/blob/HEAD/#stats;> Stats New and noteworthy More robust CPD reports There were a number of circumstances, specially around (but not limited to) literal sequences, were CPD would report duplicate overlapping or partially overlapping matches. These have now been fixed, and CPD will report only the longest non-overlapping duplicate. These improvements apply to all supported languages, irrespective of supported flags. ✨ New Rules The new Java rule https://docs.pmd-code.org/pmd-doc-7.1.0/pmd_rules_java_bestpractices.html#unnecessaryvarargsarraycreation;>UnnecessaryVarargsArrayCreation reports explicit array creation when a varargs is expected. This is more heavy to read and could be simplified. The new Java rule https://docs.pmd-code.org/pmd-doc-7.1.0/pmd_rules_java_errorprone.html#confusingargumenttovarargsmethod;>ConfusingArgumentToVarargsMethod reports some confusing situations where a varargs method is called with an inexact argument type. These may end up in a mismatch between the expected parameter type and the actual value. The new Java rule https://docs.pmd-code.org/pmd-doc-7.1.0/pmd_rules_java_codestyle.html#lambdacanbemethodreference;>LambdaCanBeMethodReference reports lambda expressions that can be replaced with a method reference. Please read the documentation of the rule for more info. This rule is now part of the Quickstart ruleset. Rule Changes https://docs.pmd-code.org/pmd-doc-7.1.0/pmd_rules_java_bestpractices.html#junittestsshouldincludeassert;>JUnitTestsShouldIncludeAssert and https://docs.pmd-code.org/pmd-doc-7.1.0/pmd_rules_java_bestpractices.html#junittestcontainstoomanyasserts;>JUnitTestContainsTooManyAsserts have a new property named extraAssertMethodNames. With this property, you can configure which additional static methods should be considered as valid verification methods. This allows to use custom mocking or assertion libraries. Fixed Issues core https://redirect.github.com/pmd/pmd/issues/494;>#494: [core] Adopt JApiCmp to enforce control over API changes https://redirect.github.com/pmd/pmd/issues/4942;>#4942: [core] CPD: --skip-duplicate-files has no effect (7.0.0 regression) https://redirect.github.com/pmd/pmd/pull/4959;>#4959: [core] Upgrade saxon to 12.4 cli ... (truncated) Commits https://github.com/pmd/pmd/commit/592e80d4a9e01b4294d10bcad8ead80291c6ffa7;>592e80d [release] prepare release pmd_releases/7.1.0 https://github.com/pmd/pmd/commit/7d0dfa0b13e96dbbe678b067853631429c61f02e;>7d0dfa0 Prepare pmd release 7.1.0 https://github.com/pmd/pmd/commit/31585acc6f5f8aa396d3f1365df348da8e3ca076;>31585ac Bump build-tools from 24-SNAPSHOT to 24 https://github.com/pmd/pmd/commit/d0870f3aa3ddf8508bb172532bfa4a94a136a661;>d0870f3 [java] New rule ConfusingArgumentToVarargsMethod (https://redirect.github.com/pmd/pmd/issues/4971;>#4971) https://github.com/pmd/pmd/commit/04206ecd80dca03495c85c196365579c299732af;>04206ec Revert [ci] Disable auto-gen-config for regression tests https://github.com/pmd/pmd/commit/f5d47ac36e7975919bfafdd0c386f81da2038591;>f5d47ac [ci] Disable auto-gen-config for regression tests https://github.com/pmd/pmd/commit/102ba1e9625400912548e3ab3a19c765bb2d6727;>102ba1e [ci] Disable auto-gen-config for regression tests https://github.com/pmd/pmd/commit/a154f783bddf8f76ab9cd858eab0701c2e9ce1f8;>a154f78 [doc] Update all-contributors https://github.com/pmd/pmd/commit/16df3dd4469eae105c104deebfac951894f64e03;>16df3dd [core] Make CPD report maximal, non-repeating and non-overlapping duplicates ... https://github.com/pmd/pmd/commit/202943e0cfc2e5dc4f3b24778460693c5aeb9443;>202943e [java] Fix
[jira] [Updated] (MRESOLVER-553) Undo site redirection
[ https://issues.apache.org/jira/browse/MRESOLVER-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-553: -- Fix Version/s: 2.0.0 > Undo site redirection > - > > Key: MRESOLVER-553 > URL: https://issues.apache.org/jira/browse/MRESOLVER-553 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > Undo MRESOLVER-552 as it was done when 1.x was already staged and on vote. > It is actually 1.x that should go LATEST-1.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-553) Undo site redirection
Tamas Cservenak created MRESOLVER-553: - Summary: Undo site redirection Key: MRESOLVER-553 URL: https://issues.apache.org/jira/browse/MRESOLVER-553 Project: Maven Resolver Issue Type: Task Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0-beta-1 Undo MRESOLVER-552 as it was done when 1.x was already staged and on vote. It is actually 1.x that should go LATEST-1.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-552) Redirect site creation to enable concurrent release of 1.x and 2.x resolver
[
https://issues.apache.org/jira/browse/MRESOLVER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-552.
-
Resolution: Fixed
> Redirect site creation to enable concurrent release of 1.x and 2.x resolver
> ---
>
> Key: MRESOLVER-552
> URL: https://issues.apache.org/jira/browse/MRESOLVER-552
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> Basically just append and make it {{LATEST-2.x}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-552) Redirect site creation to enable concurrent release of 1.x and 2.x resolver
[
https://issues.apache.org/jira/browse/MRESOLVER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MRESOLVER-552:
-
Assignee: Tamas Cservenak
> Redirect site creation to enable concurrent release of 1.x and 2.x resolver
> ---
>
> Key: MRESOLVER-552
> URL: https://issues.apache.org/jira/browse/MRESOLVER-552
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> Basically just append and make it {{LATEST-2.x}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-542) Reduce usage of final classes
[ https://issues.apache.org/jira/browse/MRESOLVER-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-542. - Resolution: Fixed > Reduce usage of final classes > - > > Key: MRESOLVER-542 > URL: https://issues.apache.org/jira/browse/MRESOLVER-542 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-alpha-11 > > > Historically, Resolver APIs were exposed via Maven (were kinda part of Maven > API in Maven3) and they went long run to keep boundaries what users can do. > One of these examples is overuse of `final` classes. > Main goal was to make GenericVersionScheme not final, also perform some > cleanup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-552) Redirect site creation to enable concurrent release of 1.x and 2.x resolver
[
https://issues.apache.org/jira/browse/MRESOLVER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841166#comment-17841166
]
ASF GitHub Bot commented on MRESOLVER-552:
--
cstamas merged PR #485:
URL: https://github.com/apache/maven-resolver/pull/485
> Redirect site creation to enable concurrent release of 1.x and 2.x resolver
> ---
>
> Key: MRESOLVER-552
> URL: https://issues.apache.org/jira/browse/MRESOLVER-552
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> Basically just append and make it {{LATEST-2.x}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MRESOLVER-552] Redirect site staging [maven-resolver]
cstamas merged PR #485: URL: https://github.com/apache/maven-resolver/pull/485 -- 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] (MRESOLVER-542) Reduce usage of final classes
[ https://issues.apache.org/jira/browse/MRESOLVER-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841163#comment-17841163 ] ASF GitHub Bot commented on MRESOLVER-542: -- cstamas merged PR #479: URL: https://github.com/apache/maven-resolver/pull/479 > Reduce usage of final classes > - > > Key: MRESOLVER-542 > URL: https://issues.apache.org/jira/browse/MRESOLVER-542 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-alpha-11 > > > Historically, Resolver APIs were exposed via Maven (were kinda part of Maven > API in Maven3) and they went long run to keep boundaries what users can do. > One of these examples is overuse of `final` classes. > Main goal was to make GenericVersionScheme not final, also perform some > cleanup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-542] Reduce usage of final classes [maven-resolver]
cstamas merged PR #479: URL: https://github.com/apache/maven-resolver/pull/479 -- 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] (MRESOLVER-552) Redirect site creation to enable concurrent release of 1.x and 2.x resolver
[
https://issues.apache.org/jira/browse/MRESOLVER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841161#comment-17841161
]
ASF GitHub Bot commented on MRESOLVER-552:
--
cstamas opened a new pull request, #485:
URL: https://github.com/apache/maven-resolver/pull/485
So make possible simultanous release of 1.x and 2.x resolver.
---
https://issues.apache.org/jira/browse/MRESOLVER-552
> Redirect site creation to enable concurrent release of 1.x and 2.x resolver
> ---
>
> Key: MRESOLVER-552
> URL: https://issues.apache.org/jira/browse/MRESOLVER-552
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> Basically just append and make it {{LATEST-2.x}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MRESOLVER-552) Redirect site creation to enable concurrent release of 1.x and 2.x resolver
Tamas Cservenak created MRESOLVER-552:
-
Summary: Redirect site creation to enable concurrent release of
1.x and 2.x resolver
Key: MRESOLVER-552
URL: https://issues.apache.org/jira/browse/MRESOLVER-552
Project: Maven Resolver
Issue Type: Task
Components: Resolver
Reporter: Tamas Cservenak
Fix For: 2.0.0, 2.0.0-alpha-11
Basically just append and make it {{LATEST-2.x}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOLVER-542) Reduce usage of final classes
[ https://issues.apache.org/jira/browse/MRESOLVER-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-542: -- Description: Historically, Resolver APIs were exposed via Maven (were kinda part of Maven API in Maven3) and they went long run to keep boundaries what users can do. One of these examples is overuse of `final` classes. Main goal was to make GenericVersionScheme not final, also perform some cleanup. was:Historically, Resolver APIs were exposed via Maven (were kinda part of Maven API in Maven3) and they went long run to keep boundaries what users can do. One of these examples is overuse of `final` classes. > Reduce usage of final classes > - > > Key: MRESOLVER-542 > URL: https://issues.apache.org/jira/browse/MRESOLVER-542 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-alpha-11 > > > Historically, Resolver APIs were exposed via Maven (were kinda part of Maven > API in Maven3) and they went long run to keep boundaries what users can do. > One of these examples is overuse of `final` classes. > Main goal was to make GenericVersionScheme not final, also perform some > cleanup. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-550) Bump Redisson from 3.28.0 to 3.29.0
[ https://issues.apache.org/jira/browse/MRESOLVER-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-550. - Resolution: Fixed > Bump Redisson from 3.28.0 to 3.29.0 > --- > > Key: MRESOLVER-550 > URL: https://issues.apache.org/jira/browse/MRESOLVER-550 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-551) (build) Bump japicmp from 0.17.2 to 0.21.1
[ https://issues.apache.org/jira/browse/MRESOLVER-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-551. - Resolution: Fixed > (build) Bump japicmp from 0.17.2 to 0.21.1 > -- > > Key: MRESOLVER-551 > URL: https://issues.apache.org/jira/browse/MRESOLVER-551 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-549) Use parent POM 42
[ https://issues.apache.org/jira/browse/MRESOLVER-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-549. - Resolution: Fixed > Use parent POM 42 > - > > Key: MRESOLVER-549 > URL: https://issues.apache.org/jira/browse/MRESOLVER-549 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-549] Parent POM 42 [maven-resolver]
cstamas merged PR #484: URL: https://github.com/apache/maven-resolver/pull/484 -- 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] (MRESOLVER-549) Use parent POM 42
[ https://issues.apache.org/jira/browse/MRESOLVER-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841136#comment-17841136 ] ASF GitHub Bot commented on MRESOLVER-549: -- cstamas merged PR #484: URL: https://github.com/apache/maven-resolver/pull/484 > Use parent POM 42 > - > > Key: MRESOLVER-549 > URL: https://issues.apache.org/jira/browse/MRESOLVER-549 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-547) BF collector always copies artifacts, even when it should not
[ https://issues.apache.org/jira/browse/MRESOLVER-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-547: -- Issue Type: Bug (was: Improvement) > BF collector always copies artifacts, even when it should not > - > > Key: MRESOLVER-547 > URL: https://issues.apache.org/jira/browse/MRESOLVER-547 > Project: Maven Resolver > Issue Type: Bug > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-alpha-11, 1.9.20 > > > Artifact instances are always copied, even when they should not be. > https://github.com/apache/maven-resolver/blob/9c2e5a1d29254d1c3b49dd25dca310c0cec8e1f6/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/collect/bf/BfDependencyCollector.java#L454 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-550) Bump Redisson from 3.28.0 to 3.29.0
[ https://issues.apache.org/jira/browse/MRESOLVER-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-550: - Assignee: Tamas Cservenak > Bump Redisson from 3.28.0 to 3.29.0 > --- > > Key: MRESOLVER-550 > URL: https://issues.apache.org/jira/browse/MRESOLVER-550 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-551) (build) Bump japicmp from 0.17.2 to 0.21.1
[ https://issues.apache.org/jira/browse/MRESOLVER-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-551: - Assignee: Tamas Cservenak > (build) Bump japicmp from 0.17.2 to 0.21.1 > -- > > Key: MRESOLVER-551 > URL: https://issues.apache.org/jira/browse/MRESOLVER-551 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-549) Use parent POM 42
[ https://issues.apache.org/jira/browse/MRESOLVER-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-549: - Assignee: Tamas Cservenak > Use parent POM 42 > - > > Key: MRESOLVER-549 > URL: https://issues.apache.org/jira/browse/MRESOLVER-549 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-550) Bump Redisson from 3.28.0 to 3.29.0
Tamas Cservenak created MRESOLVER-550: - Summary: Bump Redisson from 3.28.0 to 3.29.0 Key: MRESOLVER-550 URL: https://issues.apache.org/jira/browse/MRESOLVER-550 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-551) (build) Bump japicmp from 0.17.2 to 0.21.1
Tamas Cservenak created MRESOLVER-551: - Summary: (build) Bump japicmp from 0.17.2 to 0.21.1 Key: MRESOLVER-551 URL: https://issues.apache.org/jira/browse/MRESOLVER-551 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-549) Use parent POM 42
[ https://issues.apache.org/jira/browse/MRESOLVER-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841132#comment-17841132 ] ASF GitHub Bot commented on MRESOLVER-549: -- cstamas opened a new pull request, #484: URL: https://github.com/apache/maven-resolver/pull/484 Demos were using implicit sisu index creation that is now disabled in parent, so needs sisu plugin --- https://issues.apache.org/jira/browse/MRESOLVER-549 > Use parent POM 42 > - > > Key: MRESOLVER-549 > URL: https://issues.apache.org/jira/browse/MRESOLVER-549 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 1.9.20 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-499) IPC Named Locks
[ https://issues.apache.org/jira/browse/MRESOLVER-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-499: -- Fix Version/s: (was: 2.0.0-alpha-11) > IPC Named Locks > --- > > Key: MRESOLVER-499 > URL: https://issues.apache.org/jira/browse/MRESOLVER-499 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > Create IPC named locks implementation. Depends on MRESOLVER-421. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-549) Use parent POM 42
Tamas Cservenak created MRESOLVER-549: - Summary: Use parent POM 42 Key: MRESOLVER-549 URL: https://issues.apache.org/jira/browse/MRESOLVER-549 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 1.9.20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump com.gradle:gradle-enterprise-maven-extension from 1.17.3 to 1.20.1 [maven-mvnd]
dependabot[bot] closed pull request #947: Bump com.gradle:gradle-enterprise-maven-extension from 1.17.3 to 1.20.1 URL: https://github.com/apache/maven-mvnd/pull/947 -- 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
Re: [PR] Bump com.gradle:gradle-enterprise-maven-extension from 1.17.3 to 1.20.1 [maven-mvnd]
dependabot[bot] commented on PR #947: URL: https://github.com/apache/maven-mvnd/pull/947#issuecomment-2078972134 Looks like com.gradle:gradle-enterprise-maven-extension is no longer a dependency, 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
Re: [PR] Bump com.gradle:common-custom-user-data-maven-extension from 1.12 to 2 [maven-mvnd]
dependabot[bot] closed pull request #960: Bump com.gradle:common-custom-user-data-maven-extension from 1.12 to 2 URL: https://github.com/apache/maven-mvnd/pull/960 -- 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
Re: [PR] Bump com.gradle:common-custom-user-data-maven-extension from 1.12 to 2 [maven-mvnd]
dependabot[bot] commented on PR #960: URL: https://github.com/apache/maven-mvnd/pull/960#issuecomment-2078971754 Looks like com.gradle:common-custom-user-data-maven-extension is no longer a dependency, 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
Re: [PR] Update provisio [maven-mvnd]
cstamas merged PR #975: URL: https://github.com/apache/maven-mvnd/pull/975 -- 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
[PR] [MNG-7266] Remove maven-compat [maven]
Giovds opened a new pull request, #1487: URL: https://github.com/apache/maven/pull/1487 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/MNG) 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 `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. - [x] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`. Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message. - [ ] 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. - [ ] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. 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. - [ ] 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). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- 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-7266) Remove maven-compat module
[ https://issues.apache.org/jira/browse/MNG-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841106#comment-17841106 ] ASF GitHub Bot commented on MNG-7266: - Giovds opened a new pull request, #1487: URL: https://github.com/apache/maven/pull/1487 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/MNG) 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 `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. - [x] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`. Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message. - [ ] 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. - [ ] You have run the [Core IT][core-its] successfully. If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. 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. - [ ] 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). [core-its]: https://maven.apache.org/core-its/core-it-suite/ > Remove maven-compat module > -- > > Key: MNG-7266 > URL: https://issues.apache.org/jira/browse/MNG-7266 > Project: Maven > Issue Type: Sub-task >Reporter: Guillaume Nodet >Priority: Major > Fix For: 4.0.x-candidate > > > Maven-core does not depend on maven-compat anymore (runtime or compile time). > Do we want to carry it over up to 4.0.0 and delete it in 4.1.0, or do we > want to drop it before 4.0.0 ? > [~cstamas] [~olamy] [~romain.manni-bucau] [~sjaranowski] and others... ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Upgrade develocity [maven-mvnd]
gnodet closed pull request #952: Upgrade develocity URL: https://github.com/apache/maven-mvnd/pull/952 -- 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
