[jira] [Commented] (MNG-7701) Incompatible version sorting changes
[
https://issues.apache.org/jira/browse/MNG-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694394#comment-17694394
]
Tamas Cservenak commented on MNG-7701:
--
Given we have MNG-7690, it is safe to assume that resolver Version (the "new"
implementation) does the right thing, while maven-artifact (the "old"
implementation) does the wrong thing, maybe we need to agree simply to move
away from old one in favor of new one?
> Incompatible version sorting changes
>
>
> Key: MNG-7701
> URL: https://issues.apache.org/jira/browse/MNG-7701
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.7, 3.9.0
>Reporter: David M. Lloyd
>Assignee: Elliotte Rusty Harold
>Priority: Major
>
> Between 3.8.6 and 3.8.7, the sorting of a variety of version strings has
> changed. This table captures the observed relations:
> ||Input 1||3.8.6||3.8.7||Input 2||
> |{{0.x}}|{{>}}|{{==}}|{{0-x}}|
> |{{1.x}}|{{<}}|{{==}}|{{1-x}}|
> |{{1.x}}|{{<}}|{{>}}|{{1_y}}|
> |{{1.y}}|{{<}}|{{>}}|{{1_x}}|
> |{{1-alpha}}|{{>}}|{{==}}|{{1.alpha}}|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-jlink-plugin] slachiewicz merged pull request #147: Bump maven-compiler-plugin from 3.8.1 to 3.11.0
slachiewicz merged PR #147: URL: https://github.com/apache/maven-jlink-plugin/pull/147 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] slachiewicz merged pull request #146: Bump maven-plugin-plugin from 3.6.2 to 3.8.1
slachiewicz merged PR #146: URL: https://github.com/apache/maven-jlink-plugin/pull/146 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] dependabot[bot] commented on pull request #129: Bump jettyVersion from 9.4.50.v20221201 to 10.0.14
dependabot[bot] commented on PR #129: URL: https://github.com/apache/maven-site-plugin/pull/129#issuecomment-1447702177 OK, I won't notify you about version 10.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
[GitHub] [maven-site-plugin] dependabot[bot] commented on pull request #129: Bump jettyVersion from 9.4.50.v20221201 to 10.0.14
dependabot[bot] commented on PR #129: URL: https://github.com/apache/maven-site-plugin/pull/129#issuecomment-1447702022 OK, I won't notify you about version 10.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
[GitHub] [maven-site-plugin] dependabot[bot] closed pull request #129: Bump jettyVersion from 9.4.50.v20221201 to 10.0.14
dependabot[bot] closed pull request #129: Bump jettyVersion from 9.4.50.v20221201 to 10.0.14 URL: https://github.com/apache/maven-site-plugin/pull/129 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] slachiewicz commented on pull request #129: Bump jettyVersion from 9.4.50.v20221201 to 10.0.14
slachiewicz commented on PR #129: URL: https://github.com/apache/maven-site-plugin/pull/129#issuecomment-1447701968 @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
[GitHub] [maven-shade-plugin] dependabot[bot] commented on pull request #176: Bump mavenVersion from 3.2.5 to 3.9.0
dependabot[bot] commented on PR #176: URL: https://github.com/apache/maven-shade-plugin/pull/176#issuecomment-1447701536 OK, I won't notify you about version 3.9.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
[GitHub] [maven-shade-plugin] dependabot[bot] closed pull request #176: Bump mavenVersion from 3.2.5 to 3.9.0
dependabot[bot] closed pull request #176: Bump mavenVersion from 3.2.5 to 3.9.0 URL: https://github.com/apache/maven-shade-plugin/pull/176 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shade-plugin] slachiewicz commented on pull request #176: Bump mavenVersion from 3.2.5 to 3.9.0
slachiewicz commented on PR #176: URL: https://github.com/apache/maven-shade-plugin/pull/176#issuecomment-1447701488 @dependabot ignore this minor 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
[jira] [Created] (MRESOLVER-332) Could not acquire write lock
Delany created MRESOLVER-332:
Summary: Could not acquire write lock
Key: MRESOLVER-332
URL: https://issues.apache.org/jira/browse/MRESOLVER-332
Project: Maven Resolver
Issue Type: Bug
Components: Resolver
Affects Versions: 1.9.4
Reporter: Delany
*
{noformat}
07:59:36 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce (fail) on project
distribution-noidentityjars: Execution fail of goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could not
acquire write lock for 'artifact:org.junit.jupiter:junit-jupiter:5.9.0' ->
[Help 1]
07:59:36 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce
(fail) on project distribution-noidentityjars: Execution fail of goal
org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce failed: Could not
acquire write lock for 'artifact:org.junit.jupiter:junit-jupiter:5.9.0'07:59:36
Caused by: java.lang.IllegalStateException: Could not acquire write lock for
'artifact:org.junit.jupiter:junit-jupiter:5.9.0'
07:59:36 at
org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire
(NamedLockFactoryAdapter.java:184)
07:59:36 at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:276)
07:59:36 at
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
(DefaultArtifactResolver.java:255)
07:59:36 at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
(DefaultRepositorySystem.java:296)
07:59:36 at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:197)
07:59:36 at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:413)
07:59:36 at
org.apache.maven.repository.legacy.LegacyRepositorySystem.resolve
(LegacyRepositorySystem.java:332)
07:59:36 at
org.apache.maven.plugins.enforcer.AbstractResolveDependencies.resolveArtifact
(AbstractResolveDependencies.java:152)
07:59:36 at
org.apache.maven.plugins.enforcer.AbstractResolveDependencies.getAllDescendants
(AbstractResolveDependencies.java:124)
07:59:36 at
org.apache.maven.plugins.enforcer.AbstractResolveDependencies.getDependenciesToCheck
(AbstractResolveDependencies.java:95)
07:59:36 at
org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute
(AbstractResolveDependencies.java:76)
07:59:36 at org.apache.maven.plugins.enforcer.EnforceMojo.executeRuleOld
(EnforceMojo.java:342)
07:59:36 at org.apache.maven.plugins.enforcer.EnforceMojo.executeRule
(EnforceMojo.java:323)
07:59:36 at org.apache.maven.plugins.enforcer.EnforceMojo.execute
(EnforceMojo.java:248)
07:59:36 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:342)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:330)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:175)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:76)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:163)
07:59:36 at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
07:59:36 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:160)
07:59:36 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
07:59:36 at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
07:59:36 at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
07:59:36 at java.util.concurrent.FutureTask.run (FutureTask.java:264)
07:59:36 at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:515)
07:59:36 at java.util.concurrent.FutureTask.run (FutureTask.java:264)
07:59:36 at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1128)
07:59:36 at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:628)
07:59:36 at java.lang.Thread.run (Thread.java:829){noformat}
* maven v3.9.0
* maven-enforcer-plugin v3.2.1
via Jenkins on Windows Server 2016
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-help-plugin] dependabot[bot] closed pull request #83: Bump mavenPluginToolsVersion from 3.6.4 to 3.7.1
dependabot[bot] closed pull request #83: Bump mavenPluginToolsVersion from 3.6.4 to 3.7.1 URL: https://github.com/apache/maven-help-plugin/pull/83 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-help-plugin] dependabot[bot] commented on pull request #83: Bump mavenPluginToolsVersion from 3.6.4 to 3.7.1
dependabot[bot] commented on PR #83: URL: https://github.com/apache/maven-help-plugin/pull/83#issuecomment-1447576805 Superseded by #85. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request, #133: Bump maven-compiler-plugin from 3.10.1 to 3.11.0
dependabot[bot] opened a new pull request, #133: URL: https://github.com/apache/maven-apache-parent/pull/133 Bumps [maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) from 3.10.1 to 3.11.0. Commits https://github.com/apache/maven-compiler-plugin/commit/eeda628b832bf3cc27571e2073f62d582a6d9527;>eeda628 [maven-release-plugin] prepare release maven-compiler-plugin-3.11.0 https://github.com/apache/maven-compiler-plugin/commit/82b799f3501d0dc3ef868859245816c563c46f04;>82b799f [MCOMPILER-527] Upgrade plexus-java to 1.1.2 (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/177;>#177) https://github.com/apache/maven-compiler-plugin/commit/f9c2350c885a96638db66fbab4d9180729a31d5a;>f9c2350 [MCOMPILER-526] Fix IT (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/178;>#178) https://github.com/apache/maven-compiler-plugin/commit/4022bd0f37626124dad394b2e4583fd6768fa74a;>4022bd0 [MCOMPILER-494] - Add a useModulePath switch to the testCompile mojo (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/119;>#119) https://github.com/apache/maven-compiler-plugin/commit/f4a8a54e116b07e888ac7b6371fa24b7a81517b3;>f4a8a54 [MCOMPILER-525] Incorrect detection of dependency change (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/172;>#172) https://github.com/apache/maven-compiler-plugin/commit/86b9f5972bcb005305f8abb8fb1f3c0d89df2726;>86b9f59 [MCOMPILER-395] Allow dependency exclusions for 'annotationProcessorPaths' (#... https://github.com/apache/maven-compiler-plugin/commit/e304ceb91cb625399638f95be41e6c23ca0970d0;>e304ceb [MCOMPILER-526] Ignore reformat commit for git blame https://github.com/apache/maven-compiler-plugin/commit/f7a4613eaa2364dcaf10f96f04a6b1afb2feb7ed;>f7a4613 [MCOMPILER-526] Reformat https://github.com/apache/maven-compiler-plugin/commit/cc78aee657a684af721b3efafd0e1525272d4201;>cc78aee [MCOMPILER-526] Upgrade to parent 39 https://github.com/apache/maven-compiler-plugin/commit/3dca82f4bf91e747c81ff3fe43e670f7cd7c08e1;>3dca82f [MCOMPILER-526] Add packages to please the formatter Additional commits viewable in https://github.com/apache/maven-compiler-plugin/compare/maven-compiler-plugin-3.10.1...maven-compiler-plugin-3.11.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-help-plugin] dependabot[bot] opened a new pull request, #85: Bump mavenPluginToolsVersion from 3.6.4 to 3.8.1
dependabot[bot] opened a new pull request, #85: URL: https://github.com/apache/maven-help-plugin/pull/85 Bumps `mavenPluginToolsVersion` from 3.6.4 to 3.8.1. Updates `maven-plugin-tools-generators` from 3.6.4 to 3.8.1 Release notes Sourced from https://github.com/apache/maven-plugin-tools/releases;>maven-plugin-tools-generators's releases. 3.7.1 3.7.0 Bug [https://issues.apache.org/jira/browse/MPLUGIN-298;>MPLUGIN-298] - The plugin descriptor generated by plugin:descriptor does not consider @ see javadoc taglets [https://issues.apache.org/jira/browse/MPLUGIN-394;>MPLUGIN-394] - Report-Mojo doesn't respect input encoding [https://issues.apache.org/jira/browse/MPLUGIN-403;>MPLUGIN-403] - Generating site reports for plugin results in NoSuchMethodError [https://issues.apache.org/jira/browse/MPLUGIN-404;>MPLUGIN-404] - JDK Requirements in plugin-info.html: Consider property maven.compiler.release [https://issues.apache.org/jira/browse/MPLUGIN-420;>MPLUGIN-420] - Parameters documentation inheriting @ since from Mojo can be confusing [https://issues.apache.org/jira/browse/MPLUGIN-428;>MPLUGIN-428] - Don't emit warning for missing javadoc URL of primitives [https://issues.apache.org/jira/browse/MPLUGIN-429;>MPLUGIN-429] - Don't emit warning for missing javadoc URI if no javadoc sources are configured [https://issues.apache.org/jira/browse/MPLUGIN-438;>MPLUGIN-438] - Parameter description should be taken from annotated item New Feature [https://issues.apache.org/jira/browse/MPLUGIN-9;>MPLUGIN-9] - Add link to javadoc in configuration description page for user defined types of Mojos. [https://issues.apache.org/jira/browse/MPLUGIN-396;>MPLUGIN-396] - Allow only @ Deprecated annotation without @ deprecated javadoc tag [https://issues.apache.org/jira/browse/MPLUGIN-400;>MPLUGIN-400] - add system requirements history section [https://issues.apache.org/jira/browse/MPLUGIN-402;>MPLUGIN-402] - report: allow to generate usage section in plugin-info.html with true [https://issues.apache.org/jira/browse/MPLUGIN-419;>MPLUGIN-419] - Allow @ Parameter on setters methods [https://issues.apache.org/jira/browse/MPLUGIN-423;>MPLUGIN-423] - Extract plugin report into its own plugin [https://issues.apache.org/jira/browse/MPLUGIN-427;>MPLUGIN-427] - report: Expose generics information of Collection and Map types Improvement [https://issues.apache.org/jira/browse/MPLUGIN-297;>MPLUGIN-297] - plugin-info.html should contain a better Usage section [https://issues.apache.org/jira/browse/MPLUGIN-390;>MPLUGIN-390] - Do not overwrite generate files with no content change [https://issues.apache.org/jira/browse/MPLUGIN-393;>MPLUGIN-393] - Upgrade to JUnit 5 and @ Inject annotations [https://issues.apache.org/jira/browse/MPLUGIN-398;>MPLUGIN-398] - Support for java 20 - ASM 9.4 [https://issues.apache.org/jira/browse/MPLUGIN-405;>MPLUGIN-405] - Don't print empty Memory, Disk Space in System Requirements [https://issues.apache.org/jira/browse/MPLUGIN-408;>MPLUGIN-408] - simplification in helpmojo build [https://issues.apache.org/jira/browse/MPLUGIN-411;>MPLUGIN-411] - Get rid of plexus-compiler-manager from tests [https://issues.apache.org/jira/browse/MPLUGIN-412;>MPLUGIN-412] - Use Maven core artifacts in provided scope [https://issues.apache.org/jira/browse/MPLUGIN-417;>MPLUGIN-417] - report and descriptor goal need to evaluate Javadoc comments differently [https://issues.apache.org/jira/browse/MPLUGIN-433;>MPLUGIN-433] - Allow to reference aggregator javadoc from plugin report Task ... (truncated) Commits https://github.com/apache/maven-plugin-tools/commit/b242658bf0b3abbc9758cfe61e669d0e77037946;>b242658 [maven-release-plugin] prepare release maven-plugin-tools-3.8.1 https://github.com/apache/maven-plugin-tools/commit/2721944828592167a714bec304e8f368f6c87daf;>2721944 Revert Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/1;>#1... https://github.com/apache/maven-plugin-tools/commit/d99a455f772c1728efb732795fe06e5d2d34ecc1;>d99a455 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-plugin-tools/commit/9ca8a18dbb47c9f7e7450a85353316c6c51882e4;>9ca8a18 [maven-release-plugin] prepare release maven-plugin-tools-3.8.0 https://github.com/apache/maven-plugin-tools/commit/84f9a2e7b23aae884c5214564adb8c4759b0776f;>84f9a2e [MPLUGIN-455] Bump plexus-archiver from 4.5.0 to 4.6.1 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/189;>#189) https://github.com/apache/maven-plugin-tools/commit/df4b8fdaf719daed8b060ee161cd60f49761783c;>df4b8fd Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3
[GitHub] [maven-apache-parent] dependabot[bot] closed pull request #125: Bump maven.plugin.tools.version from 3.7.0 to 3.7.1
dependabot[bot] closed pull request #125: Bump maven.plugin.tools.version from 3.7.0 to 3.7.1 URL: https://github.com/apache/maven-apache-parent/pull/125 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] dependabot[bot] commented on pull request #125: Bump maven.plugin.tools.version from 3.7.0 to 3.7.1
dependabot[bot] commented on PR #125: URL: https://github.com/apache/maven-apache-parent/pull/125#issuecomment-1447576668 Superseded by #132. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] dependabot[bot] closed pull request #100: Bump maven-compiler-plugin from 3.8.1 to 3.10.1
dependabot[bot] closed pull request #100: Bump maven-compiler-plugin from 3.8.1 to 3.10.1 URL: https://github.com/apache/maven-jlink-plugin/pull/100 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request, #132: Bump maven.plugin.tools.version from 3.7.0 to 3.8.1
dependabot[bot] opened a new pull request, #132: URL: https://github.com/apache/maven-apache-parent/pull/132 Bumps `maven.plugin.tools.version` from 3.7.0 to 3.8.1. Updates `maven-plugin-annotations` from 3.7.0 to 3.8.1 Release notes Sourced from https://github.com/apache/maven-plugin-tools/releases;>maven-plugin-annotations's releases. 3.7.1 Commits https://github.com/apache/maven-plugin-tools/commit/b242658bf0b3abbc9758cfe61e669d0e77037946;>b242658 [maven-release-plugin] prepare release maven-plugin-tools-3.8.1 https://github.com/apache/maven-plugin-tools/commit/2721944828592167a714bec304e8f368f6c87daf;>2721944 Revert Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/1;>#1... https://github.com/apache/maven-plugin-tools/commit/d99a455f772c1728efb732795fe06e5d2d34ecc1;>d99a455 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-plugin-tools/commit/9ca8a18dbb47c9f7e7450a85353316c6c51882e4;>9ca8a18 [maven-release-plugin] prepare release maven-plugin-tools-3.8.0 https://github.com/apache/maven-plugin-tools/commit/84f9a2e7b23aae884c5214564adb8c4759b0776f;>84f9a2e [MPLUGIN-455] Bump plexus-archiver from 4.5.0 to 4.6.1 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/189;>#189) https://github.com/apache/maven-plugin-tools/commit/df4b8fdaf719daed8b060ee161cd60f49761783c;>df4b8fd Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/195;>#195) https://github.com/apache/maven-plugin-tools/commit/25837eede059b63a2c249b139c6b6340a0d7ac89;>25837ee [MPLUGIN-441] Upgrade to maven alpha-4 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/191;>#191) https://github.com/apache/maven-plugin-tools/commit/4cd8c032197587292470978235df5b4c9d07602a;>4cd8c03 [MPLUGIN-454] Bump junit-bom from 5.9.1 to 5.9.2 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/193;>#193) https://github.com/apache/maven-plugin-tools/commit/52be8fafda3abee7404548f17fca6e1b7877fe41;>52be8fa [MPLUGIN-453] Fix Temporary File Information Disclosure (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/176;>#176) https://github.com/apache/maven-plugin-tools/commit/ce498163247c9059fba390397d59dda7494274da;>ce49816 [MPLUGIN-447] Ignore reformat commit rev in blame Additional commits viewable in https://github.com/apache/maven-plugin-tools/compare/maven-plugin-tools-3.7.0...maven-plugin-tools-3.8.1;>compare view Updates `maven-plugin-plugin` from 3.7.0 to 3.8.1 Release notes Sourced from https://github.com/apache/maven-plugin-tools/releases;>maven-plugin-plugin's releases. 3.7.1 Commits https://github.com/apache/maven-plugin-tools/commit/b242658bf0b3abbc9758cfe61e669d0e77037946;>b242658 [maven-release-plugin] prepare release maven-plugin-tools-3.8.1 https://github.com/apache/maven-plugin-tools/commit/2721944828592167a714bec304e8f368f6c87daf;>2721944 Revert Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/1;>#1... https://github.com/apache/maven-plugin-tools/commit/d99a455f772c1728efb732795fe06e5d2d34ecc1;>d99a455 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-plugin-tools/commit/9ca8a18dbb47c9f7e7450a85353316c6c51882e4;>9ca8a18 [maven-release-plugin] prepare release maven-plugin-tools-3.8.0 https://github.com/apache/maven-plugin-tools/commit/84f9a2e7b23aae884c5214564adb8c4759b0776f;>84f9a2e [MPLUGIN-455] Bump plexus-archiver from 4.5.0 to 4.6.1 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/189;>#189) https://github.com/apache/maven-plugin-tools/commit/df4b8fdaf719daed8b060ee161cd60f49761783c;>df4b8fd Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/195;>#195) https://github.com/apache/maven-plugin-tools/commit/25837eede059b63a2c249b139c6b6340a0d7ac89;>25837ee [MPLUGIN-441] Upgrade to maven alpha-4 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/191;>#191) https://github.com/apache/maven-plugin-tools/commit/4cd8c032197587292470978235df5b4c9d07602a;>4cd8c03 [MPLUGIN-454] Bump junit-bom from 5.9.1 to 5.9.2 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/193;>#193) https://github.com/apache/maven-plugin-tools/commit/52be8fafda3abee7404548f17fca6e1b7877fe41;>52be8fa [MPLUGIN-453] Fix Temporary File Information Disclosure (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/176;>#176)
[GitHub] [maven-jlink-plugin] dependabot[bot] commented on pull request #100: Bump maven-compiler-plugin from 3.8.1 to 3.10.1
dependabot[bot] commented on PR #100: URL: https://github.com/apache/maven-jlink-plugin/pull/100#issuecomment-1447576611 Superseded by #147. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] dependabot[bot] opened a new pull request, #147: Bump maven-compiler-plugin from 3.8.1 to 3.11.0
dependabot[bot] opened a new pull request, #147: URL: https://github.com/apache/maven-jlink-plugin/pull/147 Bumps [maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) from 3.8.1 to 3.11.0. Release notes Sourced from https://github.com/apache/maven-compiler-plugin/releases;>maven-compiler-plugin's releases. 3.10.1 New features and improvements https://issues.apache.org/jira/browse/MCOMPILER-426;>[MCOMPILER-426] - add flag to enable-preview java compiler feature (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/98;>#98) https://github.com/olamy;>@olamy Bug Fixes https://issues.apache.org/jira/browse/MCOMPILER-346;>[MCOMPILER-346] - workaround to jdk bug: assertion error from javaxcompiler javax.tools API (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/97;>#97) https://github.com/olamy;>@olamy https://issues.apache.org/jira/browse/MCOMPILER-485;>[MCOMPILER-485] - Fixes internal string format in generated package-info.class (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/95;>#95) https://github.com/dbwiddis;>@dbwiddis Dependency updates Bump maven-javadoc-plugin from 3.3.1 to 3.3.2 (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/94;>#94) https://github.com/dependabot;>@dependabot Other contributions thanks to https://github.com/basil;>@basil for providing an IT test for the fix of https://issues.apache.org/jira/browse/MCOMPILER-346;>[MCOMPILER-346] 3.10.0 Removed https://issues.apache.org/jira/browse/MCOMPILER-484;>[MCOMPILER-484] - Remove deprecated mojos (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/87;>#87) https://github.com/gnodet;>@gnodet New features and improvements https://issues.apache.org/jira/browse/MCOMPILER-205;>[MCOMPILER-205] - Add a boolean to generate missing package-info classes by default (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/88;>#88) https://github.com/gnodet;>@gnodet https://issues.apache.org/jira/browse/MCOMPILER-474;>[MCOMPILER-474] - Also check jar files when determining if dependencies changed (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/73;>#73) https://github.com/Powerrr;>@Powerrr Bug Fixes https://issues.apache.org/jira/browse/MCOMPILER-225;>[MCOMPILER-225] - javac.sh/javac.bat added to archive (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/91;>#91) https://github.com/olamy;>@olamy https://issues.apache.org/jira/browse/MCOMPILER-481;>[MCOMPILER-481] - compiler plugin should include static module for compilation (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/82;>#82) https://github.com/olamy;>@olamy https://issues.apache.org/jira/browse/MCOMPILER-470;>[MCOMPILER-470] -parameters doesn't work with --release https://issues.apache.org/jira/browse/MCOMPILER-460;>[MCOMPILER-460] - Compiler doesn't show detailed information with the Maven Toolchains Dependency updates use plexus-compiler 2.10.0 (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/92;>#92) https://github.com/olamy;>@olamy Bump mockito-core from 4.2.0 to 4.3.1 (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/83;>#83) https://github.com/dependabot;>@dependabot Documentation updates https://issues.apache.org/jira/browse/MCOMPILER-479;>[MCOMPILER-479] - Clarify compiler arguments Javadoc (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/90;>#90) https://github.com/hisener;>@hisener (doc) Fix typo and follow xml block style used for other parameters (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/89;>#89) https://github.com/pzygielo;>@pzygielo Build add more jdk for testing (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/93;>#93) https://github.com/olamy;>@olamy ... (truncated) Commits https://github.com/apache/maven-compiler-plugin/commit/eeda628b832bf3cc27571e2073f62d582a6d9527;>eeda628 [maven-release-plugin] prepare release maven-compiler-plugin-3.11.0 https://github.com/apache/maven-compiler-plugin/commit/82b799f3501d0dc3ef868859245816c563c46f04;>82b799f [MCOMPILER-527] Upgrade plexus-java to 1.1.2 (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/177;>#177) https://github.com/apache/maven-compiler-plugin/commit/f9c2350c885a96638db66fbab4d9180729a31d5a;>f9c2350 [MCOMPILER-526] Fix IT (https://github-redirect.dependabot.com/apache/maven-compiler-plugin/issues/178;>#178) https://github.com/apache/maven-compiler-plugin/commit/4022bd0f37626124dad394b2e4583fd6768fa74a;>4022bd0 [MCOMPILER-494] - Add
[GitHub] [maven-jlink-plugin] dependabot[bot] closed pull request #135: Bump maven-plugin-plugin from 3.6.2 to 3.7.1
dependabot[bot] closed pull request #135: Bump maven-plugin-plugin from 3.6.2 to 3.7.1 URL: https://github.com/apache/maven-jlink-plugin/pull/135 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] dependabot[bot] commented on pull request #135: Bump maven-plugin-plugin from 3.6.2 to 3.7.1
dependabot[bot] commented on PR #135: URL: https://github.com/apache/maven-jlink-plugin/pull/135#issuecomment-1447576414 Superseded by #146. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] dependabot[bot] opened a new pull request, #146: Bump maven-plugin-plugin from 3.6.2 to 3.8.1
dependabot[bot] opened a new pull request, #146: URL: https://github.com/apache/maven-jlink-plugin/pull/146 Bumps [maven-plugin-plugin](https://github.com/apache/maven-plugin-tools) from 3.6.2 to 3.8.1. Release notes Sourced from https://github.com/apache/maven-plugin-tools/releases;>maven-plugin-plugin's releases. 3.7.1 3.7.0 Bug [https://issues.apache.org/jira/browse/MPLUGIN-298;>MPLUGIN-298] - The plugin descriptor generated by plugin:descriptor does not consider @ see javadoc taglets [https://issues.apache.org/jira/browse/MPLUGIN-394;>MPLUGIN-394] - Report-Mojo doesn't respect input encoding [https://issues.apache.org/jira/browse/MPLUGIN-403;>MPLUGIN-403] - Generating site reports for plugin results in NoSuchMethodError [https://issues.apache.org/jira/browse/MPLUGIN-404;>MPLUGIN-404] - JDK Requirements in plugin-info.html: Consider property maven.compiler.release [https://issues.apache.org/jira/browse/MPLUGIN-420;>MPLUGIN-420] - Parameters documentation inheriting @ since from Mojo can be confusing [https://issues.apache.org/jira/browse/MPLUGIN-428;>MPLUGIN-428] - Don't emit warning for missing javadoc URL of primitives [https://issues.apache.org/jira/browse/MPLUGIN-429;>MPLUGIN-429] - Don't emit warning for missing javadoc URI if no javadoc sources are configured [https://issues.apache.org/jira/browse/MPLUGIN-438;>MPLUGIN-438] - Parameter description should be taken from annotated item New Feature [https://issues.apache.org/jira/browse/MPLUGIN-9;>MPLUGIN-9] - Add link to javadoc in configuration description page for user defined types of Mojos. [https://issues.apache.org/jira/browse/MPLUGIN-396;>MPLUGIN-396] - Allow only @ Deprecated annotation without @ deprecated javadoc tag [https://issues.apache.org/jira/browse/MPLUGIN-400;>MPLUGIN-400] - add system requirements history section [https://issues.apache.org/jira/browse/MPLUGIN-402;>MPLUGIN-402] - report: allow to generate usage section in plugin-info.html with true [https://issues.apache.org/jira/browse/MPLUGIN-419;>MPLUGIN-419] - Allow @ Parameter on setters methods [https://issues.apache.org/jira/browse/MPLUGIN-423;>MPLUGIN-423] - Extract plugin report into its own plugin [https://issues.apache.org/jira/browse/MPLUGIN-427;>MPLUGIN-427] - report: Expose generics information of Collection and Map types Improvement [https://issues.apache.org/jira/browse/MPLUGIN-297;>MPLUGIN-297] - plugin-info.html should contain a better Usage section [https://issues.apache.org/jira/browse/MPLUGIN-390;>MPLUGIN-390] - Do not overwrite generate files with no content change [https://issues.apache.org/jira/browse/MPLUGIN-393;>MPLUGIN-393] - Upgrade to JUnit 5 and @ Inject annotations [https://issues.apache.org/jira/browse/MPLUGIN-398;>MPLUGIN-398] - Support for java 20 - ASM 9.4 [https://issues.apache.org/jira/browse/MPLUGIN-405;>MPLUGIN-405] - Don't print empty Memory, Disk Space in System Requirements [https://issues.apache.org/jira/browse/MPLUGIN-408;>MPLUGIN-408] - simplification in helpmojo build [https://issues.apache.org/jira/browse/MPLUGIN-411;>MPLUGIN-411] - Get rid of plexus-compiler-manager from tests [https://issues.apache.org/jira/browse/MPLUGIN-412;>MPLUGIN-412] - Use Maven core artifacts in provided scope [https://issues.apache.org/jira/browse/MPLUGIN-417;>MPLUGIN-417] - report and descriptor goal need to evaluate Javadoc comments differently [https://issues.apache.org/jira/browse/MPLUGIN-433;>MPLUGIN-433] - Allow to reference aggregator javadoc from plugin report Task ... (truncated) Commits https://github.com/apache/maven-plugin-tools/commit/b242658bf0b3abbc9758cfe61e669d0e77037946;>b242658 [maven-release-plugin] prepare release maven-plugin-tools-3.8.1 https://github.com/apache/maven-plugin-tools/commit/2721944828592167a714bec304e8f368f6c87daf;>2721944 Revert Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/1;>#1... https://github.com/apache/maven-plugin-tools/commit/d99a455f772c1728efb732795fe06e5d2d34ecc1;>d99a455 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-plugin-tools/commit/9ca8a18dbb47c9f7e7450a85353316c6c51882e4;>9ca8a18 [maven-release-plugin] prepare release maven-plugin-tools-3.8.0 https://github.com/apache/maven-plugin-tools/commit/84f9a2e7b23aae884c5214564adb8c4759b0776f;>84f9a2e [MPLUGIN-455] Bump plexus-archiver from 4.5.0 to 4.6.1 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/189;>#189) https://github.com/apache/maven-plugin-tools/commit/df4b8fdaf719daed8b060ee161cd60f49761783c;>df4b8fd Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/195;>#195)
[GitHub] [maven-site-plugin] dependabot[bot] closed pull request #128: Bump jettyVersion from 9.4.50.v20221201 to 10.0.13
dependabot[bot] closed pull request #128: Bump jettyVersion from 9.4.50.v20221201 to 10.0.13 URL: https://github.com/apache/maven-site-plugin/pull/128 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] dependabot[bot] commented on pull request #128: Bump jettyVersion from 9.4.50.v20221201 to 10.0.13
dependabot[bot] commented on PR #128: URL: https://github.com/apache/maven-site-plugin/pull/128#issuecomment-1447576167 Superseded by #129. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-site-plugin] dependabot[bot] opened a new pull request, #129: Bump jettyVersion from 9.4.50.v20221201 to 10.0.14
dependabot[bot] opened a new pull request, #129: URL: https://github.com/apache/maven-site-plugin/pull/129 Bumps `jettyVersion` from 9.4.50.v20221201 to 10.0.14. Updates `jetty-server` from 9.4.50.v20221201 to 10.0.14 Release notes Sourced from https://github.com/eclipse/jetty.project/releases;>jetty-server's releases. 10.0.14 Special Thanks to the following Eclipse Jetty community members https://github.com/pzygielo;>@pzygielo (Piotrek Żygieło) https://github.com/jluehe;>@jluehe (jluehe) https://github.com/dzoech;>@dzoech (Dominik Zöchbauer) Changelog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9344;>#9344 - Cleanup Multipart handling https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9343;>#9343 - URI Host Mismatch with optional Compliance modes https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9339;>#9339 - Review Cookie Cutter https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9337;>#9337 - LowResourceMonitor.getReasons should include detailed reason instead of hard-coded message (https://github.com/jluehe;>@jluehe) https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9334;>#9334 - Better support for Cookie RFC 2965 compliance https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9285;>#9285 - ContextHandler sends redirect on BaseResponse instead of Wrapped Response object from Handler chain https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9283;>#9283 - Configurable Unsafe Host Header Behaviors https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9188;>#9188 - Log as info exceptions from server after sending stop with StopMojo. https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9183;>#9183 - ConnectHandler may close the connection instead of sending 200 OK https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9128;>#9128 - Do not execute any phase for maven plugin :start (https://github.com/pzygielo;>@pzygielo) https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9119;>#9119 - Wrong value of javax.servlet.forward.context_path attribute https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9092;>#9092 - Use ASM Bom https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9059;>#9059 - IteratingCallback not serializing close() and failed() https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9055;>#9055 - PathMappings optimizations https://github-redirect.dependabot.com/eclipse/jetty.project/issues/7650;>#7650 - QueuedThreadPool: Stopped without executing or closing null (https://github.com/dzoech;>@dzoech) Dependencies https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9242;>#9242 - Bump infinispan-bom to 11.0.17.Final https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9359;>#9359 - Bump maven.version to 3.9.0 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9102;>#9102 - Bump org.apache.aries.spifly.dynamic.bundle to 1.3.6 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9098;>#9098 - Bump org.eclipse.osgi to 3.18.200 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9106;>#9106 - Bump org.eclipse.osgi.services to 3.11.100 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9097;>#9097 - Bump protostream to 4.6.0.Final https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9367;>#9367 - Bump tycho-p2-repository-plugin to 3.0.2 10.0.13 Special Thanks to the following Eclipse Jetty community members https://github.com/janvojt;>@janvojt (Jan Vojt) https://github.com/joschi;>@joschi (Jochen Schalanda) https://github.com/leonchen83;>@leonchen83 (Baoyi Chen) https://github.com/cowwoc;>@cowwoc (Gili Tzabari) https://github.com/Vlatombe;>@Vlatombe (Vincent Latombe) Changelog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9006;>#9006 - WebSocket Message InputStream read() returns signed byte https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8913;>#8913 - Review Jetty XML syntax to allow calling JDK methods ... (truncated) Commits https://github.com/eclipse/jetty.project/commit/976721d0f3e903a243584d47870ad2f2c1bf9e55;>976721d Updating to version 10.0.14 https://github.com/eclipse/jetty.project/commit/b7075161d015ddce23fbf3db873d5f6b539f6a6b;>b707516 Fix osgi dependencies for update to org.eclipse.osgi.services. https://github.com/eclipse/jetty.project/commit/4d146412c8feac05c25d171b15c4f6ab4d42719b;>4d14641 Fix https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9334;>#9334 Cookie Compliance
[GitHub] [maven-indexer] dependabot[bot] commented on pull request #281: Bump jetty-webapp from 9.4.49.v20220914 to 11.0.13
dependabot[bot] commented on PR #281: URL: https://github.com/apache/maven-indexer/pull/281#issuecomment-1447575991 Superseded by #296. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shade-plugin] dependabot[bot] opened a new pull request, #176: Bump mavenVersion from 3.2.5 to 3.9.0
dependabot[bot] opened a new pull request, #176: URL: https://github.com/apache/maven-shade-plugin/pull/176 Bumps `mavenVersion` from 3.2.5 to 3.9.0. Updates `maven-plugin-api` from 3.2.5 to 3.9.0 Release notes Sourced from https://github.com/apache/maven/releases;>maven-plugin-api's releases. 3.9.0 https://maven.apache.org/docs/3.9.0/release-notes.html;>Release Notes - Maven - Version 3.9.0 Sub-task [https://issues.apache.org/jira/browse/MNG-7019;>MNG-7019] - Notify also at start when profile is missing [https://issues.apache.org/jira/browse/MNG-7447;>MNG-7447] - Several Improvements by using Stream API Bug [https://issues.apache.org/jira/browse/MNG-5222;>MNG-5222] - Maven 3 no longer logs warnings about deprecated plugin parameters. [https://issues.apache.org/jira/browse/MNG-6965;>MNG-6965] - Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath [https://issues.apache.org/jira/browse/MNG-7055;>MNG-7055] - Using MINSTALL/DEPLOY 3.0.0-M1+ does not write plugin information into maven-metadata.xml [https://issues.apache.org/jira/browse/MNG-7106;>MNG-7106] - VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds [https://issues.apache.org/jira/browse/MNG-7131;>MNG-7131] - maven.config doesn't handle arguments with spaces in them [https://issues.apache.org/jira/browse/MNG-7160;>MNG-7160] - Extension And Classloaders: difference of result given extension types [https://issues.apache.org/jira/browse/MNG-7316;>MNG-7316] - REGRESSION: MavenProject.getAttachedArtifacts() is read-only [https://issues.apache.org/jira/browse/MNG-7352;>MNG-7352] - org.apache.maven.toolchain.java.JavaToolchainImpl should be public [https://issues.apache.org/jira/browse/MNG-7413;>MNG-7413] - Fix POM model documentation confusion on report plugins, distribution repository and profile build [https://issues.apache.org/jira/browse/MNG-7425;>MNG-7425] - Maven artifact downloads sometimes result in empty zip files in local repository [https://issues.apache.org/jira/browse/MNG-7432;>MNG-7432] - [REGRESSION] Resolver session contains non-MavenWorkspaceReader [https://issues.apache.org/jira/browse/MNG-7433;>MNG-7433] - [REGRESSION] Multiple maven instances working on same source tree can lock each other [https://issues.apache.org/jira/browse/MNG-7441;>MNG-7441] - Update Version of (optional) Logback to Address CVE-2021-42550 [https://issues.apache.org/jira/browse/MNG-7448;>MNG-7448] - Don't ignore bin/ otherwise bin/ in apache-maven module cannot be readded [https://issues.apache.org/jira/browse/MNG-7459;>MNG-7459] - Revert MNG-7347 (SessionScoped beans should be singletons for a given session) [https://issues.apache.org/jira/browse/MNG-7471;>MNG-7471] - Resolver 1.8.0 introduces binary breakage in plugin using Resolver [https://issues.apache.org/jira/browse/MNG-7487;>MNG-7487] - Fix deadlock during forked lifecycle executions [https://issues.apache.org/jira/browse/MNG-7493;>MNG-7493] - [REGRESSION] Resolving dependencies between submodules fails [https://issues.apache.org/jira/browse/MNG-7504;>MNG-7504] - Warning about unknown reportPlugins parameters for m-site-p are always generated [https://issues.apache.org/jira/browse/MNG-7511;>MNG-7511] - Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest [https://issues.apache.org/jira/browse/MNG-7515;>MNG-7515] - Cannot see a dependency tree for apache-maven module [https://issues.apache.org/jira/browse/MNG-7529;>MNG-7529] - Maven resolver makes bad repository choices when resolving version ranges [https://issues.apache.org/jira/browse/MNG-7545;>MNG-7545] - Multi building can create bad files for downloaded artifacts in local repository [https://issues.apache.org/jira/browse/MNG-7563;>MNG-7563] - REGRESSION: User properties now override model properties in dependencies [https://issues.apache.org/jira/browse/MNG-7564;>MNG-7564] - Potential NPE in MavenMetadataSource [https://issues.apache.org/jira/browse/MNG-7568;>MNG-7568] - [WARNING] The requested profile ABCDEF could not be activated because it does not exist. [https://issues.apache.org/jira/browse/MNG-7578;>MNG-7578] - Building Linux image on Windows impossible (patch incuded) [https://issues.apache.org/jira/browse/MNG-7600;>MNG-7600] - LocalRepositoryManager is created too early [https://issues.apache.org/jira/browse/MNG-7606;>MNG-7606] - Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT [https://issues.apache.org/jira/browse/MNG-7621;>MNG-7621] - Parameter '-f' causes ignoring any 'maven.config' (only on Windows) [https://issues.apache.org/jira/browse/MNG-7624;>MNG-7624] - Plugins without non-mandatory goalPrefix are now logging incomplete info [https://issues.apache.org/jira/browse/MNG-7637;>MNG-7637] - Possible
[GitHub] [maven-indexer] dependabot[bot] closed pull request #281: Bump jetty-webapp from 9.4.49.v20220914 to 11.0.13
dependabot[bot] closed pull request #281: Bump jetty-webapp from 9.4.49.v20220914 to 11.0.13 URL: https://github.com/apache/maven-indexer/pull/281 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-indexer] dependabot[bot] opened a new pull request, #296: Bump jetty-webapp from 9.4.49.v20220914 to 11.0.14
dependabot[bot] opened a new pull request, #296: URL: https://github.com/apache/maven-indexer/pull/296 Bumps [jetty-webapp](https://github.com/eclipse/jetty.project) from 9.4.49.v20220914 to 11.0.14. Release notes Sourced from https://github.com/eclipse/jetty.project/releases;>jetty-webapp's releases. 11.0.14 Special Thanks to the following Eclipse Jetty community members https://github.com/pzygielo;>@pzygielo (Piotrek Żygieło) https://github.com/jluehe;>@jluehe (jluehe) https://github.com/dzoech;>@dzoech (Dominik Zöchbauer) Changelog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9344;>#9344 - Cleanup Multipart handling https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9343;>#9343 - URI Host Mismatch with optional Compliance modes https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9339;>#9339 - Review Cookie Cutter https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9337;>#9337 - LowResourceMonitor.getReasons should include detailed reason instead of hard-coded message (https://github.com/jluehe;>@jluehe) https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9334;>#9334 - Better support for Cookie RFC 2965 compliance https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9285;>#9285 - ContextHandler sends redirect on BaseResponse instead of Wrapped Response object from Handler chain https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9283;>#9283 - Configurable Unsafe Host Header Behaviors https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9188;>#9188 - Log as info exceptions from server after sending stop with StopMojo. https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9183;>#9183 - ConnectHandler may close the connection instead of sending 200 OK https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9181;>#9181 java.lang.NullPointerException in SessionHandler.checkRequestedSessionId() https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9128;>#9128 - Do not execute any phase for maven plugin :start (https://github.com/pzygielo;>@pzygielo) https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9119;>#9119 - Wrong value of javax.servlet.forward.context_path attribute https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9092;>#9092 - Use ASM Bom https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9059;>#9059 - IteratingCallback not serializing close() and failed() https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9055;>#9055 - PathMappings optimizations https://github-redirect.dependabot.com/eclipse/jetty.project/issues/7650;>#7650 - QueuedThreadPool: Stopped without executing or closing null (https://github.com/dzoech;>@dzoech) Dependencies https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9271;>#9271 - Bump infinispan-bom to 11.0.17.Final https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9359;>#9359 - Bump maven.version to 3.9.0 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9375;>#9375 - Bump jakarta.servlet.jsp-api to 3.1.1 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9102;>#9102 - Bump org.apache.aries.spifly.dynamic.bundle to 1.3.6 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9098;>#9098 - Bump org.eclipse.osgi to 3.18.200 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9106;>#9106 - Bump org.eclipse.osgi.services to 3.11.100 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9097;>#9097 - Bump protostream to 4.6.0.Final https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9367;>#9367 - Bump tycho-p2-repository-plugin to 3.0.2 11.0.13 Special Thanks to the following Eclipse Jetty community members https://github.com/janvojt;>@janvojt (Jan Vojt) https://github.com/joschi;>@joschi (Jochen Schalanda) https://github.com/leonchen83;>@leonchen83 (Baoyi Chen) https://github.com/cowwoc;>@cowwoc (Gili Tzabari) https://github.com/Vlatombe;>@Vlatombe (Vincent Latombe) Changelog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9006;>#9006 - WebSocket Message InputStream read() returns signed byte ... (truncated) Commits https://github.com/eclipse/jetty.project/commit/4601fe8dd805ce75b69c64466c115a162586641b;>4601fe8 Updating to version 11.0.14 https://github.com/eclipse/jetty.project/commit/5e1f579f723b9b52e4837e3ee5e0b01f0f515110;>5e1f579 revert upgrade from 3aaa65c45a1e783cbc76fca04dd7a545cfa5597b https://github.com/eclipse/jetty.project/commit/135f14f0d06cd52664499013785bf657465139d4;>135f14f Merge remote-tracking branch
[GitHub] [maven-parent] dependabot[bot] opened a new pull request, #112: Bump spotless-maven-plugin from 2.28.0 to 2.34.0
dependabot[bot] opened a new pull request, #112: URL: https://github.com/apache/maven-parent/pull/112 Bumps [spotless-maven-plugin](https://github.com/diffplug/spotless) from 2.28.0 to 2.34.0. Changelog Sourced from https://github.com/diffplug/spotless/blob/main/CHANGES.md;>spotless-maven-plugin's changelog. [2.34.0] - 2023-01-26 Added Formatter now has a field public static final File NO_FILE_SENTINEL which can be used to pass string content to a Formatter or FormatterStep when there is no actual File to format. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1525;>#1525) [2.33.0] - 2023-01-26 Added ProcessRunner has added some convenience methods so it can be used for maven testing. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1496;>#1496) ProcessRunner allows to limit captured output to a certain number of bytes. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1511;>#1511) ProcessRunner is now capable of handling long-running tasks where waiting for exit is delegated to the caller. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1511;>#1511) Allow to specify node executable for node-based formatters using nodeExecutable parameter (https://github-redirect.dependabot.com/diffplug/spotless/pull/1500;>#1500) Fixed The default list of type annotations used by formatAnnotations has had 8 more annotations from the Checker Framework added https://github-redirect.dependabot.com/diffplug/spotless/pull/1494;>#1494 Changes POTENTIALLY BREAKING Bump minimum JRE from 8 to 11, next release likely to bump bytecode to Java 11 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1514;>#1514 part 1 of https://github-redirect.dependabot.com/diffplug/spotless/issues/1337;>#1337) Rename YamlJacksonStep into JacksonYamlStep while normalizing Jackson usage (https://github-redirect.dependabot.com/diffplug/spotless/pull/1492;>#1492) Convert gson integration to use a compile-only source set (https://github-redirect.dependabot.com/diffplug/spotless/pull/1510;>#1510). ** POTENTIALLY BREAKING** Removed support for KtLint 0.3x and 0.45.2 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1475;>#1475) KtLint does not maintain a stable API - before this PR, we supported every breaking change in the API since 2019. From now on, we will support no more than 2 breaking changes at a time. NpmFormatterStepStateBase delays npm install call until the formatter is first used. This enables better integration with gradle-node-plugin. (https://github-redirect.dependabot.com/diffplug/spotless/pull/1522;>#1522) Bump default ktlint version to latest 0.48.1 - 0.48.2 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1529;>#1529) Bump default scalafmt version to latest 3.6.1 - 3.7.1 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1529;>#1529) [2.32.0] - 2023-01-13 Added Add option editorConfigFile for ktLint https://github-redirect.dependabot.com/diffplug/spotless/issues/142;>#142 POTENTIALLY BREAKING ktlint step now modifies license headers. Make sure to put licenseHeader after ktlint. Added skipLinesMatching option to licenseHeader to support formats where license header cannot be immediately added to the top of the file (e.g. xml, sh). (https://github-redirect.dependabot.com/diffplug/spotless/pull/1441;>#1441). Add YAML support through Jackson (https://github-redirect.dependabot.com/diffplug/spotless/pull/1478;>#1478) Added support for npm-based https://eslint.org/;>ESLint-formatter for javascript and typescript (https://github-redirect.dependabot.com/diffplug/spotless/pull/1453;>#1453) Better suggested messages when user's default is set by JVM limitation. (https://github-redirect.dependabot.com/diffplug/spotless/pull/995;>#995) Fixed Support ktlint 0.48+ new rule disabling syntax (https://github-redirect.dependabot.com/diffplug/spotless/pull/1456;>#1456) fixes (https://github-redirect.dependabot.com/diffplug/spotless/issues/1444;>#1444) Fix subgroups leading catch all matcher. Changes Bump default version for prettier from 2.0.5 to 2.8.1 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1453;>#1453) Bump the dev version of Gradle from 7.5.1 to 7.6 (https://github-redirect.dependabot.com/diffplug/spotless/pull/1409;>#1409) We also removed the no-longer-required dependency org.codehaus.groovy:groovy-xml Breaking changes to Spotless' internal testing infrastructure testlib (https://github-redirect.dependabot.com/diffplug/spotless/pull/1443;>#1443) ResourceHarness no longer has any duplicated functionality which was also present in StepHarness StepHarness now operates on Formatter rather than a FormatterStep StepHarnessWithFile now takes a ResourceHarness in its
[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request, #196: Bump mockito-core from 4.4.0 to 4.11.0
dependabot[bot] opened a new pull request, #196: URL: https://github.com/apache/maven-javadoc-plugin/pull/196 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.4.0 to 4.11.0. Release notes Sourced from https://github.com/mockito/mockito/releases;>mockito-core's releases. v4.11.0 Changelog generated by https://github.com/shipkit/shipkit-changelog;>Shipkit Changelog Gradle Plugin 4.11.0 2022-12-28 - https://github.com/mockito/mockito/compare/v4.10.0...v4.11.0;>1 commit(s) by Andy Coates Improve vararg handling: approach 2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2807;>#2807)](https://github-redirect.dependabot.com/mockito/mockito/pull/2807;>mockito/mockito#2807) Mocking varargs method with any(String[].class) doesn't work as expected [(https://github-redirect.dependabot.com/mockito/mockito/issues/2796;>#2796)](https://github-redirect.dependabot.com/mockito/mockito/issues/2796;>mockito/mockito#2796) (Argument)Matchers regression from 1.10.19 to 2.18.3 for varargs [(https://github-redirect.dependabot.com/mockito/mockito/issues/1498;>#1498)](https://github-redirect.dependabot.com/mockito/mockito/issues/1498;>mockito/mockito#1498) Cannot verify varargs parameter as an array [(https://github-redirect.dependabot.com/mockito/mockito/issues/1222;>#1222)](https://github-redirect.dependabot.com/mockito/mockito/issues/1222;>mockito/mockito#1222) ArgumentCaptor can't capture varargs-arrays [(https://github-redirect.dependabot.com/mockito/mockito/issues/584;>#584)](https://github-redirect.dependabot.com/mockito/mockito/issues/584;>mockito/mockito#584) Verification of an empty varargs call fails when isNotNull() is used [(https://github-redirect.dependabot.com/mockito/mockito/issues/567;>#567)](https://github-redirect.dependabot.com/mockito/mockito/issues/567;>mockito/mockito#567) v4.10.0 Changelog generated by https://github.com/shipkit/shipkit-changelog;>Shipkit Changelog Gradle Plugin 4.10.0 2022-12-14 - https://github.com/mockito/mockito/compare/v4.9.0...v4.10.0;>13 commit(s) by Andrei Solntsev, Andriy Redko, Andy Coates, Christopher Lambert, Marcono1234, Vladimir Glinskikh, dependabot[bot] Add new artifact mockito-subclass (to use mock-maker-subclass MockMaker) [(https://github-redirect.dependabot.com/mockito/mockito/issues/2821;>#2821)](https://github-redirect.dependabot.com/mockito/mockito/pull/2821;>mockito/mockito#2821) Bump gradle from 7.5.1 to 7.6 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2817;>#2817)](https://github-redirect.dependabot.com/mockito/mockito/pull/2817;>mockito/mockito#2817) Fix incorrect Javadoc inline tag for MockitoJUnitRunner [(https://github-redirect.dependabot.com/mockito/mockito/issues/2816;>#2816)](https://github-redirect.dependabot.com/mockito/mockito/pull/2816;>mockito/mockito#2816) Bump shipkit-auto-version from 1.2.1 to 1.2.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2811;>#2811)](https://github-redirect.dependabot.com/mockito/mockito/pull/2811;>mockito/mockito#2811) Bump com.github.ben-manes.versions from 0.42.0 to 0.44.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2810;>#2810)](https://github-redirect.dependabot.com/mockito/mockito/pull/2810;>mockito/mockito#2810) Bump kotlinVersion from 1.7.21 to 1.7.22 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2809;>#2809)](https://github-redirect.dependabot.com/mockito/mockito/pull/2809;>mockito/mockito#2809) Bump junit from 1.1.3 to 1.1.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2806;>#2806)](https://github-redirect.dependabot.com/mockito/mockito/pull/2806;>mockito/mockito#2806) Simplify MatcherApplicationStrategy [(https://github-redirect.dependabot.com/mockito/mockito/issues/2803;>#2803)](https://github-redirect.dependabot.com/mockito/mockito/pull/2803;>mockito/mockito#2803) Bump kotlinVersion from 1.7.10 to 1.7.21 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2801;>#2801)](https://github-redirect.dependabot.com/mockito/mockito/pull/2801;>mockito/mockito#2801) Bump espresso-core from 3.4.0 to 3.5.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2800;>#2800)](https://github-redirect.dependabot.com/mockito/mockito/pull/2800;>mockito/mockito#2800) Bump versions.bytebuddy from 1.12.16 to 1.12.19 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2799;>#2799)](https://github-redirect.dependabot.com/mockito/mockito/pull/2799;>mockito/mockito#2799) Upgrade errorprone from 2.14.0 to 2.16 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2794;>#2794)](https://github-redirect.dependabot.com/mockito/mockito/pull/2794;>mockito/mockito#2794) automatically detect class to mock
[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request, #195: Bump wagonVersion from 2.4 to 2.12
dependabot[bot] opened a new pull request, #195: URL: https://github.com/apache/maven-javadoc-plugin/pull/195 Bumps `wagonVersion` from 2.4 to 2.12. Updates `wagon-provider-api` from 2.4 to 2.12 Commits https://github.com/apache/maven-wagon/commit/0f2c8bc57a9b3094e6566ca601bf2025dabd0fe9;>0f2c8bc [maven-release-plugin] prepare release wagon-2.12 https://github.com/apache/maven-wagon/commit/6843ead404b0e05ec97ff80b1cbea0ecc7472e45;>6843ead Bump version 2.12-SNAPSHOT https://github.com/apache/maven-wagon/commit/3512a321ef678209167fa978d5aafe2fdf6bfff7;>3512a32 [WAGON-485] ScpWagon parses file size to int causing overflow for large files https://github.com/apache/maven-wagon/commit/01b5631f2712d4a983c2f43f7a0b0d3df784501a;>01b5631 [WAGON-484] Update WebDAV Provider naming https://github.com/apache/maven-wagon/commit/7a0db3b2207bd58d3f28219048d6722d241ed5ec;>7a0db3b [WAGON-483] Upgrade SLF4J to 1.7.22 https://github.com/apache/maven-wagon/commit/e89c03a15d3fb0450abbd85fed45872f64686fc1;>e89c03a [WAGON-475] TransferEvent GET used instead of PUT and vice versa https://github.com/apache/maven-wagon/commit/cd519b09cf589f1f38d3a52882a4907e7e78d4bb;>cd519b0 Revert bad release https://github.com/apache/maven-wagon/commit/7fd0dca33656e5f961e9234258db9e3a2cec0d9f;>7fd0dca [WAGON-481] Sensitive (auth) information is not cleared when HttpClientWagon ... https://github.com/apache/maven-wagon/commit/1a005f1c3fe7492c10b06567738453118f1c15b6;>1a005f1 [WAGON-480] Non-threadsafe HttpClientContext is shared between threaded use o... https://github.com/apache/maven-wagon/commit/4074598777fad44a3c34c71c5842b71a03e1da3f;>4074598 [WAGON-479] Preemptive auth with HTTP Provider may fail because BasicScheme i... Additional commits viewable in https://github.com/apache/maven-wagon/compare/wagon-2.4...wagon-2.12;>compare view Updates `wagon-http` from 2.4 to 2.12 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] dependabot[bot] opened a new pull request, #194: Bump jetty.version from 9.4.50.v20221201 to 9.4.51.v20230217
dependabot[bot] opened a new pull request, #194: URL: https://github.com/apache/maven-javadoc-plugin/pull/194 Bumps `jetty.version` from 9.4.50.v20221201 to 9.4.51.v20230217. Updates `jetty-server` from 9.4.50.v20221201 to 9.4.51.v20230217 Release notes Sourced from https://github.com/eclipse/jetty.project/releases;>jetty-server's releases. 9.4.51.v20230217 Sponsored Release This is a release of the https://github-redirect.dependabot.com/eclipse/jetty.project/issues/7958;>End of Community Support Jetty 9.x series that was sponsored by a https://github.com/eclipse/jetty.project/blob/HEAD/mailto:sa...@webtide.com;>support contract from Webtide.com Changelog https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9352;>#9352 - Update / Fix CookieCutter https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9345;>#9345 - Multipart Cleanups Dependencies https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9269;>#9269 - Bump ant.version to 1.10.13 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9370;>#9370 - Bump asciidoctorj-diagram to 2.2.4 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9364;>#9364 - Bump eclipse-jarsigner-plugin to 1.4.2 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9251;>#9251 - Bump infinispan.version to 11.0.17.Final https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9247;>#9247 - Bump maven-checkstyle-plugin to 3.2.1 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9267;>#9267 - Bump maven-dependency-plugin to 3.5.0 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9365;>#9365 - Bump maven-deploy-plugin to 3.1.0 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9252;>#9252 - Bump maven-enforcer-plugin to 3.2.1 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9363;>#9363 - Bump maven-invoker-plugin to 3.5.0 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9266;>#9266 - Bump maven-plugin-plugin to 3.7.1 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9263;>#9263 - Bump maven.plugin-tools.version to 3.7.1 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9256;>#9256 - Bump maven.resolver.version to 1.9.4 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9368;>#9368 - Bump maven.surefire.plugin.version to 3.0.0-M9 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9362;>#9362 - Bump maven.version to 3.9.0 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9100;>#9100 - Bump org.apache.aries.spifly.dynamic.bundle to 1.3.6 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9103;>#9103 - Bump org.eclipse.osgi to 3.18.200 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9110;>#9110 - Bump org.eclipse.osgi.services to 3.11.100 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9262;>#9262 - Bump spring-beans to 5.3.25 Commits https://github.com/eclipse/jetty.project/commit/b45c405e4544384de066f814ed42ae3dceacdd49;>b45c405 Updating to version 9.4.51.v20230217 https://github.com/eclipse/jetty.project/commit/3beaa8158c589da77ff35af90a52225b938abdb8;>3beaa81 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9368;>#9368 from eclipse/dependabot/maven/jetty-9.4.x/maven.sure... https://github.com/eclipse/jetty.project/commit/d382683e2be1dc7527bd628df988b3e27147a94a;>d382683 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9370;>#9370 from eclipse/dependabot/maven/jetty-9.4.x/org.asciid... https://github.com/eclipse/jetty.project/commit/d52d1336da67fac3a2f7a5889d5207c78d33c389;>d52d133 Bump maven.surefire.plugin.version from 3.0.0-M8 to 3.0.0-M9 https://github.com/eclipse/jetty.project/commit/1bc959a9c3be3769ec59660df74663ceaf586ea7;>1bc959a Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9365;>#9365 from eclipse/dependabot/maven/jetty-9.4.x/org.apache... https://github.com/eclipse/jetty.project/commit/08c89c797abef55c0a500e4440c6055e1f97ed90;>08c89c7 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9364;>#9364 from eclipse/dependabot/maven/jetty-9.4.x/org.eclips... https://github.com/eclipse/jetty.project/commit/2a30acaffef584a11c1a53b371ee6ee7535d0566;>2a30aca Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9363;>#9363 from eclipse/dependabot/maven/jetty-9.4.x/org.apache... https://github.com/eclipse/jetty.project/commit/6ab783d9c810f1a1e4469244e8194111c19345f4;>6ab783d Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/9362;>#9362 from
[jira] [Commented] (MRESOLVER-325) [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
[
https://issues.apache.org/jira/browse/MRESOLVER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694277#comment-17694277
]
Robert Muir commented on MRESOLVER-325:
---
>From
>https://thunk.org/tytso/blog/2009/03/15/dont-fear-the-fsync/#a-nameatomicity-not-durabilityathe-atomicity-not-durability-argument
{quote}
remember, fsync() doesn’t create extra I/O’s, although it may introduce latency
as the application waits for some of the pending I/O’s to complete.
{quote}
>From my understanding of your email, this is the behavior you want.
> [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
>
>
> Key: MRESOLVER-325
> URL: https://issues.apache.org/jira/browse/MRESOLVER-325
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.9.4
>Reporter: Christoph Läubrich
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> If one runs a build that otherwise works fine on 3.8.x with 3.9 we now get
> the following exception (full output can be found here
> https://github.com/eclipse-platform/eclipse.platform/actions/runs/4211467991/jobs/7309831666):
> {code:java}
> Error: 5.889 [ERROR] Internal error: java.io.UncheckedIOException:
> java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:108)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:821)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:270)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:121)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addRepo
> (EnhancedLocalRepositoryManager.java:274)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addArtifact
> (EnhancedLocalRepositoryManager.java:252)
> at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.add
> (EnhancedLocalRepositoryManager.java:225)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:680)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:197)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:413)
> at org.apache.maven.repository.legacy.LegacyRepositorySystem.resolve
> (LegacyRepositorySystem.java:332)
> at
>
[jira] [Commented] (MNG-7701) Incompatible version sorting changes
[
https://issues.apache.org/jira/browse/MNG-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694276#comment-17694276
]
David M. Lloyd commented on MNG-7701:
-
Also, closing the issue is not called for as the resolution is clearly
contested.
> Incompatible version sorting changes
>
>
> Key: MNG-7701
> URL: https://issues.apache.org/jira/browse/MNG-7701
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.7, 3.9.0
>Reporter: David M. Lloyd
>Assignee: Elliotte Rusty Harold
>Priority: Major
>
> Between 3.8.6 and 3.8.7, the sorting of a variety of version strings has
> changed. This table captures the observed relations:
> ||Input 1||3.8.6||3.8.7||Input 2||
> |{{0.x}}|{{>}}|{{==}}|{{0-x}}|
> |{{1.x}}|{{<}}|{{==}}|{{1-x}}|
> |{{1.x}}|{{<}}|{{>}}|{{1_y}}|
> |{{1.y}}|{{<}}|{{>}}|{{1_x}}|
> |{{1-alpha}}|{{>}}|{{==}}|{{1.alpha}}|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7701) Incompatible version sorting changes
[
https://issues.apache.org/jira/browse/MNG-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694269#comment-17694269
]
David M. Lloyd commented on MNG-7701:
-
It is easy to demonstrate that this is *not* fixed and also *not* in line with
the spec, with just this one important example (yes this does break for us):
{code}
$ jbang org.apache.maven:maven-artifact:3.8.6 1.0.final-redhat-0001
1.0.sp1-redhat-0001
Display parameters as parsed by Maven (in canonical form and as a list of
tokens) and comparison result:
1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
1.0.final-redhat-0001 < 1.0.sp1-redhat-0001
2. 1.0.sp1-redhat-0001 -> 1.0.sp-1-redhat-1; tokens: [1, 0, sp, [1, [redhat,
[1
{code}
versus
{code}
$ jbang org.apache.maven:maven-artifact:3.8.7 1.0.final-redhat-0001
1.0.sp1-redhat-0001
Display parameters as parsed by Maven (in canonical form and as a list of
tokens) and comparison result:
1. 1.0.final-redhat-0001 -> 1-redhat-1; tokens: [1, [redhat, [1]]]
1.0.final-redhat-0001 > 1.0.sp1-redhat-0001
2. 1.0.sp1-redhat-0001 -> 1-sp-1-redhat-1; tokens: [1, [sp, [1, [redhat, [1]
{code}
As you can see, our `sp` release is now ordered *after* our `final` release
despite this clear text in the "spec":
bq. Non-numeric tokens ("qualifiers") have the alphabetical order, except for
the following tokens which come first in this order: "alpha" < "beta" <
"milestone" < "rc" = "cr" < "snapshot" < "" = "final" = "ga" < "sp"
It's clear that this tokenization isn't really correct by any reasonable
measurement, and breaking large amounts of (our) existing artifacts in the wild
is definitely not OK.
> Incompatible version sorting changes
>
>
> Key: MNG-7701
> URL: https://issues.apache.org/jira/browse/MNG-7701
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.7, 3.9.0
>Reporter: David M. Lloyd
>Assignee: Elliotte Rusty Harold
>Priority: Major
>
> Between 3.8.6 and 3.8.7, the sorting of a variety of version strings has
> changed. This table captures the observed relations:
> ||Input 1||3.8.6||3.8.7||Input 2||
> |{{0.x}}|{{>}}|{{==}}|{{0-x}}|
> |{{1.x}}|{{<}}|{{==}}|{{1-x}}|
> |{{1.x}}|{{<}}|{{>}}|{{1_y}}|
> |{{1.y}}|{{<}}|{{>}}|{{1_x}}|
> |{{1-alpha}}|{{>}}|{{==}}|{{1.alpha}}|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [maven-surefire] Tibor17 opened a new pull request, #616: Test Indexes and Reporters
Tibor17 opened a new pull request, #616: URL: https://github.com/apache/maven-surefire/pull/616 @slawekjaranowski This is a work in progress. The test reporters must not determine the test status upon timings of test events. The test reporters must not identify the test run upon text literals (e.g. class and method) of the test entry. These are all the causes why parallel tests are chaotic in JUnit5 report. These are the causes why JUnit5 and JUnit4 parameterized tests give different reports. These are the causes why Cucumber is not able to work with dynamic tests. Nevertheless this would fix the issue with memory consumption in JUnit47 parallel test and the provider. So I have some doubts about #516 #544 and #608 and I will make the audit there as well. -- 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-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Sellers updated MNG-7705:
-
Attachment: MNG-7705_strace_2023-02-27.zip
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> MNG-7705_strace_2023-02-27.zip, apache-maven-3.9.1-SNAPSHOT-bin.tar.gz,
> maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
> at
> org.apache.maven.plugins.dependency.resolvers.ResolveDependenciesMojo.doExecute
>
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694181#comment-17694181
]
Jim Sellers commented on MNG-7705:
--
I tried to use {{strace -f -tt -e trace=file mvn}} for all the commands. I'm
attaching a zip where 1 of 3 concurrent builds failed.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
> at
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694179#comment-17694179
]
Michael Osipov commented on MNG-7705:
-
I need to look them up explicitly since I use truss on BSD. Add flags for
following forks, timestamps and write directly to file.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
>
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694157#comment-17694157
]
Jim Sellers commented on MNG-7705:
--
I'm sorry, I thought that the s was a typo and you had meant just the log. Was
there any specific flags that you wanted to make sure that I have set?
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
>
[jira] [Commented] (MRESOLVER-325) [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
[
https://issues.apache.org/jira/browse/MRESOLVER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694136#comment-17694136
]
Michael Osipov commented on MRESOLVER-325:
--
interesting, thank you Uwe. I will try that and let you know. That isn't
obvious. As far as I understand {{fsync()}} can also kill performance. since
those tracking files are written very often we need to take a look how much the
impact could be, but that massive depends on OS, H/W, FS, etc.
> [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
>
>
> Key: MRESOLVER-325
> URL: https://issues.apache.org/jira/browse/MRESOLVER-325
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.9.4
>Reporter: Christoph Läubrich
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> If one runs a build that otherwise works fine on 3.8.x with 3.9 we now get
> the following exception (full output can be found here
> https://github.com/eclipse-platform/eclipse.platform/actions/runs/4211467991/jobs/7309831666):
> {code:java}
> Error: 5.889 [ERROR] Internal error: java.io.UncheckedIOException:
> java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:108)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:821)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:270)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:121)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addRepo
> (EnhancedLocalRepositoryManager.java:274)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addArtifact
> (EnhancedLocalRepositoryManager.java:252)
> at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.add
> (EnhancedLocalRepositoryManager.java:225)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:680)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:197)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:413)
> at org.apache.maven.repository.legacy.LegacyRepositorySystem.resolve
> (LegacyRepositorySystem.java:332)
> at
> org.eclipse.tycho.osgi.configuration.MavenDependenciesResolverConfigurer.resolve
>
[jira] [Comment Edited] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694133#comment-17694133
]
Michael Osipov edited comment on MNG-7705 at 2/27/23 6:55 PM:
--
The attached logfile is from Bamboo, not strace. You need to strart Maven with
strace and trace forks as well as a highres timer. I will see all system call
like fopen, etc. which will help to understand the cause here.
If you aren't familiar with strace, please read:
https://www.howtoforge.com/linux-strace-command/
was (Author: michael-o):
The attached logfile is from Bamboo, not strace. You need to strart Maven with
strace and trace forks as well as a highres timer. I will see all system call
like fopen, etc. which will help to understand the cause here.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
>
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694133#comment-17694133
]
Michael Osipov commented on MNG-7705:
-
The attached logfile is from Bamboo, not strace. You need to strart Maven with
strace and trace forks as well as a highres timer. I will see all system call
like fopen, etc. which will help to understand the cause here.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
>
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694131#comment-17694131
]
Michael Osipov commented on MNG-7705:
-
Thanks Jim, as expected that patch does not yield success, granted. I will take
a look at our code again and your trace file. Thanks!
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
>
[jira] [Comment Edited] (MNG-7713) Drop option legacy-local-repository
[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694070#comment-17694070 ] Michael Osipov edited comment on MNG-7713 at 2/27/23 6:48 PM: -- This is wrong in a patch version. Drop in 4 and warn in 3.9. was (Author: michael-o): This is wrong is a patch version. Drop in 4 and warn in 3.9. > Drop option legacy-local-repository > --- > > Key: MNG-7713 > URL: https://issues.apache.org/jira/browse/MNG-7713 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.1-candidate > > > The option offers several ways to make Maven 3 use Maven 2 legacy local > repository, the option help text states: "Use Maven 2 Legacy Local Repository > behaviour, ie no use of _remote.repositories. Can also be activated by using > -Dmaven.legacyLocalRepo=true". > Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 > local repository, that is (should be) transient anyway. Also, if really > needed, there IS a resolver configuration that offers somewhat similar > semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7712) Core should issue a warning if plugin depends on maven-compat
[ https://issues.apache.org/jira/browse/MNG-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694130#comment-17694130 ] Michael Osipov commented on MNG-7712: - Makes sense. > Core should issue a warning if plugin depends on maven-compat > - > > Key: MNG-7712 > URL: https://issues.apache.org/jira/browse/MNG-7712 > Project: Maven > Issue Type: Improvement > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.2 > > > If a plugin explicitly depends on maven-compat (non test scope), it means we > deal with a legacy plugin. Core should warn about this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-invoker-plugin] slawekjaranowski opened a new pull request, #177: [MINVOKER-328] Skip install artifacts with the same source and target path
slawekjaranowski opened a new pull request, #177: URL: https://github.com/apache/maven-invoker-plugin/pull/177 When user not specified localRepositoryPath we can not reinstall artifact with the same source and target path --- 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/MINVOKER) 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 `[MINVOKER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MINVOKER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). 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. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] slachiewicz merged pull request #182: Bump apache/maven-gh-actions-shared from 2 to 3
slachiewicz merged PR #182: URL: https://github.com/apache/maven-compiler-plugin/pull/182 -- 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-325) [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
[
https://issues.apache.org/jira/browse/MRESOLVER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694090#comment-17694090
]
Uwe Schindler commented on MRESOLVER-325:
-
Hi,
the Lucene team knows this issue, but due to our 2-phase-commits we have put a
lot of thought to get the transactional system running correctly. The issue
here is in fact not limited to Windows. When testing on Linux with e.g., the
ext4 filesystem, the underlying problem is not necesarily showing up, because
ext4 has a workaround for badly written appplications. Of course on Linux you
won't get an AccessDeniedException as Linux can overwrite files that are
currently open or in use.
https://www.kernel.org/doc/Documentation/filesystems/ext4.txt
{quote}
auto_da_alloc: Many broken applications don’t use fsync() when replacing
existing files via patterns such as fd =
open(“foo.new”)/write(fd,..)/close(fd)/ rename(“foo.new”, “foo”), or worse yet,
fd = open(“foo”, O_TRUNC)/write(fd,..)/close(fd). If auto_da_alloc is enabled,
ext4 will detect the replace-via-rename and replace-via-truncate patterns and
force that any delayed allocation blocks are allocated such that at the next
journal commit, in the default data=ordered mode, the data blocks of the new
file are forced to disk before the rename() operation is committed. This
provides roughly the same level of guarantees as ext3, and avoids the
“zero-length” problem that can happen when a system crashes before the delayed
allocation blocks are forced to disk.
{quote}
So the correct way how to do this type of stuff is to fsync the newly created
file and after that rename it.
> [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
>
>
> Key: MRESOLVER-325
> URL: https://issues.apache.org/jira/browse/MRESOLVER-325
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.9.4
>Reporter: Christoph Läubrich
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> If one runs a build that otherwise works fine on 3.8.x with 3.9 we now get
> the following exception (full output can be found here
> https://github.com/eclipse-platform/eclipse.platform/actions/runs/4211467991/jobs/7309831666):
> {code:java}
> Error: 5.889 [ERROR] Internal error: java.io.UncheckedIOException:
> java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:108)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:821)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:270)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:121)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addRepo
> (EnhancedLocalRepositoryManager.java:274)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addArtifact
> (EnhancedLocalRepositoryManager.java:252)
> at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.add
> (EnhancedLocalRepositoryManager.java:225)
> at
>
[jira] [Commented] (MNG-7713) Drop option legacy-local-repository
[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694070#comment-17694070 ] Michael Osipov commented on MNG-7713: - This is wrong is a patch version. Drop in 4 and warn in 3.9. > Drop option legacy-local-repository > --- > > Key: MNG-7713 > URL: https://issues.apache.org/jira/browse/MNG-7713 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.1-candidate > > > The option offers several ways to make Maven 3 use Maven 2 legacy local > repository, the option help text states: "Use Maven 2 Legacy Local Repository > behaviour, ie no use of _remote.repositories. Can also be activated by using > -Dmaven.legacyLocalRepo=true". > Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 > local repository, that is (should be) transient anyway. Also, if really > needed, there IS a resolver configuration that offers somewhat similar > semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-compiler-plugin] slachiewicz merged pull request #179: Bump maven-invoker-plugin from 3.4.0 to 3.5.0
slachiewicz merged PR #179: URL: https://github.com/apache/maven-compiler-plugin/pull/179 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-compiler-plugin] dependabot[bot] opened a new pull request, #182: Bump apache/maven-gh-actions-shared from 2 to 3
dependabot[bot] opened a new pull request, #182: URL: https://github.com/apache/maven-compiler-plugin/pull/182 Bumps [apache/maven-gh-actions-shared](https://github.com/apache/maven-gh-actions-shared) from 2 to 3. Commits See full diff in https://github.com/apache/maven-gh-actions-shared/commits/v3;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-327) Make tranport-http obey system properties regarding proxy settings
[ https://issues.apache.org/jira/browse/MRESOLVER-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694059#comment-17694059 ] Tamas Cservenak commented on MRESOLVER-327: --- IMHO, for sure not system properties. Maybe repository system session config properties, but still, it would require code to support that... > Make tranport-http obey system properties regarding proxy settings > -- > > Key: MRESOLVER-327 > URL: https://issues.apache.org/jira/browse/MRESOLVER-327 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 1.9.6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7713) Drop option legacy-local-repository
[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7713: - Component/s: Core > Drop option legacy-local-repository > --- > > Key: MNG-7713 > URL: https://issues.apache.org/jira/browse/MNG-7713 > Project: Maven > Issue Type: Task > Components: Core >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.1-candidate > > > The option offers several ways to make Maven 3 use Maven 2 legacy local > repository, the option help text states: "Use Maven 2 Legacy Local Repository > behaviour, ie no use of _remote.repositories. Can also be activated by using > -Dmaven.legacyLocalRepo=true". > Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 > local repository, that is (should be) transient anyway. Also, if really > needed, there IS a resolver configuration that offers somewhat similar > semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694053#comment-17694053
]
Jim Sellers commented on MNG-7705:
--
Attached the log. Sorry I didn't see your earlier comment.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
> at
>
[jira] [Updated] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Sellers updated MNG-7705:
-
Attachment: MNG-7705-2023-02-27.zip
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705-2023-02-27.zip, MNG-7705.zip,
> apache-maven-3.9.1-SNAPSHOT-bin.tar.gz, maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
> at
> org.apache.maven.plugins.dependency.resolvers.ResolveDependenciesMojo.doExecute
> (ResolveDependenciesMojo.java:103)
> at
[jira] [Assigned] (MNG-7713) Drop option legacy-local-repository
[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-7713: Assignee: Tamas Cservenak > Drop option legacy-local-repository > --- > > Key: MNG-7713 > URL: https://issues.apache.org/jira/browse/MNG-7713 > Project: Maven > Issue Type: Task >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.1-candidate > > > The option offers several ways to make Maven 3 use Maven 2 legacy local > repository, the option help text states: "Use Maven 2 Legacy Local Repository > behaviour, ie no use of _remote.repositories. Can also be activated by using > -Dmaven.legacyLocalRepo=true". > Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 > local repository, that is (should be) transient anyway. Also, if really > needed, there IS a resolver configuration that offers somewhat similar > semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCOMPILER-525) Incremental recompile incorrect detection of dependency change
[ https://issues.apache.org/jira/browse/MCOMPILER-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Solórzano updated MCOMPILER-525: -- Affects Version/s: 3.10.0 3.9.0 3.8.1 > Incremental recompile incorrect detection of dependency change > -- > > Key: MCOMPILER-525 > URL: https://issues.apache.org/jira/browse/MCOMPILER-525 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.1, 3.9.0, 3.10.0, 3.10.1 >Reporter: Jorge Solórzano >Assignee: Guillaume Nodet >Priority: Major > Fix For: 3.11.0 > > > I have just hit an issue running the ITs of maven-jar-plugin, specifically > the *MJAR-70-no-recreation* test on Maven 3.9.0-SNAPSHOT. > Trying to debug the issue I just found out that the issue is not related to > Maven 3.9.0-SNAPSHOT but the real issue seems related to the > maven-compiler-plugin used by default on that version. > maven-compiler-plugins tries to detect changes on incremental compilation > running *isDependencyChanged()* which in turn executes *hasNewFile()* but > during the same run of maven, if the compile phase is run twice it would not > detect correctly that nothing has changed since is just evaluating the file > time of the class but the class ends up being newer than the buildStartTime, > so this causes the recompilation. > My proposal is to add a step to set the last modification time if the > incremental compilation is enabled and that way it will use the exact same > time than the buildStartTime() from maven. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-antrun-plugin] dependabot[bot] closed pull request #75: Bump maven-plugin-plugin from 3.6.4 to 3.7.1
dependabot[bot] closed pull request #75: Bump maven-plugin-plugin from 3.6.4 to 3.7.1 URL: https://github.com/apache/maven-antrun-plugin/pull/75 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] commented on pull request #75: Bump maven-plugin-plugin from 3.6.4 to 3.7.1
dependabot[bot] commented on PR #75: URL: https://github.com/apache/maven-antrun-plugin/pull/75#issuecomment-1446367712 Superseded by #77. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-antrun-plugin] dependabot[bot] opened a new pull request, #77: Bump maven-plugin-plugin from 3.6.4 to 3.8.1
dependabot[bot] opened a new pull request, #77: URL: https://github.com/apache/maven-antrun-plugin/pull/77 Bumps [maven-plugin-plugin](https://github.com/apache/maven-plugin-tools) from 3.6.4 to 3.8.1. Release notes Sourced from https://github.com/apache/maven-plugin-tools/releases;>maven-plugin-plugin's releases. 3.7.1 3.7.0 Bug [https://issues.apache.org/jira/browse/MPLUGIN-298;>MPLUGIN-298] - The plugin descriptor generated by plugin:descriptor does not consider @ see javadoc taglets [https://issues.apache.org/jira/browse/MPLUGIN-394;>MPLUGIN-394] - Report-Mojo doesn't respect input encoding [https://issues.apache.org/jira/browse/MPLUGIN-403;>MPLUGIN-403] - Generating site reports for plugin results in NoSuchMethodError [https://issues.apache.org/jira/browse/MPLUGIN-404;>MPLUGIN-404] - JDK Requirements in plugin-info.html: Consider property maven.compiler.release [https://issues.apache.org/jira/browse/MPLUGIN-420;>MPLUGIN-420] - Parameters documentation inheriting @ since from Mojo can be confusing [https://issues.apache.org/jira/browse/MPLUGIN-428;>MPLUGIN-428] - Don't emit warning for missing javadoc URL of primitives [https://issues.apache.org/jira/browse/MPLUGIN-429;>MPLUGIN-429] - Don't emit warning for missing javadoc URI if no javadoc sources are configured [https://issues.apache.org/jira/browse/MPLUGIN-438;>MPLUGIN-438] - Parameter description should be taken from annotated item New Feature [https://issues.apache.org/jira/browse/MPLUGIN-9;>MPLUGIN-9] - Add link to javadoc in configuration description page for user defined types of Mojos. [https://issues.apache.org/jira/browse/MPLUGIN-396;>MPLUGIN-396] - Allow only @ Deprecated annotation without @ deprecated javadoc tag [https://issues.apache.org/jira/browse/MPLUGIN-400;>MPLUGIN-400] - add system requirements history section [https://issues.apache.org/jira/browse/MPLUGIN-402;>MPLUGIN-402] - report: allow to generate usage section in plugin-info.html with true [https://issues.apache.org/jira/browse/MPLUGIN-419;>MPLUGIN-419] - Allow @ Parameter on setters methods [https://issues.apache.org/jira/browse/MPLUGIN-423;>MPLUGIN-423] - Extract plugin report into its own plugin [https://issues.apache.org/jira/browse/MPLUGIN-427;>MPLUGIN-427] - report: Expose generics information of Collection and Map types Improvement [https://issues.apache.org/jira/browse/MPLUGIN-297;>MPLUGIN-297] - plugin-info.html should contain a better Usage section [https://issues.apache.org/jira/browse/MPLUGIN-390;>MPLUGIN-390] - Do not overwrite generate files with no content change [https://issues.apache.org/jira/browse/MPLUGIN-393;>MPLUGIN-393] - Upgrade to JUnit 5 and @ Inject annotations [https://issues.apache.org/jira/browse/MPLUGIN-398;>MPLUGIN-398] - Support for java 20 - ASM 9.4 [https://issues.apache.org/jira/browse/MPLUGIN-405;>MPLUGIN-405] - Don't print empty Memory, Disk Space in System Requirements [https://issues.apache.org/jira/browse/MPLUGIN-408;>MPLUGIN-408] - simplification in helpmojo build [https://issues.apache.org/jira/browse/MPLUGIN-411;>MPLUGIN-411] - Get rid of plexus-compiler-manager from tests [https://issues.apache.org/jira/browse/MPLUGIN-412;>MPLUGIN-412] - Use Maven core artifacts in provided scope [https://issues.apache.org/jira/browse/MPLUGIN-417;>MPLUGIN-417] - report and descriptor goal need to evaluate Javadoc comments differently [https://issues.apache.org/jira/browse/MPLUGIN-433;>MPLUGIN-433] - Allow to reference aggregator javadoc from plugin report Task ... (truncated) Commits https://github.com/apache/maven-plugin-tools/commit/b242658bf0b3abbc9758cfe61e669d0e77037946;>b242658 [maven-release-plugin] prepare release maven-plugin-tools-3.8.1 https://github.com/apache/maven-plugin-tools/commit/2721944828592167a714bec304e8f368f6c87daf;>2721944 Revert Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/1;>#1... https://github.com/apache/maven-plugin-tools/commit/d99a455f772c1728efb732795fe06e5d2d34ecc1;>d99a455 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-plugin-tools/commit/9ca8a18dbb47c9f7e7450a85353316c6c51882e4;>9ca8a18 [maven-release-plugin] prepare release maven-plugin-tools-3.8.0 https://github.com/apache/maven-plugin-tools/commit/84f9a2e7b23aae884c5214564adb8c4759b0776f;>84f9a2e [MPLUGIN-455] Bump plexus-archiver from 4.5.0 to 4.6.1 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/189;>#189) https://github.com/apache/maven-plugin-tools/commit/df4b8fdaf719daed8b060ee161cd60f49761783c;>df4b8fd Bump plexus-velocity from 1.2 to 2.0 and velocity from 1.7 to 2.3 (https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/195;>#195)
[GitHub] [maven] cstamas opened a new pull request, #1018: [MNH-7713] Drop legacy-local-repository option
cstamas opened a new pull request, #1018: URL: https://github.com/apache/maven/pull/1018 There is really no need for it, and there is a resolver option if really must (but really should not, local repo is and should be considered as transient). --- https://issues.apache.org/jira/browse/MNG-7713 -- 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-7713) Drop option legacy-local-repository
Tamas Cservenak created MNG-7713: Summary: Drop option legacy-local-repository Key: MNG-7713 URL: https://issues.apache.org/jira/browse/MNG-7713 Project: Maven Issue Type: Task Reporter: Tamas Cservenak Fix For: 3.9.1-candidate The option offers several ways to make Maven 3 use Maven 2 legacy local repository, the option help text states: "Use Maven 2 Legacy Local Repository behaviour, ie no use of _remote.repositories. Can also be activated by using -Dmaven.legacyLocalRepo=true". Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 local repository, that is (should be) transient anyway. Also, if really needed, there IS a resolver configuration that offers somewhat similar semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694022#comment-17694022
]
Jim Sellers commented on MNG-7705:
--
[~michael-o] I can still reproduce the error with that snapshot build. It
always seems to be on the {{.lastUpdated}} files. Sometimes on pom's, sometimes
on other artifacts like the javadocs.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705.zip, apache-maven-3.9.1-SNAPSHOT-bin.tar.gz,
> maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
>
[GitHub] [maven-dist-tool] dependabot[bot] closed pull request #23: Bump github-api from 1.129 to 1.313
dependabot[bot] closed pull request #23: Bump github-api from 1.129 to 1.313 URL: https://github.com/apache/maven-dist-tool/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dist-tool] dependabot[bot] commented on pull request #23: Bump github-api from 1.129 to 1.313
dependabot[bot] commented on PR #23: URL: https://github.com/apache/maven-dist-tool/pull/23#issuecomment-1446280837 Superseded by #27. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-dist-tool] dependabot[bot] opened a new pull request, #27: Bump github-api from 1.129 to 1.314
dependabot[bot] opened a new pull request, #27: URL: https://github.com/apache/maven-dist-tool/pull/27 Bumps [github-api](https://github.com/hub4j/github-api) from 1.129 to 1.314. Release notes Sourced from https://github.com/hub4j/github-api/releases;>github-api's releases. v1.314 Changes added fields in GHPullRequestReviewComment which were missing https://github.com/kisaga;>@kisaga (https://github-redirect.dependabot.com/hub4j/github-api/issues/1469;>#1469) Issue 1597: Tested and implemented GHRepository.listCodeownersErrors() https://github.com/michael-s-grant;>@michael-s-grant (https://github-redirect.dependabot.com/hub4j/github-api/issues/1610;>#1610) Adding Star/Unstar Methods https://github.com/antrix190;>@antrix190 (https://github-redirect.dependabot.com/hub4j/github-api/issues/1372;>#1372) Improve deploy key and user key handling https://github.com/van-vliet;>@van-vliet (https://github-redirect.dependabot.com/hub4j/github-api/issues/1616;>#1616) ci: use Eclipse Temurin https://github.com/yeikel;>@yeikel (https://github-redirect.dependabot.com/hub4j/github-api/issues/1617;>#1617) Chore(deps): Bump maven-project-info-reports-plugin from 3.4.1 to 3.4.2 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1609;>#1609) Filter check runs to retrieve from commit https://github.com/alecharp;>@alecharp (https://github-redirect.dependabot.com/hub4j/github-api/issues/1612;>#1612) Chore(deps-dev): Bump commons-fileupload from 1.4 to 1.5 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1619;>#1619) Incorrect project version downgrade https://github.com/alecharp;>@alecharp (https://github-redirect.dependabot.com/hub4j/github-api/issues/1611;>#1611) Issue https://github-redirect.dependabot.com/hub4j/github-api/issues/1597;>#1597: Add deliberately broken CODEOWNERS file https://github.com/michael-s-grant;>@michael-s-grant (https://github-redirect.dependabot.com/hub4j/github-api/issues/1604;>#1604) Chore(deps-dev): Bump wiremock-jre8-standalone from 2.32.0 to 2.35.0 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1563;>#1563) fixed flaky test in GHObjectTest https://github.com/ycliu28;>@ycliu28 (https://github-redirect.dependabot.com/hub4j/github-api/issues/1576;>#1576) Spelling https://github.com/bitwiseman;>@bitwiseman (https://github-redirect.dependabot.com/hub4j/github-api/issues/1603;>#1603) Update link to GitHub conditional requests doc https://github.com/jjlharrison;>@jjlharrison (https://github-redirect.dependabot.com/hub4j/github-api/issues/1601;>#1601) Add logs in GitHubClient response. fixes https://github-redirect.dependabot.com/hub4j/github-api/issues/1594;>#1594 https://github.com/c3p0-maif;>@c3p0-maif (https://github-redirect.dependabot.com/hub4j/github-api/issues/1599;>#1599) Chore(deps): Bump spotbugs-maven-plugin from 4.7.1.1 to 4.7.3.0 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1590;>#1590) Chore(deps-dev): Bump mockito-core from 4.8.0 to 4.11.0 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1589;>#1589) feat: Add head_commit to GHEventPayload.Push https://github.com/rahulsom;>@rahulsom (https://github-redirect.dependabot.com/hub4j/github-api/issues/1586;>#1586) Chore(deps-dev): Bump org.eclipse.jgit from 6.3.0.2022009070944-r to 6.4.0.202211300538-r https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1574;>#1574) Chore(deps-dev): Bump gson from 2.9.1 to 2.10 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1571;>#1571) Chore(deps): Bump spotbugs.version from 4.7.2 to 4.7.3 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1565;>#1565) Chore(deps): Bump jackson-databind from 2.13.4.2 to 2.14.0 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1566;>#1566) Add outside_collaborators list https://github.com/Diegunix;>@Diegunix (https://github-redirect.dependabot.com/hub4j/github-api/issues/1561;>#1561) Chore(deps-dev): Bump org.eclipse.jgit from 6.1.0.202203080745-r to 6.3.0.2022009070944-r https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1554;>#1554) Chore(deps): Bump bcel from 6.5.0 to 6.6.1 https://github.com/dependabot;>@dependabot (https://github-redirect.dependabot.com/hub4j/github-api/issues/1562;>#1562) Chore(deps): Bump jackson-databind from 2.13.3 to 2.13.4.2 https://github.com/dependabot;>@dependabot
[GitHub] [maven] elharo merged pull request #1017: Simplify code with try with resources
elharo merged PR #1017: URL: https://github.com/apache/maven/pull/1017 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven] elharo commented on pull request #1016: remove unused code
elharo commented on PR #1016: URL: https://github.com/apache/maven/pull/1016#issuecomment-1446254347 It all moves to JDK classes when possible, and Apache commons when not so there's no intermediate step. This is true whether it's maven-shared-utils or plexus utils. I have already deprecated a lot of the functionality in maven-shared-utils so I hope that pokes a few projects to update themselves without me having to do the work piecemeal. -- 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-329) Make IO in DefaultTrackingFileManager more robust
[ https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693990#comment-17693990 ] ASF GitHub Bot commented on MRESOLVER-329: -- michael-o commented on PR #260: URL: https://github.com/apache/maven-resolver/pull/260#issuecomment-1446227239 Before we merge this, I'd like to see Jim's data first. > Make IO in DefaultTrackingFileManager more robust > - > > Key: MRESOLVER-329 > URL: https://issues.apache.org/jira/browse/MRESOLVER-329 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.6 > > > There are couple of spots where implementation naively assumes is alone > running process on this world. Several user reports suggests this is not the > case, like MRESOLVER-325 or MNG-7705. Fix these spots. > Still, something is fishy, as it seems these files (all that are handled by > DefaultTrackingFileManager) are not subject to locking? This needs > investigation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-resolver] michael-o commented on pull request #260: [MRESOLVER-329] More robust IO in default tracking file manager
michael-o commented on PR #260: URL: https://github.com/apache/maven-resolver/pull/260#issuecomment-1446227239 Before we merge this, I'd like to see Jim's data first. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-pmd-plugin] dependabot[bot] opened a new pull request, #115: Bump pmdVersion from 6.54.0 to 6.55.0
dependabot[bot] opened a new pull request, #115: URL: https://github.com/apache/maven-pmd-plugin/pull/115 Bumps `pmdVersion` from 6.54.0 to 6.55.0. Updates `pmd-core` from 6.54.0 to 6.55.0 Release notes Sourced from https://github.com/pmd/pmd/releases;>pmd-core's releases. PMD 6.55.0 (25-February-2023) 25-February-2023 - 6.55.0 The PMD team is pleased to announce PMD 6.55.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/#pmd-7-development;>PMD 7 Development https://github.com/pmd/pmd/blob/HEAD/#java-20-support;>Java 20 Support https://github.com/pmd/pmd/blob/HEAD/#t-sql-support;>T-SQL support 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/#go;>Go https://github.com/pmd/pmd/blob/HEAD/#java;>Java https://github.com/pmd/pmd/blob/HEAD/#external-contributions;>External Contributions https://github.com/pmd/pmd/blob/HEAD/#stats;>Stats New and noteworthy PMD 7 Development This release is the last planned release of PMD 6. The first version 6.0.0 was released in December 2017. Over the course of more than 5 years we published almost every month a new minor version of PMD 6 with new features and improvements. Already in November 2018 we started in parallel the development of the next major version 7.0.0, and we are now in the process of finalizing the scope of the major version. We want to release a couple of release candidates before publishing the final version 7.0.0. We plan to release 7.0.0-rc1 soon. You can see the progress in [PMD 7 Tracking Issue https://github-redirect.dependabot.com/pmd/pmd/issues/3898;>#3898](https://github-redirect.dependabot.com/pmd/pmd/issues/3898;>pmd/pmd#3898). Java 20 Support This release of PMD brings support for Java 20. There are no new standard language features. PMD supports https://openjdk.org/jeps/433;>JEP 433: Pattern Matching for switch (Fourth Preview) and https://openjdk.org/jeps/432;>JEP 432: Record Patterns (Second Preview) as preview language features. In order to analyze a project with PMD that uses these language features, you'll need to enable it via the environment variable PMD_JAVA_OPTS and select the new language version 20-preview: export PMD_JAVA_OPTS=--enable-preview ./run.sh pmd --use-version java-20-preview ... T-SQL support Thanks to the contribution from https://github.com/pguyot;>Paul Guyot PMD now has CPD support for T-SQL (Transact-SQL). ... (truncated) Commits https://github.com/pmd/pmd/commit/ef3455348603aa25f86894b9930f05f141f44d20;>ef34553 [maven-release-plugin] prepare release pmd_releases/6.55.0 https://github.com/pmd/pmd/commit/b491afc628ec9c1c67f5f4825b95ea2290d82ca3;>b491afc Prepare pmd release 6.55.0 https://github.com/pmd/pmd/commit/1abf8e063abf49406846655a3a1e1e70f7f9eaaf;>1abf8e0 Merge pull request https://github-redirect.dependabot.com/pmd/pmd/issues/4407;>#4407 from adangel:pmd6-release-notes-6.55.0 https://github.com/pmd/pmd/commit/8bdfc9538bbc01a120e195e8007240ca4221970d;>8bdfc95 Merge pull request https://github-redirect.dependabot.com/pmd/pmd/issues/4377;>#4377 from adangel:pmd6-java-20 https://github.com/pmd/pmd/commit/2db72550353cb39fa4f1fc35348de7b92a1b11bc;>2db7255 Merge pull request https://github-redirect.dependabot.com/pmd/pmd/issues/4395;>#4395 from adangel:pmd6-support-env-CLASSPATH https://github.com/pmd/pmd/commit/794263c463e86df5b2e9462989554c5739ac23e4;>794263c [doc] Update release notes - last pmd6 release, pmd7 development https://github.com/pmd/pmd/commit/67c8daaf25a151d9cc6508c030e8132efbf86dc6;>67c8daa Merge pull request https://github-redirect.dependabot.com/pmd/pmd/issues/4398;>#4398 from adangel/pmd6-cpd-usage-text https://github.com/pmd/pmd/commit/17364a997b1ff135cb48dc412a797286bb0025fe;>17364a9 [doc] CPD - use non deprecated --dir cli option https://github.com/pmd/pmd/commit/a74bf9665fe9af5efabb43677560725016325179;>a74bf96 [doc] Update gitter urls, update codacy badge https://github.com/pmd/pmd/commit/af6d502afbd0c954c525cfba02315a93e45baeb5;>af6d502 Merge pull request https://github-redirect.dependabot.com/pmd/pmd/issues/4390;>#4390 from pguyot:w06/add_support_for_tsql Additional commits viewable in https://github.com/pmd/pmd/compare/pmd_releases/6.54.0...pmd_releases/6.55.0;>compare view Updates `pmd-java` from 6.54.0 to 6.55.0 Release notes Sourced from https://github.com/pmd/pmd/releases;>pmd-java's releases. PMD 6.55.0 (25-February-2023) 25-February-2023 - 6.55.0 The PMD team is pleased to announce PMD 6.55.0. This is a minor release. Table Of Contents
[GitHub] [maven-resolver] laeubi closed pull request #252: Be more graceful when updating the index file
laeubi closed pull request #252: Be more graceful when updating the index file URL: https://github.com/apache/maven-resolver/pull/252 -- 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-329) Make IO in DefaultTrackingFileManager more robust
[ https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693978#comment-17693978 ] ASF GitHub Bot commented on MRESOLVER-329: -- cstamas commented on PR #257: URL: https://github.com/apache/maven-resolver/pull/257#issuecomment-1446192026 Superseded by https://github.com/apache/maven-resolver/pull/260 > Make IO in DefaultTrackingFileManager more robust > - > > Key: MRESOLVER-329 > URL: https://issues.apache.org/jira/browse/MRESOLVER-329 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.6 > > > There are couple of spots where implementation naively assumes is alone > running process on this world. Several user reports suggests this is not the > case, like MRESOLVER-325 or MNG-7705. Fix these spots. > Still, something is fishy, as it seems these files (all that are handled by > DefaultTrackingFileManager) are not subject to locking? This needs > investigation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-329) Make IO in DefaultTrackingFileManager more robust
[ https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693979#comment-17693979 ] ASF GitHub Bot commented on MRESOLVER-329: -- cstamas closed pull request #257: [MRESOLVER-329] More robust IO in DefaultTrackingFileManager URL: https://github.com/apache/maven-resolver/pull/257 > Make IO in DefaultTrackingFileManager more robust > - > > Key: MRESOLVER-329 > URL: https://issues.apache.org/jira/browse/MRESOLVER-329 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.6 > > > There are couple of spots where implementation naively assumes is alone > running process on this world. Several user reports suggests this is not the > case, like MRESOLVER-325 or MNG-7705. Fix these spots. > Still, something is fishy, as it seems these files (all that are handled by > DefaultTrackingFileManager) are not subject to locking? This needs > investigation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-329) Make IO in DefaultTrackingFileManager more robust
[ https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693977#comment-17693977 ] ASF GitHub Bot commented on MRESOLVER-329: -- cstamas opened a new pull request, #260: URL: https://github.com/apache/maven-resolver/pull/260 In case of concurrent r/w of tracking file, the if Files.isReablable may return true, but the file might be gone once it arrives to Files.newInputStream. In these cases, just ignore the missing file related exception. --- https://issues.apache.org/jira/browse/MRESOLVER-329 > Make IO in DefaultTrackingFileManager more robust > - > > Key: MRESOLVER-329 > URL: https://issues.apache.org/jira/browse/MRESOLVER-329 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.6 > > > There are couple of spots where implementation naively assumes is alone > running process on this world. Several user reports suggests this is not the > case, like MRESOLVER-325 or MNG-7705. Fix these spots. > Still, something is fishy, as it seems these files (all that are handled by > DefaultTrackingFileManager) are not subject to locking? This needs > investigation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-resolver] cstamas closed pull request #257: [MRESOLVER-329] More robust IO in DefaultTrackingFileManager
cstamas closed pull request #257: [MRESOLVER-329] More robust IO in DefaultTrackingFileManager URL: https://github.com/apache/maven-resolver/pull/257 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-resolver] cstamas commented on pull request #257: [MRESOLVER-329] More robust IO in DefaultTrackingFileManager
cstamas commented on PR #257: URL: https://github.com/apache/maven-resolver/pull/257#issuecomment-1446192026 Superseded by https://github.com/apache/maven-resolver/pull/260 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-resolver] cstamas opened a new pull request, #260: [MRESOLVER-329] More robust IO in default tracking file manager
cstamas opened a new pull request, #260: URL: https://github.com/apache/maven-resolver/pull/260 In case of concurrent r/w of tracking file, the if Files.isReablable may return true, but the file might be gone once it arrives to Files.newInputStream. In these cases, just ignore the missing file related exception. --- https://issues.apache.org/jira/browse/MRESOLVER-329 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-shade-plugin] slachiewicz merged pull request #173: Bump xmlunit-legacy from 2.9.0 to 2.9.1
slachiewicz merged PR #173: URL: https://github.com/apache/maven-shade-plugin/pull/173 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-install-plugin] dependabot[bot] commented on pull request #55: Bump maven-plugins from 37 to 39
dependabot[bot] commented on PR #55: URL: https://github.com/apache/maven-install-plugin/pull/55#issuecomment-1446043259 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
[GitHub] [maven-install-plugin] gnodet closed pull request #55: Bump maven-plugins from 37 to 39
gnodet closed pull request #55: Bump maven-plugins from 37 to 39 URL: https://github.com/apache/maven-install-plugin/pull/55 -- 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] [Comment Edited] (MJAVADOC-745) Taglet auto-detection doesn't support transitive dependencies
[
https://issues.apache.org/jira/browse/MJAVADOC-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693825#comment-17693825
]
Stefano Chizzolini edited comment on MJAVADOC-745 at 2/27/23 9:58 AM:
--
For the purpose, I prepared a fix proposal (see
[fix-taglet-autodetect|https://github.com/stechio/maven-javadoc-plugin/tree/fix-taglet-autodetect]
branch — because of a regression affecting dependency resolution on current
master HEAD (see MJAVADOC-742), I had to temporarily create my branch from the
last functioning version (3.4.1); when that regression is solved, I will move
my changes to a proper PR branch from master).
My proposal replaces the old taglet auto-detection algorithm with an invocation
to a robust classpath scanner
([classgraph|https://github.com/classgraph/classgraph]) — I'm not aware if
Apache already has its own preferred classpath scanner, neither am I aware
which Apache policies apply to the addition of new dependencies (I'm looking
forward to your feedback, thanks).
My branch includes a new unit test ({{{}tagletArtifacts-jdk9-test{}}}) and has
been successfully verified before commit ({{{}mvn -P run-its verify{}}}).
was (Author: JIRAUSER299015):
For the purpose, I prepared a fix proposal (see
[fix-taglet-autodetect|https://github.com/stechio/maven-javadoc-plugin/tree/fix-taglet-autodetect]
branch — because of a regression affecting dependency resolution on current
master HEAD (see MJAVADOC-742), I had to temporarily create my branch from the
last functioning version (3.4.1); when that regression is solved, I will move
my changes to a proper PR branch from master).
My proposal overcomes the severe limitation on topic, replacing the old taglet
auto-detection algorithm with an invocation to a robust classpath scanner
([classgraph|https://github.com/classgraph/classgraph]) — I'm not aware if
Apache already has its own preferred classpath scanner, neither am I aware
which Apache policies apply to the addition of new dependencies (I'm looking
forward to your feedback, thanks).
My branch includes a new unit test ({{{}tagletArtifacts-jdk9-test{}}}) and has
been successfully verified before commit ({{{}mvn -P run-its verify{}}}).
> Taglet auto-detection doesn't support transitive dependencies
> -
>
> Key: MJAVADOC-745
> URL: https://issues.apache.org/jira/browse/MJAVADOC-745
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.4.1
>Reporter: Stefano Chizzolini
>Priority: Major
>
> The current implementation of the taglet auto-detection algorithm (initial
> feature request: MJAVADOC-204) doesn't honor the transitive dependency
> resolution of the configured taglet artifacts (see
> [|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#tagletArtifacts]):
> _each artifact on the taglet classpath is scanned separately_ (see
> [AbstractJavadocMojo.addTagletsFromTagletArtifacts(..)|https://github.com/apache/maven-javadoc-plugin/blob/a5db96e7e16cc432d8fdea05f460f6c3fa258ba9/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L5901]
> and
> [JavadocUtil.getTagletClassNames(..)|https://github.com/apache/maven-javadoc-plugin/blob/a5db96e7e16cc432d8fdea05f460f6c3fa258ba9/src/main/java/org/apache/maven/plugins/javadoc/JavadocUtil.java#L721]),
> _causing taglet class loading to fail in case its hierarchy is spread across
> multiple artifacts_ (its class loader has visibility only on a single
> artifact at a time, in the wrong assumption that no intermediate artifact
> lies between the Taglet interface and its implementations).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-742) [REGRESSION] Transitive dependencies of docletArtifact missing
[ https://issues.apache.org/jira/browse/MJAVADOC-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693907#comment-17693907 ] Tamas Cservenak commented on MJAVADOC-742: -- Unsure about NPE, but this PR fixes doclet resolution https://github.com/apache/maven-javadoc-plugin/pull/186 > [REGRESSION] Transitive dependencies of docletArtifact missing > -- > > Key: MJAVADOC-742 > URL: https://issues.apache.org/jira/browse/MJAVADOC-742 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: javadoc >Affects Versions: 3.5.0 >Reporter: Patrick Ruckstuhl >Priority: Blocker > Fix For: 3.5.1 > > > It looks like with 3.5.0 transitive dependencies of the docletArtifact are no > longer added to the classpath and generation fails with class not found. > Reverting back to 3.4.1 everything works fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7712) Core should issue a warning if plugin depends on maven-compat
[ https://issues.apache.org/jira/browse/MNG-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693902#comment-17693902 ] Tamas Cservenak commented on MNG-7712: -- No, this is only about Maven Plugins (packaging maven-plugin) and the fact their POM contains dependency to maven-compat in non-test scope (so even provided). As it being present, clearly means some Maven2 stuff is being used by plugin. So this is not about "transitive" tree (ie. component that plugin depends on), but the plugin itself declaring direct dependency on it. > Core should issue a warning if plugin depends on maven-compat > - > > Key: MNG-7712 > URL: https://issues.apache.org/jira/browse/MNG-7712 > Project: Maven > Issue Type: Improvement > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.2 > > > If a plugin explicitly depends on maven-compat (non test scope), it means we > deal with a legacy plugin. Core should warn about this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7700) Improper canonicalization of versions
[
https://issues.apache.org/jira/browse/MNG-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693900#comment-17693900
]
Michael Osipov commented on MNG-7700:
-
Guys, it'd be nice if you could settle on this in a week or so, I'd intend to
push 3.8.8 by 2023-03-08.
> Improper canonicalization of versions
> -
>
> Key: MNG-7700
> URL: https://issues.apache.org/jira/browse/MNG-7700
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.8.7, 3.9.0
>Reporter: David M. Lloyd
>Assignee: Elliotte Rusty Harold
>Priority: Minor
> Fix For: 3.8.x-candidate, 3.9.1-candidate, waiting-for-feedback
>
>
> The canonicalization logic for versions is incorrect.
> Using the method {{ComparableVersion#getCanonical}} as in {{new
> ComparableVersion(input).getCanonical()}}, the following results can be
> observed:
> ||Input||3.8.6 Output||3.8.6 OK?||3.9.0 Output||3.9.0 OK?||
> |{{1}}|{{1}}|yes|{{1}}|yes|
> |{{0.1}}|{{0.1}}|yes|{{0.1}}|yes|
> |{{0-1}}|{{1}}|no|{{1}}|no|
> |{{1.x}}|{{1.x}}|yes|{{1-x}}|maybe*|
> |{{1-x}}|{{1-x}}|yes|{{1-x}}|yes|
> |{{0.x}}|{{0.x}}|yes|{{x}}|no|
> |{{0-x}}|{{x}}|no|{{x}}|no|
> |{{x}}|{{x}}|yes|{{x}}|yes|
> |{{0.rc}}|{{0.rc}}|yes|{{rc}}|no|
> The "OK?" columns indicate whether parsing the canonical version string will
> yield a {{ComparableVersion}} instance that is {{equal}} to one constructed
> from the original input, i.e. it's internally consistent.
> The "maybe*" item indicates that starting with 3.9.0, version `1.x` is now
> considered to be equal to `1-x`. I'm not sure if this is a bug or not, or was
> intentional or not, but it is definitely a change.
> These canonicalizations seem to have gotten less consistent in the move to
> 3.9.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7705) Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file
[
https://issues.apache.org/jira/browse/MNG-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693899#comment-17693899
]
Michael Osipov commented on MNG-7705:
-
[~sellersj], please try also provide full strace output of the failing process.
I want to see the system calls and analyze them. Thanks.
> Sporadic failures on multiple builds sharing the same local repo when writing
> the .lastUpdated file
> ---
>
> Key: MNG-7705
> URL: https://issues.apache.org/jira/browse/MNG-7705
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.0
> Environment: Apache Maven 3.9.0
> (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: /data00/bamboo/maven/maven-next
> Java version: 1.8.0_362, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.362.b09-2.el8_7.x86_64/jre
> Default locale: en_CA, platform encoding: ISO-8859-1
> OS name: "linux", version: "4.18.0-193.el8.x86_64", arch: "amd64", family:
> "unix"
>Reporter: Jim Sellers
>Priority: Minor
> Fix For: 3.9.2
>
> Attachments: MNG-7705.zip, apache-maven-3.9.1-SNAPSHOT-bin.tar.gz,
> maven-resolver-util-1.9.6-SNAPSHOT.jar
>
>
> On a CI server, we have multiple builds running on the same host and sharing
> the same repo.
> While testing 3.9.0, I started to see a NIO exception for the
> {{.lastUpdated}} file. This has worked fine for years, all the way up to
> 3.8.7.
> If you re-run the build, it will work. I think that it's just a collision
> between the different processes.
> {code:title=example command}
> mvn --batch-mode dependency:sources dependency:resolve -Dclassifier=javadoc
> # this uses dependency:3.5.0:sources
> {code}
> {code:title=stracktrace}
> [WARNING] Failed to write tracking file
> '/home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated'
> java.nio.file.NoSuchFileException:
> /home/bamboo/.m2/repository/io/smallrye/config/smallrye-config/2.3.0/smallrye-config-2.3.0-javadoc.jar.lastUpdated
> at sun.nio.fs.UnixException.translateToIOException
> (UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException
> (UnixException.java:107)
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel
> (UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel (Files.java:361)
> at java.nio.file.Files.newByteChannel (Files.java:407)
> at java.nio.file.spi.FileSystemProvider.newInputStream
> (FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream (Files.java:152)
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:90)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.write
> (DefaultUpdateCheckManager.java:604)
> at
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.touchArtifact
> (DefaultUpdateCheckManager.java:539)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:701)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:97)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.Maven31ArtifactResolver.resolveArtifact
> (Maven31ArtifactResolver.java:78)
> at
> org.apache.maven.shared.transfer.artifact.resolve.internal.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:70)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.resolve
> (AbstractDependencyFilterMojo.java:464)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies
> (AbstractDependencyFilterMojo.java:408)
> at
> org.apache.maven.plugins.dependency.fromDependencies.AbstractDependencyFilterMojo.getDependencySets
> (AbstractDependencyFilterMojo.java:340)
> at
>
[jira] [Commented] (MNG-7712) Core should issue a warning if plugin depends on maven-compat
[ https://issues.apache.org/jira/browse/MNG-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693896#comment-17693896 ] Michael Osipov commented on MNG-7712: - Many components depend on it. Can all parts of compat replaced? > Core should issue a warning if plugin depends on maven-compat > - > > Key: MNG-7712 > URL: https://issues.apache.org/jira/browse/MNG-7712 > Project: Maven > Issue Type: Improvement > Components: Core >Reporter: Tamas Cservenak >Priority: Major > Fix For: 3.9.2 > > > If a plugin explicitly depends on maven-compat (non test scope), it means we > deal with a legacy plugin. Core should warn about this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-329) Make IO in DefaultTrackingFileManager more robust
[ https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693894#comment-17693894 ] Michael Osipov commented on MRESOLVER-329: -- [~cstamas], any objections to close this out? > Make IO in DefaultTrackingFileManager more robust > - > > Key: MRESOLVER-329 > URL: https://issues.apache.org/jira/browse/MRESOLVER-329 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 1.9.6 > > > There are couple of spots where implementation naively assumes is alone > running process on this world. Several user reports suggests this is not the > case, like MRESOLVER-325 or MNG-7705. Fix these spots. > Still, something is fishy, as it seems these files (all that are handled by > DefaultTrackingFileManager) are not subject to locking? This needs > investigation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-331) Make DefaultTrackingFileManager write directly to tracking files
[
https://issues.apache.org/jira/browse/MRESOLVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693893#comment-17693893
]
Michael Osipov commented on MRESOLVER-331:
--
Issue logged: https://bugs.openjdk.org/browse/JDK-8303225
> Make DefaultTrackingFileManager write directly to tracking files
>
>
> Key: MRESOLVER-331
> URL: https://issues.apache.org/jira/browse/MRESOLVER-331
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Affects Versions: 1.9.5
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> Resolver recently introduced file collocation that is write to an adjecent
> temp file and then atomically move to the target file. It turned out that on
> Windows, when the target file is written with a high frequency the system
> fails to move in time and it causes an {{AccessDeniedException}}, there is no
> known workaround with current Java code.
> Since tracking files are written very often for the same artifact this
> creates a bottleneck. We need to resort to write to the file directly for
> now, although it just affects Windows.
> Pending: Report to the OpenJDK team
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MRESOLVER-325) [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
[
https://issues.apache.org/jira/browse/MRESOLVER-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17693892#comment-17693892
]
Michael Osipov commented on MRESOLVER-325:
--
Issue logged: https://bugs.openjdk.org/browse/JDK-8303225
> [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
>
>
> Key: MRESOLVER-325
> URL: https://issues.apache.org/jira/browse/MRESOLVER-325
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 1.9.4
>Reporter: Christoph Läubrich
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> If one runs a build that otherwise works fine on 3.8.x with 3.9 we now get
> the following exception (full output can be found here
> https://github.com/eclipse-platform/eclipse.platform/actions/runs/4211467991/jobs/7309831666):
> {code:java}
> Error: 5.889 [ERROR] Internal error: java.io.UncheckedIOException:
> java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:108)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:821)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:270)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: java.io.UncheckedIOException: java.nio.file.AccessDeniedException:
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories.15650462061630955031.tmp
> ->
> C:\Users\runneradmin\.m2\repository\com\google\code\gson\gson\2.10.1\_remote.repositories
> at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.update
> (DefaultTrackingFileManager.java:121)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addRepo
> (EnhancedLocalRepositoryManager.java:274)
> at
> org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addArtifact
> (EnhancedLocalRepositoryManager.java:252)
> at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.add
> (EnhancedLocalRepositoryManager.java:225)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads
> (DefaultArtifactResolver.java:680)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads
> (DefaultArtifactResolver.java:592)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:478)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
> (DefaultArtifactResolver.java:278)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
> (DefaultArtifactResolver.java:255)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
> (DefaultRepositorySystem.java:296)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:197)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
> (DefaultArtifactResolver.java:413)
> at org.apache.maven.repository.legacy.LegacyRepositorySystem.resolve
> (LegacyRepositorySystem.java:332)
> at
> org.eclipse.tycho.osgi.configuration.MavenDependenciesResolverConfigurer.resolve
> (MavenDependenciesResolverConfigurer.java:104)
> at org.eclipse.tycho.core.shared.MavenDependenciesResolver.resolve
> (MavenDependenciesResolver.java:60)
> at org.eclipse.tycho.core.resolver.MavenTargetDefinitionContent.
> (MavenTargetDefinitionContent.java:262)
[jira] [Created] (MNG-7712) Core should issue a warning if plugin depends on maven-compat
Tamas Cservenak created MNG-7712: Summary: Core should issue a warning if plugin depends on maven-compat Key: MNG-7712 URL: https://issues.apache.org/jira/browse/MNG-7712 Project: Maven Issue Type: Improvement Components: Core Reporter: Tamas Cservenak Fix For: 3.9.2 If a plugin explicitly depends on maven-compat (non test scope), it means we deal with a legacy plugin. Core should warn about this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [maven-javadoc-plugin] dependabot[bot] commented on pull request #189: Bump wagonVersion from 2.4 to 3.5.3
dependabot[bot] commented on PR #189: URL: https://github.com/apache/maven-javadoc-plugin/pull/189#issuecomment-1445880416 OK, I won't notify you about version 3.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
[GitHub] [maven-javadoc-plugin] dependabot[bot] closed pull request #189: Bump wagonVersion from 2.4 to 3.5.3
dependabot[bot] closed pull request #189: Bump wagonVersion from 2.4 to 3.5.3 URL: https://github.com/apache/maven-javadoc-plugin/pull/189 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-javadoc-plugin] slachiewicz commented on pull request #189: Bump wagonVersion from 2.4 to 3.5.3
slachiewicz commented on PR #189: URL: https://github.com/apache/maven-javadoc-plugin/pull/189#issuecomment-1445880339 @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
[GitHub] [maven-javadoc-plugin] dependabot[bot] commented on pull request #190: Bump mockito-core from 4.4.0 to 5.1.1
dependabot[bot] commented on PR #190: URL: https://github.com/apache/maven-javadoc-plugin/pull/190#issuecomment-1445880115 OK, I won't notify you about version 5.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
[GitHub] [maven-javadoc-plugin] slachiewicz commented on pull request #190: Bump mockito-core from 4.4.0 to 5.1.1
slachiewicz commented on PR #190: URL: https://github.com/apache/maven-javadoc-plugin/pull/190#issuecomment-1445880047 @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
