gnodet opened a new pull request, #2306:
URL: https://github.com/apache/maven-resolver/pull/2306

   ## Summary
   
   Tone down the hard-link fallback log message introduced in #2198: `WARN` → 
`INFO`,
   exception stack trace demoted to `DEBUG`, and the message is emitted **at 
most once
   per local repository path per session** instead of once per `install()` call.
   
   ## Motivation
   
   On setups where the build output tree and `~/.m2` are on different volumes 
(common in
   containers, CI environments with separate mounts, or custom local repo 
paths),
   `Files.createLink` always fails and the installer silently falls back to a 
regular
   copy — which is correct. But the previous `WARN` fired on every install 
invocation,
   producing noise every build when the behaviour is expected and benign.
   
   ## Changes
   
   - **Level** `WARN` → `INFO`. The fallback is not a build problem; `WARN` 
implies
     something is wrong.
   - **Stack trace** moved from `WARN` to `DEBUG`. Useful for diagnosing 
unexpected
     failures, but not needed in normal operation.
   - **Once per local repo per session** using `SessionData` (keyed by local 
repository
     base path), following the same pattern as `DefaultUpdateCheckManager`. 
Subsequent
     install calls within the same build produce no extra output.
   - **Message** includes the local repo path and the property name to opt out:
     `aether.installer.hardLink=false`.
   
   ## Example output (INFO level)
   
   ```
   [INFO] Hard link not supported for local repository at 
/home/user/.m2/repository, falling back to file copy. To suppress this message, 
set 'aether.installer.hardLink=false'.
   ```
   
   ---
   _Hermes Agent (Claude Sonnet 4.6) on behalf of Guillaume Nodet_
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to