[GitHub] [maven-integration-testing] slawekjaranowski opened a new pull request, #200: Add org.apache.maven.plugins:maven-plugin-plugin:3.2 to bootstrap

[GitBox]

slawekjaranowski opened a new pull request, #200:
URL: https://github.com/apache/maven-integration-testing/pull/200

   Causes failing tests on 3.9.x branch


-- 
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-integration-testing] slawekjaranowski merged pull request #200: Add org.apache.maven.plugins:maven-plugin-plugin:3.2 to bootstrap

[GitBox]

slawekjaranowski merged PR #200:
URL: https://github.com/apache/maven-integration-testing/pull/200


-- 
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-verifier] slawekjaranowski closed pull request #45: Bump slf4j-simple from 1.7.36 to 2.0.1

[GitBox]

slawekjaranowski closed pull request #45: Bump slf4j-simple from 1.7.36 to 2.0.1
URL: https://github.com/apache/maven-verifier/pull/45


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-verifier] dependabot[bot] commented on pull request #45: Bump slf4j-simple from 1.7.36 to 2.0.1

[GitBox]

dependabot[bot] commented on PR #45:
URL: https://github.com/apache/maven-verifier/pull/45#issuecomment-124064

   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

[jira] [Commented] (MASSEMBLY-965) Symbolic links get copied with absolute path

[Jira]

[ 
https://issues.apache.org/jira/browse/MASSEMBLY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605206#comment-17605206
 ] 

Václav Haisman commented on MASSEMBLY-965:
--

This is a real bummer. This appears to be in Plexus IO. I am able to reproduce 
this with 3.3.0 with explicit dependency on plexus-io 3.4.0.

> Symbolic links get copied with absolute path
> 
>
> Key: MASSEMBLY-965
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-965
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Marc Guillemot
>Priority: Major
>
> Copied symbolic links in a `` have an absolute path as target and 
> not the one of the original resource.
> Example:
> Source: {{foo -> ../my-file1}}
> Assembly: {{foo ->/home/marc/projects/demo/src/somestuff/myfile1}}
> This is a regression compared to 3.3.0. According to git bisect, the problem 
> has been introduced with commit
> [https://github.com/apache/maven-assembly-plugin/commit/937750250bfe06333f92351fa1a19a9cd5e59d28]
> Pull Request with failing integration test follows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MASSEMBLY-965) Symbolic links get copied with absolute path

[Jira]

[ 
https://issues.apache.org/jira/browse/MASSEMBLY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605212#comment-17605212
 ] 

Václav Haisman commented on MASSEMBLY-965:
--

Cross reference to Plexus IO GitHub issue: 
https://github.com/codehaus-plexus/plexus-io/issues/89

> Symbolic links get copied with absolute path
> 
>
> Key: MASSEMBLY-965
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-965
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Marc Guillemot
>Priority: Major
>
> Copied symbolic links in a `` have an absolute path as target and 
> not the one of the original resource.
> Example:
> Source: {{foo -> ../my-file1}}
> Assembly: {{foo ->/home/marc/projects/demo/src/somestuff/myfile1}}
> This is a regression compared to 3.3.0. According to git bisect, the problem 
> has been introduced with commit
> [https://github.com/apache/maven-assembly-plugin/commit/937750250bfe06333f92351fa1a19a9cd5e59d28]
> Pull Request with failing integration test follows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-ear-plugin] dependabot[bot] opened a new pull request, #60: Bump plexus-archiver from 4.2.4 to 4.5.0

[GitBox]

dependabot[bot] opened a new pull request, #60:
URL: https://github.com/apache/maven-ear-plugin/pull/60

   Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) 
from 4.2.4 to 4.5.0.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>plexus-archiver's
 releases.
   
   Plexus Archiver 4.5.0
   🚀 New features and improvements
   
   Add zstd (un)archiver support (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/pull/226";>#226)
 https://github.com/pleeplop";>@​pleeplop
   
   🐛 Bug Fixes
   
   Fix UnArchiver#isOverwrite not working as expected (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/pull/229";>#229)
 https://github.com/plamentotev";>@​plamentotev
   Existing files were overridden only if UnArchiver#isOverwrite 
was set and the existing files were older than the archive entry.
   Now it works as documented: older files are always overridden; when 
UnArchiver#isOverwrite is true, existing files are 
always
   overridden regardless if they are older or not.
   
   Plexus Archiver 4.4.0
   
   🚀 New features and improvements
   
   Drop legacy plexus API and use only JSR330 components (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/220";>#220)
 https://github.com/cstamas";>@​cstamas
   
   Plexus Archiver 4.3.0
   
   🚀 New features and improvements
   
   Require Java 8 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/206";>#206)
 https://github.com/plamentotev";>@​plamentotev
   Refactor to use FileTime API (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/199";>#199)
 https://github.com/jorsol";>@​jorsol
   Rename setTime method to setZipEntryTime (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/209";>#209)
 https://github.com/jorsol";>@​jorsol
   Convert InputStreamSupplier to lambdas (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/212";>#212)
 https://github.com/jorsol";>@​jorsol
   Update plexus-container-default to 2.1.1, commons-io 2.11.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/211";>#211)
 https://github.com/jorsol";>@​jorsol
   FIX: Reproducible Builds not working when using modular jar (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/205";>#205)
 https://github.com/jorsol";>@​jorsol
   
   📦 Dependency updates
   
   Bump plexus-parent from 8 to 10 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/219";>#219)
 https://github.com/dependabot";>@​dependabot
   Bump plexus-io from 3.2.0 to 3.3.1 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/214";>#214)
 https://github.com/dependabot";>@​dependabot
   Bump plexus-utils from 3.4.1 to 3.4.2 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/218";>#218)
 https://github.com/dependabot";>@​dependabot
   
   Plexus Archiver 4.2.7
   🚀 New features and improvements
   
   Respect order of META-INF/ and META-INF/MANIFEST.MF entries in a JAR 
file (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/189";>#189)
 https://github.com/michael-o";>@​michael-o
   
   Plexus Archiver 4.2.6
   This release updates commons-compress to 1.21 which contains security 
fixed for https://github.com/advisories/GHSA-xqfj-vm6h-2x34";>CVE-2021-35517 https://github.com/advisories/GHSA-crv7-7245-f45f";>CVE-2021-35516 https://github.com/advisories/GHSA-7hfm-57qf-j43q";>CVE-2021-35515 https://github.com/advisories/GHSA-mc84-pj99-q6hh";>CVE-2021-36090
   This version requires Java 8 as minimum (commons-compress 1.21 
requires Java 8).
   🚀 New features and improvements
   
   FileInputStream, FileOutputStream, FileReader and FileWriter are no 
longer used (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/183";>#183)
 https://github.com/jorsol";>@​jorsol
   
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/61aa536b08b1ddb71308660d35ac9277a3b2113b";>61aa536
 [maven-release-plugin] prepare release plexus-archiver-4.5.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/69d9efbe4a22625a3dea024811d19ba1267d98b8";>69d9efb
 Bump zstd-jni from 1.5.2-3 to 1.5.2-4
   https://github.com/codehaus-plexus/plexus-archiver/commit/b5aae67e84b4f2c307ef7be83fe6624c634d1e5d";>b5aae67
 Bump to 4.5.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/5ba0d19755d396e28ef925cbda98ec1fe3aa9c7d";>5ba0d19
 Add zstd (un)archiver support
   https://github.com/codehaus-plexus/plexus-archiver/commit/8656ee0eaa1e10ad1c49891cab7cd4ab54854b68";>8656ee0
 Fix UnArchiver#isOverwrite not working as expected
   https://github.com/codehaus-plexus/plexus-archiver/commit/57d924bae86fc1cc5f18a42c3efeb43b8e1c63ce";>57d924b
 Bump junitVersion from 5.8.2 to 5.9.0
   ht

[GitHub] [maven-ear-plugin] dependabot[bot] commented on pull request #57: Bump plexus-archiver from 4.2.4 to 4.4.0

[GitBox]

dependabot[bot] commented on PR #57:
URL: https://github.com/apache/maven-ear-plugin/pull/57#issuecomment-1247833065

   Superseded by #60.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-ear-plugin] dependabot[bot] closed pull request #57: Bump plexus-archiver from 4.2.4 to 4.4.0

[GitBox]

dependabot[bot] closed pull request #57: Bump plexus-archiver from 4.2.4 to 
4.4.0
URL: https://github.com/apache/maven-ear-plugin/pull/57


-- 
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] (MASSEMBLY-965) Symbolic links get copied with absolute path

[Jira]

[ 
https://issues.apache.org/jira/browse/MASSEMBLY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605232#comment-17605232
 ] 

Václav Haisman commented on MASSEMBLY-965:
--

Workaround: Overriding the plexus-io dependency version with 3.3.1 seems to fix 
the issue for me. 

> Symbolic links get copied with absolute path
> 
>
> Key: MASSEMBLY-965
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-965
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Marc Guillemot
>Priority: Major
>
> Copied symbolic links in a `` have an absolute path as target and 
> not the one of the original resource.
> Example:
> Source: {{foo -> ../my-file1}}
> Assembly: {{foo ->/home/marc/projects/demo/src/somestuff/myfile1}}
> This is a regression compared to 3.3.0. According to git bisect, the problem 
> has been introduced with commit
> [https://github.com/apache/maven-assembly-plugin/commit/937750250bfe06333f92351fa1a19a9cd5e59d28]
> Pull Request with failing integration test follows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-javadoc-plugin] kwin merged pull request #161: [MJAVADOC-729] Link to Javadoc references from JDK 17

[GitBox]

kwin merged PR #161:
URL: https://github.com/apache/maven-javadoc-plugin/pull/161


-- 
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] [Resolved] (MJAVADOC-729) Link to Javadoc references from JDK 17

[Konrad Windszus (Jira)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus resolved MJAVADOC-729.
--
Fix Version/s: 3.4.2
   Resolution: Fixed

Fixed in 
https://github.com/apache/maven-javadoc-plugin/commit/7cbf43499fa801ed633462ce590284667ac8898a.

> Link to Javadoc references from JDK 17
> --
>
> Key: MJAVADOC-729
> URL: https://issues.apache.org/jira/browse/MJAVADOC-729
> Project: Maven Javadoc Plugin
>  Issue Type: Improvement
>  Components: javadoc
>Affects Versions: 3.4.1
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.4.2
>
>
> Currently the external links explaining javadoc features or options from the 
> site at https://github.com/apache/maven-javadoc-plugin still [point to 
> https://docs.oracle.com/javase/7/docs/technotes/tools/windows/javadoc.html|https://github.com/apache/maven-javadoc-plugin/search?q=https%3A%2F%2Fdocs.oracle.com%2Fjavase%2F7%2Fdocs%2Ftechnotes%2Ftools%2Fwindows%2Fjavadoc.html].
> Instead one should leverage the new documentation at
> # 
> https://docs.oracle.com/en/java/javase/17/docs/specs/javadoc/doc-comment-spec.html
>  (for the standard doclet) and
> # https://docs.oracle.com/en/java/javase/17/javadoc/javadoc.html (for the 
> options of the javadoc tool)
> The new documentation provides a better overview of javadoc and also 
> describes the additions added since Java 7.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

Robert Seidel created MRELEASE-1103:
---

 Summary: decryption of server password in settings.xml failed 
(works with 2.5.3)
 Key: MRELEASE-1103
 URL: https://issues.apache.org/jira/browse/MRELEASE-1103
 Project: Maven Release Plugin
  Issue Type: Bug
Affects Versions: 3.0.0-M6
Reporter: Robert Seidel


A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket repository.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40*  [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40*  [INFO] 11/17 prepare:scm-commit-release

*11:35:40*  [INFO] Checking in modified POMs...

*11:35:40*  [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41*  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project AEBParentPom: Unable to commit files

*11:35:41*  [ERROR] Provider message:

*11:35:41*  [ERROR] The git-push command failed.

*11:35:41*  [ERROR] Command output: *11:35:41*  [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/aebparentpom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

 [ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Seidel updated MRELEASE-1103:

Description: 
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket repository.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project AEBParentPom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.

  was:
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket repository.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40*  [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40*  [INFO] 11/17 prepare:scm-commit-release

*11:35:40*  [INFO] Checking in modified POMs...

*11:35:40*  [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41*  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project AEBParentPom: Unable to commit files

*11:35:41*  [ERROR] Provider message:

*11:35:41*  [ERROR] The git-push command failed.

*11:35:41*  [ERROR] Command output: *11:35:41*  [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/aebparentpom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.


> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket repository.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project AEBParentPom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
> failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

 [ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Seidel updated MRELEASE-1103:

Description: 
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket server.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project AEBParentPom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.

  was:
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket repository.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project AEBParentPom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.


> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project AEBParentPom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
> failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-javadoc-plugin] kwin opened a new pull request, #162: [MJAVADOC-685] Deprecate parameter "stylesheet"

[GitBox]

kwin opened a new pull request, #162:
URL: https://github.com/apache/maven-javadoc-plugin/pull/162

   Remove custom Maven stylesheet CSS as incompatible with javadoc at least 
since JDK8
   
   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/MJAVADOC) 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 `[MJAVADOC-XXX] - Fixes bug in 
ApproximateQuantiles`,
  where you replace `MJAVADOC-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.
- [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A 
more thorough check will 
  be performed on your pull request automatically.
   
   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)
   
- [ ] 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

[jira] [Updated] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

 [ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Seidel updated MRELEASE-1103:

Description: 
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket server.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project ExamplePom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.

  was:
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket server.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project AEBParentPom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.


> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
> failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MJAVADOC-729) Link to Javadoc references from JDK 17

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605267#comment-17605267
 ] 

Hudson commented on MJAVADOC-729:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven-javadoc-plugin » master 
#38

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-javadoc-plugin/job/master/38/

> Link to Javadoc references from JDK 17
> --
>
> Key: MJAVADOC-729
> URL: https://issues.apache.org/jira/browse/MJAVADOC-729
> Project: Maven Javadoc Plugin
>  Issue Type: Improvement
>  Components: javadoc
>Affects Versions: 3.4.1
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.4.2
>
>
> Currently the external links explaining javadoc features or options from the 
> site at https://github.com/apache/maven-javadoc-plugin still [point to 
> https://docs.oracle.com/javase/7/docs/technotes/tools/windows/javadoc.html|https://github.com/apache/maven-javadoc-plugin/search?q=https%3A%2F%2Fdocs.oracle.com%2Fjavase%2F7%2Fdocs%2Ftechnotes%2Ftools%2Fwindows%2Fjavadoc.html].
> Instead one should leverage the new documentation at
> # 
> https://docs.oracle.com/en/java/javase/17/docs/specs/javadoc/doc-comment-spec.html
>  (for the standard doclet) and
> # https://docs.oracle.com/en/java/javase/17/javadoc/javadoc.html (for the 
> options of the javadoc tool)
> The new documentation provides a better overview of javadoc and also 
> describes the additions added since Java 7.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven] slawekjaranowski commented on pull request #802: [MNG-7463] Improve documentation about deprecation in Mojo

[GitBox]

slawekjaranowski commented on PR #802:
URL: https://github.com/apache/maven/pull/802#issuecomment-1247974318

   After a few re-run all builds pass.
   
   There is left wrong check from previous builds on GH ... 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MNG-7463) Improve documentation about deprecation in Mojo

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605280#comment-17605280
 ] 

ASF GitHub Bot commented on MNG-7463:
-

slawekjaranowski commented on PR #802:
URL: https://github.com/apache/maven/pull/802#issuecomment-1247974318

   After a few re-run all builds pass.
   
   There is left wrong check from previous builds on GH ... 




> Improve documentation about deprecation in Mojo
> ---
>
> Key: MNG-7463
> URL: https://issues.apache.org/jira/browse/MNG-7463
> Project: Maven
>  Issue Type: Improvement
>  Components: Documentation:  General, Plugin API
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.9.0-candidate, 4.0.0-alpha-1, 4.0.0
>
>
> fix, improve:
> - java docs of {{org.apache.maven.plugin.descriptor.MojoDescriptor}} 
> -- {{deprecated}} filed and set/get methods.
> - maven-plugin-api/src/main/mdo/plugin.mdo 
> -- descriptions of mojo, parameters deprecated field
> - https://maven.apache.org/developers/mojo-api-specification.html
> -- descriptions of mojo, parameters deprecated 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-pmd-plugin] dependabot[bot] opened a new pull request, #93: Bump release-drafter/release-drafter from 5.20.1 to 5.21.0

[GitBox]

dependabot[bot] opened a new pull request, #93:
URL: https://github.com/apache/maven-pmd-plugin/pull/93

   Bumps 
[release-drafter/release-drafter](https://github.com/release-drafter/release-drafter)
 from 5.20.1 to 5.21.0.
   
   Release notes
   Sourced from https://github.com/release-drafter/release-drafter/releases";>release-drafter/release-drafter's
 releases.
   
   v5.21.0
   What's Changed
   New
   
   fetch 100 labels for pull requests instead of 10 (https://github-redirect.dependabot.com/release-drafter/release-drafter/issues/1220";>#1220)
 https://github.com/matoubidou";>@​matoubidou
   
   Full Changelog: https://github.com/release-drafter/release-drafter/compare/v6.0.0-beta.1...v5.21.0";>https://github.com/release-drafter/release-drafter/compare/v6.0.0-beta.1...v5.21.0
   
   
   
   Commits
   
   https://github.com/release-drafter/release-drafter/commit/df69d584deac33d8569990cb6413f82447181076";>df69d58
 v5.21.0
   https://github.com/release-drafter/release-drafter/commit/ecbbed96e59dfeb4f433d84fbdca2b1e01887d62";>ecbbed9
 fetch 100 labels for pull requests instead of 10 (https://github-redirect.dependabot.com/release-drafter/release-drafter/issues/1220";>#1220)
   See full diff in https://github.com/release-drafter/release-drafter/compare/v5.20.1...v5.21.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=release-drafter/release-drafter&package-manager=github_actions&previous-version=5.20.1&new-version=5.21.0)](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-pmd-plugin] dependabot[bot] opened a new pull request, #94: Bump slf4jVersion from 1.7.36 to 2.0.1

[GitBox]

dependabot[bot] opened a new pull request, #94:
URL: https://github.com/apache/maven-pmd-plugin/pull/94

   Bumps `slf4jVersion` from 1.7.36 to 2.0.1.
   Updates `slf4j-api` from 1.7.36 to 2.0.1
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   Updates `jul-to-slf4j` from 1.7.36 to 2.0.1
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   Updates `slf4j-simple` from 1.7.36 to 2.0.1
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can al

[jira] [Comment Edited] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605285#comment-17605285
 ] 

Michael Osipov edited comment on MRELEASE-1103 at 9/15/22 11:41 AM:


No really helpful. I recommend to try out every milestone to figure out the 
first broken release.

 

Side note: The so called encryption gives you a false sense of security. It is 
just an indirection.

[~cstamas] , yes another reason why we should deprecate it.


was (Author: michael-o):
No really helpful. I recommend to try out every milestone to figure out the 
first broken release.

 

Side note: The so called encryption gives you a false sense of security. It is 
just an indirection.

> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
> failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605285#comment-17605285
 ] 

Michael Osipov commented on MRELEASE-1103:
--

No really helpful. I recommend to try out every milestone to figure out the 
first broken release.

 

Side note: The so called encryption gives you a false sense of security. It is 
just an indirection.

> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
> failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MRESOLVER-273) Create more compact File locking layout

[Jira]

Tamás Cservenák created MRESOLVER-273:
-

 Summary: Create more compact File locking layout
 Key: MRESOLVER-273
 URL: https://issues.apache.org/jira/browse/MRESOLVER-273
 Project: Maven Resolver
  Issue Type: Improvement
Reporter: Tamás Cservenák


Current FileGAVNameMapper "mimics" loosely local reposiory layout, uses long 
paths, hence (relatively) big strings etc. 

More compact layout would be just to hash strings like "a:G:A:V" and 
"m:G[:A[:V]]" for artifacts and metadata instead, and create 2 level deep 
hashed storage.

Problem with "loose" layout is that they do end up as files in OS, while these 
would be much shorter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRESOLVER-273) Create more compact File locking layout

[Jira]

 [ 
https://issues.apache.org/jira/browse/MRESOLVER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamás Cservenák updated MRESOLVER-273:
--
Fix Version/s: resolver-next

> Create more compact File locking layout
> ---
>
> Key: MRESOLVER-273
> URL: https://issues.apache.org/jira/browse/MRESOLVER-273
> Project: Maven Resolver
>  Issue Type: Improvement
>Reporter: Tamás Cservenák
>Priority: Major
> Fix For: resolver-next
>
>
> Current FileGAVNameMapper "mimics" loosely local reposiory layout, uses long 
> paths, hence (relatively) big strings etc. 
> More compact layout would be just to hash strings like "a:G:A:V" and 
> "m:G[:A[:V]]" for artifacts and metadata instead, and create 2 level deep 
> hashed storage.
> Problem with "loose" layout is that they do end up as files in OS, while 
> these would be much shorter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSHADE-141) keepDependenciesWithProvidedScope does not work

[Delany (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHADE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605290#comment-17605290
 ] 

Delany commented on MSHADE-141:
---

Still an issue with plugin version 3.4.0 in the dependency-reduced-pom.xml

> keepDependenciesWithProvidedScope does not work
> ---
>
> Key: MSHADE-141
> URL: https://issues.apache.org/jira/browse/MSHADE-141
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Steve Tynor
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: pom-direct.xml, pom-indirect.xml
>
>
> keepDependenciesWithProvidedScope option does not seem to work.
> Expected behavior from both poms is to create an uber jar from the following 
> transitive dependencies: 
> [INFO] Including org.apache.activemq:activemq-client:jar:5.8.0 in the shaded 
> jar.
> [INFO] Including org.slf4j:slf4j-api:jar:1.6.6 in the shaded jar.
> [INFO] Including org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1 in 
> the shaded jar.
> [INFO] Including org.fusesource.hawtbuf:hawtbuf:jar:1.9 in the shaded jar.
> [INFO] Including 
> org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1 in the 
> shaded jar.
> I've attached two test cases 
>mvn -f pom-direct.xml clean install
> will create an empty jar.
>mvn -f pom-indirect.xml clean install
> will not include the slf4j-api which is a dependency of activemq-client, but 
> is marked provided in the pom.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-doxia] dependabot[bot] opened a new pull request, #118: Bump slf4jVersion from 1.7.36 to 2.0.1

[GitBox]

dependabot[bot] opened a new pull request, #118:
URL: https://github.com/apache/maven-doxia/pull/118

   Bumps `slf4jVersion` from 1.7.36 to 2.0.1.
   Updates `slf4j-api` from 1.7.36 to 2.0.1
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   Updates `slf4j-simple` from 1.7.36 to 2.0.1
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   
   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 

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request, #75: Bump slf4j-api from 1.7.32 to 2.0.1

[GitBox]

dependabot[bot] opened a new pull request, #75:
URL: https://github.com/apache/maven-artifact-transfer/pull/75

   Bumps [slf4j-api](https://github.com/qos-ch/slf4j) from 1.7.32 to 2.0.1.
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.32...v_2.0.1";>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.slf4j:slf4j-api&package-manager=maven&previous-version=1.7.32&new-version=2.0.1)](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-artifact-transfer] dependabot[bot] commented on pull request #73: Bump slf4j-api from 1.7.32 to 2.0.0

[GitBox]

dependabot[bot] commented on PR #73:
URL: 
https://github.com/apache/maven-artifact-transfer/pull/73#issuecomment-1248020023

   Superseded by #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-artifact-transfer] dependabot[bot] closed pull request #73: Bump slf4j-api from 1.7.32 to 2.0.0

[GitBox]

dependabot[bot] closed pull request #73: Bump slf4j-api from 1.7.32 to 2.0.0
URL: https://github.com/apache/maven-artifact-transfer/pull/73


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Assigned] (MASSEMBLY-965) Symbolic links get copied with absolute path

[Guillaume Nodet (Jira)]

 [ 
https://issues.apache.org/jira/browse/MASSEMBLY-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reassigned MASSEMBLY-965:
-

Assignee: Guillaume Nodet

> Symbolic links get copied with absolute path
> 
>
> Key: MASSEMBLY-965
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-965
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 3.4.0
>Reporter: Marc Guillemot
>Assignee: Guillaume Nodet
>Priority: Major
>
> Copied symbolic links in a `` have an absolute path as target and 
> not the one of the original resource.
> Example:
> Source: {{foo -> ../my-file1}}
> Assembly: {{foo ->/home/marc/projects/demo/src/somestuff/myfile1}}
> This is a regression compared to 3.3.0. According to git bisect, the problem 
> has been introduced with commit
> [https://github.com/apache/maven-assembly-plugin/commit/937750250bfe06333f92351fa1a19a9cd5e59d28]
> Pull Request with failing integration test follows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MRESOLVER-273) Create more compact File locking layout/mapper

[Jira]

 [ 
https://issues.apache.org/jira/browse/MRESOLVER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamás Cservenák updated MRESOLVER-273:
--
Summary: Create more compact File locking layout/mapper  (was: Create more 
compact File locking layout)

> Create more compact File locking layout/mapper
> --
>
> Key: MRESOLVER-273
> URL: https://issues.apache.org/jira/browse/MRESOLVER-273
> Project: Maven Resolver
>  Issue Type: Improvement
>Reporter: Tamás Cservenák
>Priority: Major
> Fix For: resolver-next
>
>
> Current FileGAVNameMapper "mimics" loosely local reposiory layout, uses long 
> paths, hence (relatively) big strings etc. 
> More compact layout would be just to hash strings like "a:G:A:V" and 
> "m:G[:A[:V]]" for artifacts and metadata instead, and create 2 level deep 
> hashed storage.
> Problem with "loose" layout is that they do end up as files in OS, while 
> these would be much shorter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-jxr] dependabot[bot] opened a new pull request, #77: Bump slf4j-simple from 1.7.36 to 2.0.1

[GitBox]

dependabot[bot] opened a new pull request, #77:
URL: https://github.com/apache/maven-jxr/pull/77

   Bumps [slf4j-simple](https://github.com/qos-ch/slf4j) from 1.7.36 to 2.0.1.
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.slf4j:slf4j-simple&package-manager=maven&previous-version=1.7.36&new-version=2.0.1)](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-jxr] dependabot[bot] opened a new pull request, #78: Bump slf4j-api from 1.7.36 to 2.0.1

[GitBox]

dependabot[bot] opened a new pull request, #78:
URL: https://github.com/apache/maven-jxr/pull/78

   Bumps [slf4j-api](https://github.com/qos-ch/slf4j) from 1.7.36 to 2.0.1.
   
   Commits
   
   https://github.com/qos-ch/slf4j/commit/9752442b6e6db0749915dc40e80437dc97cd772d";>9752442
 prepare release 2.0.1
   https://github.com/qos-ch/slf4j/commit/c0f7f16bfb2cdbcf38df6039219ee3f57c99117e";>c0f7f16
 minor javadoc change
   https://github.com/qos-ch/slf4j/commit/1148b9852997376ab865cfc5e448fee0675cabbd";>1148b98
 Merge branch 'master' of github.com:qos-ch/slf4j
   https://github.com/qos-ch/slf4j/commit/593f89f85af8d181f0727315224f37fe0aa5fdcb";>593f89f
 fix SLF4J SLF4J-560
   https://github.com/qos-ch/slf4j/commit/03deea9f77c354ccd59c578808cff689299ba5eb";>03deea9
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/302";>#302 
from coheigea/coheigea/reload4j_1.2.22
   https://github.com/qos-ch/slf4j/commit/c9d5cc1257be51d837bf8e3f10f94eb18d1390bb";>c9d5cc1
 Update reload4j to 1.2.22
   https://github.com/qos-ch/slf4j/commit/bae56f544b0c30cedb265729f3c6cce72fa79f10";>bae56f5
 Merge pull request https://github-redirect.dependabot.com/qos-ch/slf4j/issues/294";>#294 
from marcwrobel/fix-typos
   https://github.com/qos-ch/slf4j/commit/24788ac731cdce9f27670f22efd42a7b9f1d771e";>24788ac
 fix typos in documentations
   https://github.com/qos-ch/slf4j/commit/05c0b0a88165094a9044e981c7836e10a05c8f6c";>05c0b0a
 fix SLF4J-555
   https://github.com/qos-ch/slf4j/commit/400a885e7d74c291b728f983a38697553d4e0431";>400a885
 remove reference to 1.7
   Additional commits viewable in https://github.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.1";>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.slf4j:slf4j-api&package-manager=maven&previous-version=1.7.36&new-version=2.0.1)](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] [Updated] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

 [ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Seidel updated MRELEASE-1103:

Description: 
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket server.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project ExamplePom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output:

*11:35:41* [ERROR] fatal: Authentication failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.

  was:
A server section was defined in the settings.xml at  
with id, username and password to connect to a Bitbucket server.

In the pom.xml the id was referenced in the properties via project.scm.id.

With 2.5.3 the build is running fine, but with 3.0.06-M6 the following happens:

*11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
activated because it does not exist.

*11:35:40* [INFO] 11/17 prepare:scm-commit-release

*11:35:40* [INFO] Checking in modified POMs...

*11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
bitbucket-prod, using auth token as is: decrypt failed

and in the aftermath:

*11:35:41* [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) on 
project ExamplePom: Unable to commit files

*11:35:41* [ERROR] Provider message:

*11:35:41* [ERROR] The git-push command failed.

*11:35:41* [ERROR] Command output: *11:35:41* [ERROR] fatal: Authentication 
failed for 
'[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'

 

JDK used was Adoptium 17 (but with 11 the same problem occured).

Maven used was 3.8.6.


> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output:
> *11:35:41* [ERROR] fatal: Authentication failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven] gnodet opened a new pull request, #803: Project and model builder improvements

[GitBox]

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

   Various speed improvements to the initial project building:
 * small optimisations
 * multi-threading in DefaultProjectBuilder and DefaultModelBuilder
 * add caching (using weak keys) for model inheritance and profile injection


-- 
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-integration-testing] gnodet commented on a diff in pull request #199: Remove code corresponding to Maven 2.x and JDK 7

[GitBox]

gnodet commented on code in PR #199:
URL: 
https://github.com/apache/maven-integration-testing/pull/199#discussion_r971987215


##
core-it-support/maven-it-helper/src/main/java/org/apache/maven/it/AbstractMavenIntegrationTestCase.java:
##
@@ -568,33 +568,19 @@ protected Verifier newVerifier( String basedir, String 
settings, boolean debug )
 
 String path = settingsFile.getAbsolutePath();
 
-// dedicated CLI option only available since MNG-3914
-if ( matchesVersionRange( "[2.1.0,)" ) )
+verifier.addCliOption( "--global-settings" );
+if ( path.indexOf( ' ' ) < 0 )
 {
-verifier.addCliOption( "--global-settings" );
-if ( path.indexOf( ' ' ) < 0 )
-{
-verifier.addCliOption( path );
-}
-else
-{
-verifier.addCliOption( '"' + path + '"' );
-}
+verifier.addCliOption( path );
 }
 else
 {
-verifier.getSystemProperties().put( 
"org.apache.maven.global-settings", path );
+verifier.addCliOption( '"' + path + '"' );
 }

Review Comment:
   Yes, note that the upgrade to verifier 2.0 will break quotes arguments.  
Also note that I plan to merge 
https://github.com/apache/maven-integration-testing/pull/176 soon and it 
includes an upgrade to verifier 2.0-SNAPSHOT.  Unless we really do want to 
postpone until it's released, but the snapshots are available on public apache 
repos, so that's not a dealbreaker, especially as ITs are never released.



-- 
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] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605348#comment-17605348
 ] 

Robert Seidel commented on MRELEASE-1103:
-

I've checked the older versions between 2.5.3 and M6 and the problem is 
introduced with M6 (it works M5).

I'm well aware of maven settings.xml security. In my case this is not an issue 
as only jenkins build agents using that specific settings.xml where only 
authorized users have access to.

> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output:
> *11:35:41* [ERROR] fatal: Authentication failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Robert Seidel (Jira)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605348#comment-17605348
 ] 

Robert Seidel edited comment on MRELEASE-1103 at 9/15/22 1:35 PM:
--

I've checked the older versions between 2.5.3 and M6 and the problem is 
introduced with M6 (it works with M5).

I'm well aware of maven settings.xml security. In my case this is not an issue 
as only jenkins build agents using that specific settings.xml where only 
authorized users have access to.


was (Author: JIRAUSER295788):
I've checked the older versions between 2.5.3 and M6 and the problem is 
introduced with M6 (it works M5).

I'm well aware of maven settings.xml security. In my case this is not an issue 
as only jenkins build agents using that specific settings.xml where only 
authorized users have access to.

> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output:
> *11:35:41* [ERROR] fatal: Authentication failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRESOLVER-273) Create more compact File locking layout/mapper

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MRESOLVER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605350#comment-17605350
 ] 

Michael Osipov commented on MRESOLVER-273:
--

This is similar to the hash key I use for Redis. Interesting idea. Similar to 
Git database.

> Create more compact File locking layout/mapper
> --
>
> Key: MRESOLVER-273
> URL: https://issues.apache.org/jira/browse/MRESOLVER-273
> Project: Maven Resolver
>  Issue Type: Improvement
>Reporter: Tamás Cservenák
>Priority: Major
> Fix For: resolver-next
>
>
> Current FileGAVNameMapper "mimics" loosely local reposiory layout, uses long 
> paths, hence (relatively) big strings etc. 
> More compact layout would be just to hash strings like "a:G:A:V" and 
> "m:G[:A[:V]]" for artifacts and metadata instead, and create 2 level deep 
> hashed storage.
> Problem with "loose" layout is that they do end up as files in OS, while 
> these would be much shorter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-integration-testing] slawekjaranowski commented on a diff in pull request #199: Remove code corresponding to Maven 2.x and JDK 7

[GitBox]

slawekjaranowski commented on code in PR #199:
URL: 
https://github.com/apache/maven-integration-testing/pull/199#discussion_r972012766


##
core-it-support/maven-it-helper/src/main/java/org/apache/maven/it/AbstractMavenIntegrationTestCase.java:
##
@@ -568,33 +568,19 @@ protected Verifier newVerifier( String basedir, String 
settings, boolean debug )
 
 String path = settingsFile.getAbsolutePath();
 
-// dedicated CLI option only available since MNG-3914
-if ( matchesVersionRange( "[2.1.0,)" ) )
+verifier.addCliOption( "--global-settings" );
+if ( path.indexOf( ' ' ) < 0 )
 {
-verifier.addCliOption( "--global-settings" );
-if ( path.indexOf( ' ' ) < 0 )
-{
-verifier.addCliOption( path );
-}
-else
-{
-verifier.addCliOption( '"' + path + '"' );
-}
+verifier.addCliOption( path );
 }
 else
 {
-verifier.getSystemProperties().put( 
"org.apache.maven.global-settings", path );
+verifier.addCliOption( '"' + path + '"' );
 }

Review Comment:
   We have many changes in Verifier 2.0.0, many deprecated methods, etc 
   My proposition is to release Verifier 2.0.0-M1 as is now - I can do it in 
next weekend.
   
   In next step after #176   we can clean of using deprecated methods we can 
release next milestone with next part of resolved issues and so on, until to 
final 2.0.0
   
   As always I like step by step and if it possible split bigger changes.
   
   What do you think?



-- 
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-plugin-tools] dependabot[bot] opened a new pull request, #142: Bump plexus-archiver from 4.2.7 to 4.5.0

[GitBox]

dependabot[bot] opened a new pull request, #142:
URL: https://github.com/apache/maven-plugin-tools/pull/142

   Bumps [plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) 
from 4.2.7 to 4.5.0.
   
   Release notes
   Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>plexus-archiver's
 releases.
   
   Plexus Archiver 4.5.0
   🚀 New features and improvements
   
   Add zstd (un)archiver support (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/pull/226";>#226)
 https://github.com/pleeplop";>@​pleeplop
   
   🐛 Bug Fixes
   
   Fix UnArchiver#isOverwrite not working as expected (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/pull/229";>#229)
 https://github.com/plamentotev";>@​plamentotev
   Existing files were overridden only if UnArchiver#isOverwrite 
was set and the existing files were older than the archive entry.
   Now it works as documented: older files are always overridden; when 
UnArchiver#isOverwrite is true, existing files are 
always
   overridden regardless if they are older or not.
   
   Plexus Archiver 4.4.0
   
   🚀 New features and improvements
   
   Drop legacy plexus API and use only JSR330 components (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/220";>#220)
 https://github.com/cstamas";>@​cstamas
   
   Plexus Archiver 4.3.0
   
   🚀 New features and improvements
   
   Require Java 8 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/206";>#206)
 https://github.com/plamentotev";>@​plamentotev
   Refactor to use FileTime API (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/199";>#199)
 https://github.com/jorsol";>@​jorsol
   Rename setTime method to setZipEntryTime (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/209";>#209)
 https://github.com/jorsol";>@​jorsol
   Convert InputStreamSupplier to lambdas (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/212";>#212)
 https://github.com/jorsol";>@​jorsol
   Update plexus-container-default to 2.1.1, commons-io 2.11.0 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/211";>#211)
 https://github.com/jorsol";>@​jorsol
   FIX: Reproducible Builds not working when using modular jar (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/205";>#205)
 https://github.com/jorsol";>@​jorsol
   
   📦 Dependency updates
   
   Bump plexus-parent from 8 to 10 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/219";>#219)
 https://github.com/dependabot";>@​dependabot
   Bump plexus-io from 3.2.0 to 3.3.1 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/214";>#214)
 https://github.com/dependabot";>@​dependabot
   Bump plexus-utils from 3.4.1 to 3.4.2 (https://github-redirect.dependabot.com/codehaus-plexus/plexus-archiver/issues/218";>#218)
 https://github.com/dependabot";>@​dependabot
   
   
   
   
   Commits
   
   https://github.com/codehaus-plexus/plexus-archiver/commit/61aa536b08b1ddb71308660d35ac9277a3b2113b";>61aa536
 [maven-release-plugin] prepare release plexus-archiver-4.5.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/69d9efbe4a22625a3dea024811d19ba1267d98b8";>69d9efb
 Bump zstd-jni from 1.5.2-3 to 1.5.2-4
   https://github.com/codehaus-plexus/plexus-archiver/commit/b5aae67e84b4f2c307ef7be83fe6624c634d1e5d";>b5aae67
 Bump to 4.5.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/5ba0d19755d396e28ef925cbda98ec1fe3aa9c7d";>5ba0d19
 Add zstd (un)archiver support
   https://github.com/codehaus-plexus/plexus-archiver/commit/8656ee0eaa1e10ad1c49891cab7cd4ab54854b68";>8656ee0
 Fix UnArchiver#isOverwrite not working as expected
   https://github.com/codehaus-plexus/plexus-archiver/commit/57d924bae86fc1cc5f18a42c3efeb43b8e1c63ce";>57d924b
 Bump junitVersion from 5.8.2 to 5.9.0
   https://github.com/codehaus-plexus/plexus-archiver/commit/0a5115cc1fdc39b201f49b0763d449593d2d770a";>0a5115c
 Use @Enabled/https://github.com/Disabled";>@​Disabled 
to run tests only on specific OS/JDK
   https://github.com/codehaus-plexus/plexus-archiver/commit/5363cf902f17979fcab2b5bf8593a28513b3c20a";>5363cf9
 Migrate to JUnit 5
   https://github.com/codehaus-plexus/plexus-archiver/commit/bf33d5877efc07086652fb3754140c1d1d580a26";>bf33d58
 Update release-drafter.yml
   https://github.com/codehaus-plexus/plexus-archiver/commit/f558d87ce8b7fbdc74bdd4f512188e97a70ac3e8";>f558d87
 Use shared workflow for the Maven build
   Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.2.7...plexus-archiver-4.5.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.plexus:plexus-archiver&package-manager=maven&previous-version=4.2.7&new-version=4.5

[GitHub] [maven-plugin-tools] dependabot[bot] closed pull request #97: Bump plexus-archiver from 4.2.7 to 4.4.0

[GitBox]

dependabot[bot] closed pull request #97: Bump plexus-archiver from 4.2.7 to 
4.4.0
URL: https://github.com/apache/maven-plugin-tools/pull/97


-- 
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-plugin-tools] dependabot[bot] commented on pull request #97: Bump plexus-archiver from 4.2.7 to 4.4.0

[GitBox]

dependabot[bot] commented on PR #97:
URL: 
https://github.com/apache/maven-plugin-tools/pull/97#issuecomment-1248140066

   Superseded by #142.


-- 
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-integration-testing] gnodet commented on a diff in pull request #199: Remove code corresponding to Maven 2.x and JDK 7

[GitBox]

gnodet commented on code in PR #199:
URL: 
https://github.com/apache/maven-integration-testing/pull/199#discussion_r972026490


##
core-it-support/maven-it-helper/src/main/java/org/apache/maven/it/AbstractMavenIntegrationTestCase.java:
##
@@ -568,33 +568,19 @@ protected Verifier newVerifier( String basedir, String 
settings, boolean debug )
 
 String path = settingsFile.getAbsolutePath();
 
-// dedicated CLI option only available since MNG-3914
-if ( matchesVersionRange( "[2.1.0,)" ) )
+verifier.addCliOption( "--global-settings" );
+if ( path.indexOf( ' ' ) < 0 )
 {
-verifier.addCliOption( "--global-settings" );
-if ( path.indexOf( ' ' ) < 0 )
-{
-verifier.addCliOption( path );
-}
-else
-{
-verifier.addCliOption( '"' + path + '"' );
-}
+verifier.addCliOption( path );
 }
 else
 {
-verifier.getSystemProperties().put( 
"org.apache.maven.global-settings", path );
+verifier.addCliOption( '"' + path + '"' );
 }

Review Comment:
   Sounds like a plan to me !



-- 
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-integration-testing] slawekjaranowski commented on a diff in pull request #176: Move ITs to JDK 8 / JUnit 5

[GitBox]

slawekjaranowski commented on code in PR #176:
URL: 
https://github.com/apache/maven-integration-testing/pull/176#discussion_r972024803


##
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3038TransitiveDepManVersionTest.java:
##
@@ -22,14 +22,19 @@
 import java.io.File;
 import java.io.IOException;
 
-import org.apache.maven.it.util.ResourceExtractor;
+import org.apache.maven.shared.verifier.VerificationException;
+import org.apache.maven.shared.verifier.Verifier;
+import org.apache.maven.shared.verifier.util.ResourceExtractor;
+import org.junit.jupiter.api.Disabled;
+import org.junit.jupiter.api.Test;
 
 /**
  * This is a test set for https://issues.apache.org/jira/browse/MNG-3038";>MNG-3038
  *
  * @author Joakim Erdfelt
  *
  */
+@Disabled( "cannot reproduce" )

Review Comment:
   I suppose that now is working with junit 4, maybe TODO remarks to verify 
later



##
pom.xml:
##
@@ -82,7 +82,12 @@ under the License.
   
 org.apache.maven.shared
 maven-verifier
-1.8.0
+2.0.0-SNAPSHOT

Review Comment:
   I prefer a some of release version, even milestone
   In other case tests can be unstable and investigation can be more difficult. 



-- 
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-7539) Validate/Download SNAPSHOT dependencies once

[Adrian Tarau (Jira)]

Adrian Tarau created MNG-7539:
-

 Summary: Validate/Download SNAPSHOT dependencies once
 Key: MNG-7539
 URL: https://issues.apache.org/jira/browse/MNG-7539
 Project: Maven
  Issue Type: Improvement
  Components: Dependencies
Reporter: Adrian Tarau


Building an unreleased multi-module project (30-40 modules) which depends on 
various other unreleased modules puts a significant preasure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and server those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done outside the fact that it is not needed, it might also 
introduce flaky behaviors:
 * one module downloads a version of artifact A works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A, and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MNG-7539) Validate/Download SNAPSHOT dependencies once

[Adrian Tarau (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adrian Tarau updated MNG-7539:
--
Description: 
Building an unreleased multi-module project (30-40 modules) which depends on 
various other unreleased modules puts a significant preasure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and serve those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done outside the fact that it is not needed, it might also 
introduce flaky behaviors:
 * one module downloads a version of artifact A works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A, and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 

  was:
Building an unreleased multi-module project (30-40 modules) which depends on 
various other unreleased modules puts a significant preasure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and server those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done outside the fact that it is not needed, it might also 
introduce flaky behaviors:
 * one module downloads a version of artifact A works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A, and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 


> Validate/Download SNAPSHOT dependencies once
> 
>
> Key: MNG-7539
> URL: https://issues.apache.org/jira/browse/MNG-7539
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Adrian Tarau
>Priority: Critical
>
> Building an unreleased multi-module project (30-40 modules) which depends on 
> various other unreleased modules puts a significant preasure on the Maven 
> Repository (a local Nexus instance), and artifact resolution could slow down 
> the build 2x-3x.
> I do acknowledge that it is the job of the repository to cache and serve 
> those responses fast, and for some reason, sometimes it slows down without an 
> apparent reason.
> However, the whole build process will be faster if Maven validates a SNAPSHOT 
> once for multi-module (when the dependency is reached the first time) and 
> then use that version. Even if Maven Repository is relative fast, there is 
> still network traffic done outside the fact that it is not needed, it might 
> also introduce flaky behaviors:
>  * one module downloads a version of artifact A works with it, and everything 
> is fine
>  * 10 minutes later, another module needs artifact A, and gets a newer 
> version, which has some issues, and various (test) failures will be raised
> For consistency, on a multi-module build, all modules should _see_ the same 
> version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
> (which is very important).
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MNG-7539) Validate/Download SNAPSHOT dependencies once

[Adrian Tarau (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adrian Tarau updated MNG-7539:
--
Description: 
Building an unreleased multi-module project (30-40 modules) which depends on 
various other unreleased modules puts a significant preasure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and serve those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done. Outside the fact that it should not be done, it might 
also introduce flaky behaviors:
 * one module downloads a version of artifact A works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A, and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 

  was:
Building an unreleased multi-module project (30-40 modules) which depends on 
various other unreleased modules puts a significant preasure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and serve those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done outside the fact that it is not needed, it might also 
introduce flaky behaviors:
 * one module downloads a version of artifact A works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A, and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 


> Validate/Download SNAPSHOT dependencies once
> 
>
> Key: MNG-7539
> URL: https://issues.apache.org/jira/browse/MNG-7539
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Adrian Tarau
>Priority: Critical
>
> Building an unreleased multi-module project (30-40 modules) which depends on 
> various other unreleased modules puts a significant preasure on the Maven 
> Repository (a local Nexus instance), and artifact resolution could slow down 
> the build 2x-3x.
> I do acknowledge that it is the job of the repository to cache and serve 
> those responses fast, and for some reason, sometimes it slows down without an 
> apparent reason.
> However, the whole build process will be faster if Maven validates a SNAPSHOT 
> once for multi-module (when the dependency is reached the first time) and 
> then use that version. Even if Maven Repository is relative fast, there is 
> still network traffic done. Outside the fact that it should not be done, it 
> might also introduce flaky behaviors:
>  * one module downloads a version of artifact A works with it, and everything 
> is fine
>  * 10 minutes later, another module needs artifact A, and gets a newer 
> version, which has some issues, and various (test) failures will be raised
> For consistency, on a multi-module build, all modules should _see_ the same 
> version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
> (which is very important).
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MNG-7539) Validate/Download SNAPSHOT dependencies once

[Adrian Tarau (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adrian Tarau updated MNG-7539:
--
Description: 
Building an unreleased multi-module project (30-40 modules) that depends on 
various other unreleased modules puts significant pressure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and serve those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done. Outside the fact that it should not be done, it might 
also introduce flaky behaviors:
 * one module downloads a version of artifact A, works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 

  was:
Building an unreleased multi-module project (30-40 modules) which depends on 
various other unreleased modules puts a significant preasure on the Maven 
Repository (a local Nexus instance), and artifact resolution could slow down 
the build 2x-3x.

I do acknowledge that it is the job of the repository to cache and serve those 
responses fast, and for some reason, sometimes it slows down without an 
apparent reason.

However, the whole build process will be faster if Maven validates a SNAPSHOT 
once for multi-module (when the dependency is reached the first time) and then 
use that version. Even if Maven Repository is relative fast, there is still 
network traffic done. Outside the fact that it should not be done, it might 
also introduce flaky behaviors:
 * one module downloads a version of artifact A works with it, and everything 
is fine
 * 10 minutes later, another module needs artifact A, and gets a newer version, 
which has some issues, and various (test) failures will be raised

For consistency, on a multi-module build, all modules should _see_ the same 
version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
(which is very important).

 

 


> Validate/Download SNAPSHOT dependencies once
> 
>
> Key: MNG-7539
> URL: https://issues.apache.org/jira/browse/MNG-7539
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Adrian Tarau
>Priority: Critical
>
> Building an unreleased multi-module project (30-40 modules) that depends on 
> various other unreleased modules puts significant pressure on the Maven 
> Repository (a local Nexus instance), and artifact resolution could slow down 
> the build 2x-3x.
> I do acknowledge that it is the job of the repository to cache and serve 
> those responses fast, and for some reason, sometimes it slows down without an 
> apparent reason.
> However, the whole build process will be faster if Maven validates a SNAPSHOT 
> once for multi-module (when the dependency is reached the first time) and 
> then use that version. Even if Maven Repository is relative fast, there is 
> still network traffic done. Outside the fact that it should not be done, it 
> might also introduce flaky behaviors:
>  * one module downloads a version of artifact A, works with it, and 
> everything is fine
>  * 10 minutes later, another module needs artifact A and gets a newer 
> version, which has some issues, and various (test) failures will be raised
> For consistency, on a multi-module build, all modules should _see_ the same 
> version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
> (which is very important).
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972084891


##
src/main/java/org/apache/maven/buildcache/checksum/MavenProjectInput.java:
##
@@ -180,9 +182,21 @@ public MavenProjectInput( MavenProject project,
 {
 if ( propertyName.startsWith( CACHE_EXCLUDE_NAME ) )
 {
+String propertyValue = properties.getProperty( propertyName );
+Path path = Paths.get( propertyValue );
+filteredOutPaths.add( path );
+if ( LOGGER.isDebugEnabled() )
+{
+LOGGER.debug( "Adding an excludePath from property '{}', 
values is '{}', path is '{}' ",
+propertyName, propertyValue, path );
+}
+
 filteredOutPaths.add( Paths.get( properties.getProperty( 
propertyName ) ) );

Review Comment:
   @AlexanderAshitkin  thanks, fixed



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605386#comment-17605386
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972084891


##
src/main/java/org/apache/maven/buildcache/checksum/MavenProjectInput.java:
##
@@ -180,9 +182,21 @@ public MavenProjectInput( MavenProject project,
 {
 if ( propertyName.startsWith( CACHE_EXCLUDE_NAME ) )
 {
+String propertyValue = properties.getProperty( propertyName );
+Path path = Paths.get( propertyValue );
+filteredOutPaths.add( path );
+if ( LOGGER.isDebugEnabled() )
+{
+LOGGER.debug( "Adding an excludePath from property '{}', 
values is '{}', path is '{}' ",
+propertyName, propertyValue, path );
+}
+
 filteredOutPaths.add( Paths.get( properties.getProperty( 
propertyName ) ) );

Review Comment:
   @AlexanderAshitkin  thanks, fixed





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972086104


##
src/main/java/org/apache/maven/buildcache/BuildCacheMojosExecutionStrategy.java:
##
@@ -96,6 +97,7 @@ public void execute( List mojoExecutions,
 // execute clean bound goals before restoring to not 
interfere/slowdown clean
 CacheState cacheState = DISABLED;
 CacheResult result = CacheResult.empty();
+boolean skipCacheLookup = cacheConfig.isSkipLookup() || 
MavenProjectInput.shouldSkipCacheLookup( project );

Review Comment:
   @AlexanderAshitkin renamed



-- 
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] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605389#comment-17605389
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972086104


##
src/main/java/org/apache/maven/buildcache/BuildCacheMojosExecutionStrategy.java:
##
@@ -96,6 +97,7 @@ public void execute( List mojoExecutions,
 // execute clean bound goals before restoring to not 
interfere/slowdown clean
 CacheState cacheState = DISABLED;
 CacheResult result = CacheResult.empty();
+boolean skipCacheLookup = cacheConfig.isSkipLookup() || 
MavenProjectInput.shouldSkipCacheLookup( project );

Review Comment:
   @AlexanderAshitkin renamed





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605391#comment-17605391
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972087439


##
src/main/java/org/apache/maven/buildcache/BuildCacheMojosExecutionStrategy.java:
##
@@ -104,9 +106,9 @@ public void execute( List mojoExecutions,
 mojoExecutionRunner.run( mojoExecution );
 }
 cacheState = cacheConfig.initialize();
-if ( cacheState == INITIALIZED )
+if ( cacheState == INITIALIZED || skipCacheLookup )
 {
-result = cacheController.findCachedBuild( session, project, 
mojoExecutions );
+result = cacheController.findCachedBuild( session, project, 
mojoExecutions, skipCacheLookup );

Review Comment:
   @AlexanderAshitkin renamed to skipCache





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972087439


##
src/main/java/org/apache/maven/buildcache/BuildCacheMojosExecutionStrategy.java:
##
@@ -104,9 +106,9 @@ public void execute( List mojoExecutions,
 mojoExecutionRunner.run( mojoExecution );
 }
 cacheState = cacheConfig.initialize();
-if ( cacheState == INITIALIZED )
+if ( cacheState == INITIALIZED || skipCacheLookup )
 {
-result = cacheController.findCachedBuild( session, project, 
mojoExecutions );
+result = cacheController.findCachedBuild( session, project, 
mojoExecutions, skipCacheLookup );

Review Comment:
   @AlexanderAshitkin renamed to skipCache



-- 
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-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972089001


##
src/main/java/org/apache/maven/buildcache/CacheControllerImpl.java:
##
@@ -153,37 +154,50 @@ public CacheControllerImpl(
 @Override
 @Nonnull
 public CacheResult findCachedBuild( MavenSession session, MavenProject 
project,
-List mojoExecutions )
+List mojoExecutions, boolean skipLookup )
 {
 final String highestRequestPhase = CacheUtils.getLast( mojoExecutions 
).getLifecyclePhase();
 if ( !lifecyclePhasesHelper.isLaterPhaseThanClean( highestRequestPhase 
) )
 {
 return empty();
 }
 
-LOGGER.info( "Attempting to restore project from build cache" );
+String projectName = getVersionlessProjectKey( project );
 
 ProjectsInputInfo inputInfo = projectInputCalculator.calculateInput( 
project );
 
 final CacheContext context = new CacheContext( project, inputInfo, 
session );
-// remote build first
-CacheResult result = findCachedBuild( mojoExecutions, context );
 
-if ( !result.isSuccess() && result.getContext() != null )
+CacheResult result = empty( context );
+if ( !skipLookup )
 {
-LOGGER.debug( "Remote cache is incomplete or missing, trying local 
build" );
 
-CacheResult localBuild = findLocalBuild( mojoExecutions, context );
+LOGGER.info( "Attempting to restore project {} from build cache", 
projectName );
 
-if ( localBuild.isSuccess() || ( localBuild.isPartialSuccess() && 
!result.isPartialSuccess() ) )
-{
-result = localBuild;
-}
-else
+// remote build first

Review Comment:
   Thus is not my comment - just part of code by @gnodet that I've moved inside 
a block



-- 
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-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972089001


##
src/main/java/org/apache/maven/buildcache/CacheControllerImpl.java:
##
@@ -153,37 +154,50 @@ public CacheControllerImpl(
 @Override
 @Nonnull
 public CacheResult findCachedBuild( MavenSession session, MavenProject 
project,
-List mojoExecutions )
+List mojoExecutions, boolean skipLookup )
 {
 final String highestRequestPhase = CacheUtils.getLast( mojoExecutions 
).getLifecyclePhase();
 if ( !lifecyclePhasesHelper.isLaterPhaseThanClean( highestRequestPhase 
) )
 {
 return empty();
 }
 
-LOGGER.info( "Attempting to restore project from build cache" );
+String projectName = getVersionlessProjectKey( project );
 
 ProjectsInputInfo inputInfo = projectInputCalculator.calculateInput( 
project );
 
 final CacheContext context = new CacheContext( project, inputInfo, 
session );
-// remote build first
-CacheResult result = findCachedBuild( mojoExecutions, context );
 
-if ( !result.isSuccess() && result.getContext() != null )
+CacheResult result = empty( context );
+if ( !skipLookup )
 {
-LOGGER.debug( "Remote cache is incomplete or missing, trying local 
build" );
 
-CacheResult localBuild = findLocalBuild( mojoExecutions, context );
+LOGGER.info( "Attempting to restore project {} from build cache", 
projectName );
 
-if ( localBuild.isSuccess() || ( localBuild.isPartialSuccess() && 
!result.isPartialSuccess() ) )
-{
-result = localBuild;
-}
-else
+// remote build first

Review Comment:
   This is not my comment - just part of code by @gnodet that I've moved inside 
a block



-- 
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] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605392#comment-17605392
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972089001


##
src/main/java/org/apache/maven/buildcache/CacheControllerImpl.java:
##
@@ -153,37 +154,50 @@ public CacheControllerImpl(
 @Override
 @Nonnull
 public CacheResult findCachedBuild( MavenSession session, MavenProject 
project,
-List mojoExecutions )
+List mojoExecutions, boolean skipLookup )
 {
 final String highestRequestPhase = CacheUtils.getLast( mojoExecutions 
).getLifecyclePhase();
 if ( !lifecyclePhasesHelper.isLaterPhaseThanClean( highestRequestPhase 
) )
 {
 return empty();
 }
 
-LOGGER.info( "Attempting to restore project from build cache" );
+String projectName = getVersionlessProjectKey( project );
 
 ProjectsInputInfo inputInfo = projectInputCalculator.calculateInput( 
project );
 
 final CacheContext context = new CacheContext( project, inputInfo, 
session );
-// remote build first
-CacheResult result = findCachedBuild( mojoExecutions, context );
 
-if ( !result.isSuccess() && result.getContext() != null )
+CacheResult result = empty( context );
+if ( !skipLookup )
 {
-LOGGER.debug( "Remote cache is incomplete or missing, trying local 
build" );
 
-CacheResult localBuild = findLocalBuild( mojoExecutions, context );
+LOGGER.info( "Attempting to restore project {} from build cache", 
projectName );
 
-if ( localBuild.isSuccess() || ( localBuild.isPartialSuccess() && 
!result.isPartialSuccess() ) )
-{
-result = localBuild;
-}
-else
+// remote build first

Review Comment:
   Thus is not my comment - just part of code by @gnodet that I've moved inside 
a block





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605393#comment-17605393
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972089001


##
src/main/java/org/apache/maven/buildcache/CacheControllerImpl.java:
##
@@ -153,37 +154,50 @@ public CacheControllerImpl(
 @Override
 @Nonnull
 public CacheResult findCachedBuild( MavenSession session, MavenProject 
project,
-List mojoExecutions )
+List mojoExecutions, boolean skipLookup )
 {
 final String highestRequestPhase = CacheUtils.getLast( mojoExecutions 
).getLifecyclePhase();
 if ( !lifecyclePhasesHelper.isLaterPhaseThanClean( highestRequestPhase 
) )
 {
 return empty();
 }
 
-LOGGER.info( "Attempting to restore project from build cache" );
+String projectName = getVersionlessProjectKey( project );
 
 ProjectsInputInfo inputInfo = projectInputCalculator.calculateInput( 
project );
 
 final CacheContext context = new CacheContext( project, inputInfo, 
session );
-// remote build first
-CacheResult result = findCachedBuild( mojoExecutions, context );
 
-if ( !result.isSuccess() && result.getContext() != null )
+CacheResult result = empty( context );
+if ( !skipLookup )
 {
-LOGGER.debug( "Remote cache is incomplete or missing, trying local 
build" );
 
-CacheResult localBuild = findLocalBuild( mojoExecutions, context );
+LOGGER.info( "Attempting to restore project {} from build cache", 
projectName );
 
-if ( localBuild.isSuccess() || ( localBuild.isPartialSuccess() && 
!result.isPartialSuccess() ) )
-{
-result = localBuild;
-}
-else
+// remote build first

Review Comment:
   This is not my comment - just part of code by @gnodet that I've moved inside 
a block





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972094842


##
src/main/java/org/apache/maven/buildcache/DefaultNormalizedModelProvider.java:
##
@@ -123,10 +127,16 @@ private List normalizePlugins( List 
plugins )
 {
 Plugin copy = plugin.clone();
 List excludeProperties = 
cacheConfig.getEffectivePomExcludeProperties( copy );
-removeBlacklistedAttributes( copy.getConfiguration(), 
excludeProperties );

Review Comment:
   @AlexanderAshitkin the code is still there - just after debug output



-- 
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] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605396#comment-17605396
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972094842


##
src/main/java/org/apache/maven/buildcache/DefaultNormalizedModelProvider.java:
##
@@ -123,10 +127,16 @@ private List normalizePlugins( List 
plugins )
 {
 Plugin copy = plugin.clone();
 List excludeProperties = 
cacheConfig.getEffectivePomExcludeProperties( copy );
-removeBlacklistedAttributes( copy.getConfiguration(), 
excludeProperties );

Review Comment:
   @AlexanderAshitkin the code is still there - just after debug output





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] AlexanderAshitkin commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

AlexanderAshitkin commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972112153


##
src/site/markdown/parameters.md:
##
@@ -32,7 +32,7 @@ This documents contains various configuration parameters 
supported by cache engi
 | `-Dmaven.build.cache.lazyRestore=(true/false)` | Restore 
artifacts from remote cache lazily  
 | Performance optimization |
 | `-Dmaven.build.cache.restoreGeneratedSources=(true/false)` | Do not restore 
generated sources and directly attached files   
  | Performance optimization |
 | `-Dmaven.build.cache.alwaysRunPlugins=`   | Comma seprated 
list of plugins to always run regardless of cache state. An example: 
`maven-deploy-plugin:*,maven-install-plugin:install` | Remote cache 
setup/tuning/troubleshooting |
-| `-Dmaven.build.cache.skipLookup=(true/false)`  | Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|
+| `-Dmaven.build.cache.skip=(true/false)`| Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|

Review Comment:
   small typo. maching -> matching



-- 
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] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605403#comment-17605403
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

AlexanderAshitkin commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972112153


##
src/site/markdown/parameters.md:
##
@@ -32,7 +32,7 @@ This documents contains various configuration parameters 
supported by cache engi
 | `-Dmaven.build.cache.lazyRestore=(true/false)` | Restore 
artifacts from remote cache lazily  
 | Performance optimization |
 | `-Dmaven.build.cache.restoreGeneratedSources=(true/false)` | Do not restore 
generated sources and directly attached files   
  | Performance optimization |
 | `-Dmaven.build.cache.alwaysRunPlugins=`   | Comma seprated 
list of plugins to always run regardless of cache state. An example: 
`maven-deploy-plugin:*,maven-install-plugin:install` | Remote cache 
setup/tuning/troubleshooting |
-| `-Dmaven.build.cache.skipLookup=(true/false)`  | Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|
+| `-Dmaven.build.cache.skip=(true/false)`| Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|

Review Comment:
   small typo. maching -> matching





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972132304


##
src/main/java/org/apache/maven/buildcache/checksum/MavenProjectInput.java:
##
@@ -180,9 +182,21 @@ public MavenProjectInput( MavenProject project,
 {
 if ( propertyName.startsWith( CACHE_EXCLUDE_NAME ) )
 {
+String propertyValue = properties.getProperty( propertyName );
+Path path = Paths.get( propertyValue );
+filteredOutPaths.add( path );
+if ( LOGGER.isDebugEnabled() )
+{
+LOGGER.debug( "Adding an excludePath from property '{}', 
values is '{}', path is '{}' ",
+propertyName, propertyValue, path );
+}
+
 filteredOutPaths.add( Paths.get( properties.getProperty( 
propertyName ) ) );
 }
 }
+CacheUtils.debugPrintCollection( LOGGER, filteredOutPaths,
+"List of excluded paths (checked either by fileName or by 
startsWith prefix)",
+"Pah entry" );

Review Comment:
   @AlexanderAshitkin fixed



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605413#comment-17605413
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972132304


##
src/main/java/org/apache/maven/buildcache/checksum/MavenProjectInput.java:
##
@@ -180,9 +182,21 @@ public MavenProjectInput( MavenProject project,
 {
 if ( propertyName.startsWith( CACHE_EXCLUDE_NAME ) )
 {
+String propertyValue = properties.getProperty( propertyName );
+Path path = Paths.get( propertyValue );
+filteredOutPaths.add( path );
+if ( LOGGER.isDebugEnabled() )
+{
+LOGGER.debug( "Adding an excludePath from property '{}', 
values is '{}', path is '{}' ",
+propertyName, propertyValue, path );
+}
+
 filteredOutPaths.add( Paths.get( properties.getProperty( 
propertyName ) ) );
 }
 }
+CacheUtils.debugPrintCollection( LOGGER, filteredOutPaths,
+"List of excluded paths (checked either by fileName or by 
startsWith prefix)",
+"Pah entry" );

Review Comment:
   @AlexanderAshitkin fixed





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972138664


##
src/site/markdown/parameters.md:
##
@@ -32,6 +32,7 @@ This documents contains various configuration parameters 
supported by cache engi
 | `-Dmaven.build.cache.lazyRestore=(true/false)` | Restore 
artifacts from remote cache lazily  
 | Performance optimization |
 | `-Dmaven.build.cache.restoreGeneratedSources=(true/false)` | Do not restore 
generated sources and directly attached files   
  | Performance optimization |
 | `-Dmaven.build.cache.alwaysRunPlugins=`   | Comma seprated 
list of plugins to always run regardless of cache state. An example: 
`maven-deploy-plugin:*,maven-install-plugin:install` | Remote cache 
setup/tuning/troubleshooting |
+| `-Dmaven.build.cache.skipLookup=(true/false)`  | Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|

Review Comment:
   @AlexanderAshitkin renamed to -Dorg.maven.build.cache.skipCache



-- 
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] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605416#comment-17605416
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972138664


##
src/site/markdown/parameters.md:
##
@@ -32,6 +32,7 @@ This documents contains various configuration parameters 
supported by cache engi
 | `-Dmaven.build.cache.lazyRestore=(true/false)` | Restore 
artifacts from remote cache lazily  
 | Performance optimization |
 | `-Dmaven.build.cache.restoreGeneratedSources=(true/false)` | Do not restore 
generated sources and directly attached files   
  | Performance optimization |
 | `-Dmaven.build.cache.alwaysRunPlugins=`   | Comma seprated 
list of plugins to always run regardless of cache state. An example: 
`maven-deploy-plugin:*,maven-install-plugin:install` | Remote cache 
setup/tuning/troubleshooting |
+| `-Dmaven.build.cache.skipLookup=(true/false)`  | Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|

Review Comment:
   @AlexanderAshitkin renamed to -Dorg.maven.build.cache.skipCache





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added possibility to skip cache lookup per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972139469


##
src/main/java/org/apache/maven/buildcache/checksum/MavenProjectInput.java:
##
@@ -819,4 +833,22 @@ public int compare( Path f1, Path f2 )
 }
 }
 
+public static boolean shouldSkipCacheLookup( MavenProject project )

Review Comment:
   @AlexanderAshitkin fixed



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605417#comment-17605417
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972139469


##
src/main/java/org/apache/maven/buildcache/checksum/MavenProjectInput.java:
##
@@ -819,4 +833,22 @@ public int compare( Path f1, Path f2 )
 }
 }
 
+public static boolean shouldSkipCacheLookup( MavenProject project )

Review Comment:
   @AlexanderAshitkin fixed





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-build-cache-extension] eltsovalex commented on a diff in pull request #24: [MBUILDCACHE-22] added flag to force rebuild per project or globally

[GitBox]

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972151400


##
src/site/markdown/parameters.md:
##
@@ -32,7 +32,7 @@ This documents contains various configuration parameters 
supported by cache engi
 | `-Dmaven.build.cache.lazyRestore=(true/false)` | Restore 
artifacts from remote cache lazily  
 | Performance optimization |
 | `-Dmaven.build.cache.restoreGeneratedSources=(true/false)` | Do not restore 
generated sources and directly attached files   
  | Performance optimization |
 | `-Dmaven.build.cache.alwaysRunPlugins=`   | Comma seprated 
list of plugins to always run regardless of cache state. An example: 
`maven-deploy-plugin:*,maven-install-plugin:install` | Remote cache 
setup/tuning/troubleshooting |
-| `-Dmaven.build.cache.skipLookup=(true/false)`  | Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|
+| `-Dmaven.build.cache.skip=(true/false)`| Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|

Review Comment:
   @AlexanderAshitkin  - thx, fixed



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MBUILDCACHE-22) Add possibility to skip cache lookup

[ASF GitHub Bot (Jira)]

[ 
https://issues.apache.org/jira/browse/MBUILDCACHE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605423#comment-17605423
 ] 

ASF GitHub Bot commented on MBUILDCACHE-22:
---

eltsovalex commented on code in PR #24:
URL: 
https://github.com/apache/maven-build-cache-extension/pull/24#discussion_r972151400


##
src/site/markdown/parameters.md:
##
@@ -32,7 +32,7 @@ This documents contains various configuration parameters 
supported by cache engi
 | `-Dmaven.build.cache.lazyRestore=(true/false)` | Restore 
artifacts from remote cache lazily  
 | Performance optimization |
 | `-Dmaven.build.cache.restoreGeneratedSources=(true/false)` | Do not restore 
generated sources and directly attached files   
  | Performance optimization |
 | `-Dmaven.build.cache.alwaysRunPlugins=`   | Comma seprated 
list of plugins to always run regardless of cache state. An example: 
`maven-deploy-plugin:*,maven-install-plugin:install` | Remote cache 
setup/tuning/troubleshooting |
-| `-Dmaven.build.cache.skipLookup=(true/false)`  | Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|
+| `-Dmaven.build.cache.skip=(true/false)`| Skip looking up 
artifacts in caches. Does not affect writing artifacts to caches, disables only 
reading when set to `true`   | May be used to trigger a forced 
rebuild when maching artifatcs do exist in caches|

Review Comment:
   @AlexanderAshitkin  - thx, fixed





> Add possibility to skip cache lookup
> 
>
> Key: MBUILDCACHE-22
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-22
> Project: Maven Build Cache Extension
>  Issue Type: New Feature
>  Components: remote build cache
>Affects Versions: 1.0.0-alpha
>Reporter: Alexander Eltsov
>Priority: Major
>  Labels: pull-request-available
>
> Add ability to skip cache lookup for a particular module or whole project 
> (required to get some modules always built e.g. via a profile - e.g. I have 
> some additional artifacts published by CI).
> Alternatively it allows an easy "force" rebuild of a whole project
> The difference with not using cache is that results are put into cache, just 
> current matching versions are not taken from caches



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605442#comment-17605442
 ] 

Michael Osipov commented on MRELEASE-1103:
--

Are you able to bisect down to the offending commit?

> decryption of server password in settings.xml failed (works with 2.5.3)
> ---
>
> Key: MRELEASE-1103
> URL: https://issues.apache.org/jira/browse/MRELEASE-1103
> Project: Maven Release Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M6
>Reporter: Robert Seidel
>Priority: Major
>
> A server section was defined in the settings.xml at 
>  with id, username and password to connect to a 
> Bitbucket server.
> In the pom.xml the id was referenced in the properties via project.scm.id.
> With 2.5.3 the build is running fine, but with 3.0.06-M6 the following 
> happens:
> *11:35:40* [INFO] [WARNING] The requested profile "distribute" could not be 
> activated because it does not exist.
> *11:35:40* [INFO] 11/17 prepare:scm-commit-release
> *11:35:40* [INFO] Checking in modified POMs...
> *11:35:40* [WARNING] Failed to decrypt password/passphrase for server 
> bitbucket-prod, using auth token as is: decrypt failed
> and in the aftermath:
> *11:35:41* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M6:prepare (default-cli) 
> on project ExamplePom: Unable to commit files
> *11:35:41* [ERROR] Provider message:
> *11:35:41* [ERROR] The git-push command failed.
> *11:35:41* [ERROR] Command output:
> *11:35:41* [ERROR] fatal: Authentication failed for 
> '[https://prod.bitbucket/scm/cp/examplepom.git/|https://git.aeb.com/bitbucket/scm/cp/aebparentpom.git/]'
>  
> JDK used was Adoptium 17 (but with 11 the same problem occured).
> Maven used was 3.8.6.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7539) Validate/Download SNAPSHOT dependencies once

[Michael Osipov (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605524#comment-17605524
 ] 

Michael Osipov commented on MNG-7539:
-

You should try to fiddle with the repo policy for updating metadata. That might 
be too short for you.

> Validate/Download SNAPSHOT dependencies once
> 
>
> Key: MNG-7539
> URL: https://issues.apache.org/jira/browse/MNG-7539
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Adrian Tarau
>Priority: Critical
>
> Building an unreleased multi-module project (30-40 modules) that depends on 
> various other unreleased modules puts significant pressure on the Maven 
> Repository (a local Nexus instance), and artifact resolution could slow down 
> the build 2x-3x.
> I do acknowledge that it is the job of the repository to cache and serve 
> those responses fast, and for some reason, sometimes it slows down without an 
> apparent reason.
> However, the whole build process will be faster if Maven validates a SNAPSHOT 
> once for multi-module (when the dependency is reached the first time) and 
> then use that version. Even if Maven Repository is relative fast, there is 
> still network traffic done. Outside the fact that it should not be done, it 
> might also introduce flaky behaviors:
>  * one module downloads a version of artifact A, works with it, and 
> everything is fine
>  * 10 minutes later, another module needs artifact A and gets a newer 
> version, which has some issues, and various (test) failures will be raised
> For consistency, on a multi-module build, all modules should _see_ the same 
> version of a SNAPSHOT artifact. It will be faster, and it will be consistent 
> (which is very important).
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request, #249: Bump jettyVersion from 9.4.48.v20220622 to 9.4.49.v20220914

[GitBox]

dependabot[bot] opened a new pull request, #249:
URL: https://github.com/apache/maven-dependency-plugin/pull/249

   Bumps `jettyVersion` from 9.4.48.v20220622 to 9.4.49.v20220914.
   Updates `jetty-server` from 9.4.48.v20220622 to 9.4.49.v20220914
   
   Release notes
   Sourced from https://github.com/eclipse/jetty.project/releases";>jetty-server's 
releases.
   
   9.4.49.v20220914
   Changelog
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - getRequestURL can append "null" if 
getRequestURI is unspecified in an authority-form 
request-target
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8493";>#8493
 - Review HTTP client feature setRemoveIdleDestinations
   
   Dependencies
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8253";>#8253
 - Bump google-cloud-datastore to 2.9.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8233";>#8233
 - Bump jna to 5.12.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8242";>#8242
 - Bump mariadb-java-client to 3.0.6
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8238";>#8238
 - Bump maven-enforcer-plugin to 3.1.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8230";>#8230
 - Bump maven.version to 3.8.6
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8246";>#8246
 - Bump org.eclipse.osgi to 3.18.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8245";>#8245
 - Bump testcontainers.version to 1.17.3
   
   
   
   
   Commits
   
   https://github.com/eclipse/jetty.project/commit/4231a3b2e4cb8548a412a789936d640a97b1aa0a";>4231a3b
 Updating to version 9.4.49.v20220914
   https://github.com/eclipse/jetty.project/commit/b32d739a1d158c270b98c300e9b84af245bfde2d";>b32d739
 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8579";>#8579
 from eclipse/fix/jetty-9.4.x-abstractproxy-null-requ...
   https://github.com/eclipse/jetty.project/commit/5944ff4b3a0aa0b9c2a5ad4048fd497e6d7a23cf";>5944ff4
 Issue https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - Changes from review
   https://github.com/eclipse/jetty.project/commit/48c16deb21efd67d369675a9126e68459fdc9408";>48c16de
 Issue https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - test both request URL/URI results
   https://github.com/eclipse/jetty.project/commit/d3c7ee3d71c57a32336481df7246c49ff51282b1";>d3c7ee3
 Issue https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - restore backward compat of getRequestURL and getRequestURI when...
   https://github.com/eclipse/jetty.project/commit/06f2fa41ddd83236a8484572e93fb3363c2084ad";>06f2fa4
 Jetty 9.4.x : fix client remove idle destinations (https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8495";>#8495)
   https://github.com/eclipse/jetty.project/commit/940455b01274d957075166d53e9b908b27ed7ad6";>940455b
 https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8414";>#8414:
 fix drainTo when head == tail but the queue isn't empty
   https://github.com/eclipse/jetty.project/commit/a846f4fc9dc734d40084f58af44ac925c0ba0aa8";>a846f4f
 Updating for published CVES (https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8273";>#8273)
   https://github.com/eclipse/jetty.project/commit/064682b4ce57282e49a80a64b6d7a7a66fb47b28";>064682b
 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8253";>#8253
 from eclipse/dependabot/maven/jetty-9.4.x/com.google...
   https://github.com/eclipse/jetty.project/commit/7b4057142ed44a29849f24a2572d2649e9458921";>7b40571
 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8245";>#8245
 from eclipse/dependabot/maven/jetty-9.4.x/testcontai...
   Additional commits viewable in https://github.com/eclipse/jetty.project/compare/jetty-9.4.48.v20220622...jetty-9.4.49.v20220914";>compare
 view
   
   
   
   
   Updates `jetty-util` from 9.4.48.v20220622 to 9.4.49.v20220914
   
   Release notes
   Sourced from https://github.com/eclipse/jetty.project/releases";>jetty-util's 
releases.
   
   9.4.49.v20220914
   Changelog
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - getRequestURL can append "null" if 
getRequestURI is unspecified in an authority-form 
request-target
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8493";>#8493
 - Review HTTP client feature setRemoveIdleDestinations
   
   Dependencies
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8253";>#8253
 - Bump google-cloud-datastore to 2.9.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8233";>#8233
 - Bump jna to 5.12.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8242";>#8242
 - Bump maria

[GitHub] [maven-gh-actions-shared] dependabot[bot] opened a new pull request, #58: Bump release-drafter/release-drafter from 5.20.1 to 5.21.0

[GitBox]

dependabot[bot] opened a new pull request, #58:
URL: https://github.com/apache/maven-gh-actions-shared/pull/58

   Bumps 
[release-drafter/release-drafter](https://github.com/release-drafter/release-drafter)
 from 5.20.1 to 5.21.0.
   
   Release notes
   Sourced from https://github.com/release-drafter/release-drafter/releases";>release-drafter/release-drafter's
 releases.
   
   v5.21.0
   What's Changed
   New
   
   fetch 100 labels for pull requests instead of 10 (https://github-redirect.dependabot.com/release-drafter/release-drafter/issues/1220";>#1220)
 https://github.com/matoubidou";>@​matoubidou
   
   Full Changelog: https://github.com/release-drafter/release-drafter/compare/v6.0.0-beta.1...v5.21.0";>https://github.com/release-drafter/release-drafter/compare/v6.0.0-beta.1...v5.21.0
   
   
   
   Commits
   
   https://github.com/release-drafter/release-drafter/commit/df69d584deac33d8569990cb6413f82447181076";>df69d58
 v5.21.0
   https://github.com/release-drafter/release-drafter/commit/ecbbed96e59dfeb4f433d84fbdca2b1e01887d62";>ecbbed9
 fetch 100 labels for pull requests instead of 10 (https://github-redirect.dependabot.com/release-drafter/release-drafter/issues/1220";>#1220)
   See full diff in https://github.com/release-drafter/release-drafter/compare/v5.20.1...v5.21.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=release-drafter/release-drafter&package-manager=github_actions&previous-version=5.20.1&new-version=5.21.0)](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] (MASSEMBLY-941) file permissions removed during assembly:single since 3.2.0

[Christopher Tubbs (Jira)]

[ 
https://issues.apache.org/jira/browse/MASSEMBLY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605585#comment-17605585
 ] 

Christopher Tubbs commented on MASSEMBLY-941:
-

I'm just going to ping this one once again, as I'm updating to the latest 
Apache parent POM (27), and maven-assembly-plugin is now upgraded to 3.4.1 with 
that, and this is still broken. So, we're still stuck on 3.1.1, the last 
version where file permissions were preserved correctly by this plugin.

> file permissions removed during assembly:single since 3.2.0
> ---
>
> Key: MASSEMBLY-941
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-941
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>  Components: permissions
>Affects Versions: 3.2.0, 3.3.0
>Reporter: Christopher Tubbs
>Priority: Critical
>
> Since 3.2.0, existing file permissions seem to be ignored when creating a 
> tarball assembly, and files stored in the assembly do not have their original 
> file permissions preserved.
> Using version 3.1.1 of this plugin and earlier, when creating a tar.gz, 
> existing file permissions are normally preserved. This is now broken in 
> 3.2.0, unless the component descriptor explicitly sets the fileModes.
> This was discovered trying to prepare a release candidate for Apache Accumulo 
> using the apache-23.pom parent POM's predefined `source-release-tar` 
> descriptor using the `single` goal. We noticed that the resulting 
> source-release tarball had stripped all the executable permissions from our 
> scripts, instead of preserving them. This makes the resulting source release 
> more difficult to build from source.
> A source-release assembly, and any other assembly that does not specify the 
> file permissions explicitly, should preserve the existing file permissions, 
> just as it used to with 3.1.1 and earlier.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [maven-gh-actions-shared] dependabot[bot] opened a new pull request, #59: Bump release-drafter/release-drafter from 5.20.1 to 5.21.0

[GitBox]

dependabot[bot] opened a new pull request, #59:
URL: https://github.com/apache/maven-gh-actions-shared/pull/59

   Bumps 
[release-drafter/release-drafter](https://github.com/release-drafter/release-drafter)
 from 5.20.1 to 5.21.0.
   
   Release notes
   Sourced from https://github.com/release-drafter/release-drafter/releases";>release-drafter/release-drafter's
 releases.
   
   v5.21.0
   What's Changed
   New
   
   fetch 100 labels for pull requests instead of 10 (https://github-redirect.dependabot.com/release-drafter/release-drafter/issues/1220";>#1220)
 https://github.com/matoubidou";>@​matoubidou
   
   Full Changelog: https://github.com/release-drafter/release-drafter/compare/v6.0.0-beta.1...v5.21.0";>https://github.com/release-drafter/release-drafter/compare/v6.0.0-beta.1...v5.21.0
   
   
   
   Commits
   
   https://github.com/release-drafter/release-drafter/commit/df69d584deac33d8569990cb6413f82447181076";>df69d58
 v5.21.0
   https://github.com/release-drafter/release-drafter/commit/ecbbed96e59dfeb4f433d84fbdca2b1e01887d62";>ecbbed9
 fetch 100 labels for pull requests instead of 10 (https://github-redirect.dependabot.com/release-drafter/release-drafter/issues/1220";>#1220)
   See full diff in https://github.com/release-drafter/release-drafter/compare/v5.20.1...v5.21.0";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=release-drafter/release-drafter&package-manager=github_actions&previous-version=5.20.1&new-version=5.21.0)](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-javadoc-plugin] dependabot[bot] opened a new pull request, #163: Bump jetty.version from 9.4.43.v20210629 to 11.0.12

[GitBox]

dependabot[bot] opened a new pull request, #163:
URL: https://github.com/apache/maven-javadoc-plugin/pull/163

   Bumps `jetty.version` from 9.4.43.v20210629 to 11.0.12.
   Updates `jetty-server` from 9.4.43.v20210629 to 11.0.12
   
   Release notes
   Sourced from https://github.com/eclipse/jetty.project/releases";>jetty-server's 
releases.
   
   11.0.12
   Special Thanks to the following Eclipse Jetty community members
   
   https://github.com/MoonLord-LM";>@​MoonLord-LM 
(MoonLord-LM)
   
   Changelog
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8497";>#8497
 - jetty-bom/11.0.11 depends on 
jetty-slf4j-impl/10.0.8-SNAPSHOT that cause 404 error (https://github.com/MoonLord-LM";>@​MoonLord-LM)
   
   Dependencies
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8389";>#8389
 - Bump avro to 1.11.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8239";>#8239
 - Bump checkstyle to 10.3.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8300";>#8300
 - Bump google-cloud-datastore to 2.10.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8508";>#8508
 - Bump grpc-core to 1.49.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8249";>#8249
 - Bump jakarta.annotation-api to 2.1.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8506";>#8506
 - Bump jboss-threads to 3.5.0.Final
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8254";>#8254
 - Bump jna-jpms to 5.12.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8529";>#8529
 - Bump mariadb-java-client to 3.0.7
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8371";>#8371
 - Bump maven-assembly-plugin to 3.4.2
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8520";>#8520
 - Bump maven-checkstyle-plugin to 3.2.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8248";>#8248
 - Bump maven-enforcer-plugin to 3.1.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8377";>#8377
 - Bump maven-install-plugin to 3.0.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8528";>#8528
 - Bump maven-javadoc-plugin to 3.4.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8368";>#8368
 - Bump maven-resources-plugin to 3.3.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8244";>#8244
 - Bump maven.version to 3.8.6
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8308";>#8308
 - Bump spotbugs-maven-plugin to 4.7.1.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8309";>#8309
 - Bump tycho-p2-repository-plugin to 2.7.4
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8369";>#8369
 - Bump wildfly-elytron to 1.20.0.Final
   
   11.0.11
   Special Thanks to the following Eclipse Jetty community members
   
   https://github.com/cstamas";>@​cstamas (Tamas 
Cservenak)
   
   Critical Fix
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8184";>#8184
 - All suffix globs except first fail to match if path has . 
character in prefix section
   
   Changelog
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8187";>#8187
 - Fix test-distribution classpath re resolver (https://github.com/cstamas";>@​cstamas)
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8175";>#8175
 - Removing invalid maxConnections references
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8163";>#8163
 - RegexPathSpec documentation and MatchedPath improvements
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8162";>#8162
 - Migrate code from jetty-util Logger to slf4j Logger
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8161";>#8161
 - Improve SSLConnection buffers handling
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8155";>#8155
 - Use static exceptions for closing websocket flushers and in 
ContentProducer
   
   11.0.10
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/eclipse/jetty.project/commit/d5b8c29485f5f56a14be5f20c2ccce81b93c";>d5b8c29
 Updating to version 11.0.12
   https://github.com/eclipse/jetty.project/commit/e46f0a62b2d308551106f05fca3db285955f51b3";>e46f0a6
 Merge github.com:eclipse/jetty.project into jetty-11.0.x
   https://github.com/eclipse/jetty.project/commit/2a49f8665847239a635f382511d40c1682dea90a";>2a49f86
 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8580";>#8580
 from eclipse/fix/jetty-10.0.x-proxy-rewrite-null-uri
   https://github.com/eclipse/jetty.project/commit/8eba1c9924cbb3578f7c6600afecd26864c8f3eb";>8eba1c9
 Issue https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - Changes from review
   ht

[GitHub] [maven-javadoc-plugin] dependabot[bot] commented on pull request #154: Bump jetty-server from 9.4.43.v20210629 to 10.0.10

[GitBox]

dependabot[bot] commented on PR #154:
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/154#issuecomment-1248869754

   Superseded by #163.


-- 
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 #154: Bump jetty-server from 9.4.43.v20210629 to 10.0.10

[GitBox]

dependabot[bot] closed pull request #154: Bump jetty-server from 
9.4.43.v20210629 to 10.0.10
URL: https://github.com/apache/maven-javadoc-plugin/pull/154


-- 
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 #153: Bump jetty.version from 9.4.43.v20210629 to 11.0.11

[GitBox]

dependabot[bot] commented on PR #153:
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/153#issuecomment-1248869771

   Superseded by #163.


-- 
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 #153: Bump jetty.version from 9.4.43.v20210629 to 11.0.11

[GitBox]

dependabot[bot] closed pull request #153: Bump jetty.version from 
9.4.43.v20210629 to 11.0.11
URL: https://github.com/apache/maven-javadoc-plugin/pull/153


-- 
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, #103: Bump jettyVersion from 9.4.48.v20220622 to 11.0.12

[GitBox]

dependabot[bot] opened a new pull request, #103:
URL: https://github.com/apache/maven-site-plugin/pull/103

   Bumps `jettyVersion` from 9.4.48.v20220622 to 11.0.12.
   Updates `jetty-server` from 9.4.48.v20220622 to 11.0.12
   
   Release notes
   Sourced from https://github.com/eclipse/jetty.project/releases";>jetty-server's 
releases.
   
   11.0.12
   Special Thanks to the following Eclipse Jetty community members
   
   https://github.com/MoonLord-LM";>@​MoonLord-LM 
(MoonLord-LM)
   
   Changelog
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8497";>#8497
 - jetty-bom/11.0.11 depends on 
jetty-slf4j-impl/10.0.8-SNAPSHOT that cause 404 error (https://github.com/MoonLord-LM";>@​MoonLord-LM)
   
   Dependencies
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8389";>#8389
 - Bump avro to 1.11.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8239";>#8239
 - Bump checkstyle to 10.3.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8300";>#8300
 - Bump google-cloud-datastore to 2.10.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8508";>#8508
 - Bump grpc-core to 1.49.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8249";>#8249
 - Bump jakarta.annotation-api to 2.1.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8506";>#8506
 - Bump jboss-threads to 3.5.0.Final
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8254";>#8254
 - Bump jna-jpms to 5.12.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8529";>#8529
 - Bump mariadb-java-client to 3.0.7
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8371";>#8371
 - Bump maven-assembly-plugin to 3.4.2
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8520";>#8520
 - Bump maven-checkstyle-plugin to 3.2.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8248";>#8248
 - Bump maven-enforcer-plugin to 3.1.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8377";>#8377
 - Bump maven-install-plugin to 3.0.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8528";>#8528
 - Bump maven-javadoc-plugin to 3.4.1
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8368";>#8368
 - Bump maven-resources-plugin to 3.3.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8244";>#8244
 - Bump maven.version to 3.8.6
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8308";>#8308
 - Bump spotbugs-maven-plugin to 4.7.1.0
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8309";>#8309
 - Bump tycho-p2-repository-plugin to 2.7.4
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8369";>#8369
 - Bump wildfly-elytron to 1.20.0.Final
   
   11.0.11
   Special Thanks to the following Eclipse Jetty community members
   
   https://github.com/cstamas";>@​cstamas (Tamas 
Cservenak)
   
   Critical Fix
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8184";>#8184
 - All suffix globs except first fail to match if path has . 
character in prefix section
   
   Changelog
   
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8187";>#8187
 - Fix test-distribution classpath re resolver (https://github.com/cstamas";>@​cstamas)
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8175";>#8175
 - Removing invalid maxConnections references
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8163";>#8163
 - RegexPathSpec documentation and MatchedPath improvements
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8162";>#8162
 - Migrate code from jetty-util Logger to slf4j Logger
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8161";>#8161
 - Improve SSLConnection buffers handling
   https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8155";>#8155
 - Use static exceptions for closing websocket flushers and in 
ContentProducer
   
   11.0.10
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/eclipse/jetty.project/commit/d5b8c29485f5f56a14be5f20c2ccce81b93c";>d5b8c29
 Updating to version 11.0.12
   https://github.com/eclipse/jetty.project/commit/e46f0a62b2d308551106f05fca3db285955f51b3";>e46f0a6
 Merge github.com:eclipse/jetty.project into jetty-11.0.x
   https://github.com/eclipse/jetty.project/commit/2a49f8665847239a635f382511d40c1682dea90a";>2a49f86
 Merge pull request https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8580";>#8580
 from eclipse/fix/jetty-10.0.x-proxy-rewrite-null-uri
   https://github.com/eclipse/jetty.project/commit/8eba1c9924cbb3578f7c6600afecd26864c8f3eb";>8eba1c9
 Issue https://github-redirect.dependabot.com/eclipse/jetty.project/issues/8578";>#8578
 - Changes from review
   https:

[GitHub] [maven-indexer] dependabot[bot] opened a new pull request, #244: Bump version.spring from 5.3.22 to 5.3.23

[GitBox]

dependabot[bot] opened a new pull request, #244:
URL: https://github.com/apache/maven-indexer/pull/244

   Bumps `version.spring` from 5.3.22 to 5.3.23.
   Updates `spring-beans` from 5.3.22 to 5.3.23
   
   Release notes
   Sourced from https://github.com/spring-projects/spring-framework/releases";>spring-beans's
 releases.
   
   v5.3.23
   :star: New Features
   
   Introduce AnnotationUtils.isSynthesizedAnnotation(Annotation) https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29054";>#29054
   Introduce createContext() factory method in 
AbstractGenericWebContextLoader https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28983";>#28983
   Support TreeSet collection type in CollectionFactory.createCollection() 
without using reflection https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28949";>#28949
   Document when RequestEntity.getUrl() throws an 
UnsupportedOperationException https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28930";>#28930
   Deprecate NestedIOException https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28929";>#28929
   Make isConnected() in WebSocketConnectionManager public https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28785";>#28785
   Expose headers from STOMP RECEIPT frame to registered callbacks https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28715";>#28715
   Make WebClientException serializable https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28321";>#28321
   
   :lady_beetle: Bug Fixes
   
   Ordering inconsistency with beans defined in parent context https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29105";>#29105
   RelativeRedirectResponseWrapper does not commit response in sendRedirect 
https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29050";>#29050
   MockServerContainerContextCustomizerFactory does not support 
@Nested tests https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29037";>#29037
   Request to improve KotlinSerializationJsonHttpMessageConverter logic in 
RestTemplate https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/29008";>#29008
   WebFlux: multipart requests hang sometimes https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28963";>#28963
   DataBufferUtils.write(Publisher, Path) loses context https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28933";>#28933
   connectionTimeOut and readTimeout not working on UrlResource https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28909";>#28909
   SockJsServiceRegistration#setSupressCors has a typo and should be 
deprecated https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28853";>#28853
   RenderingResponse does not set status code on redirect views https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28839";>#28839
   Avoid IllegalArgumentException when setting WebSocket error status https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28836";>#28836
   Loss of context path after using ServerRequest.from https://github-redirect.dependabot.com/spring-projects/spring-framework/issues/28820";>#28820
   ResponseCookie does not declare nullability annotations consistently for 
domain and path https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28780";>#28780
   
   :notebook_with_decorative_cover: Documentation
   
   Fix typo in data-access section https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/29048";>#29048
   Correct description of @RequestParam with WebFlux https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28944";>#28944
   Fix broken kdoc-api links in kotlin.adoc https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28908";>#28908
   Fix typos in Javadoc of class AbstractEncoder https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28885";>#28885
   Fix links in Javadoc and reference docs https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28876";>#28876
   Add missing closing parenthesis in reference doc https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28867";>#28867
   Fix typos in Javadoc, reference docs, and code https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28822";>#28822
   Replace use of the  HTML tag in Javadoc https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28819";>#28819
   Fix broken link in rsocket documentation https://github-redirect.dependabot.com/spring-projects/spring-framework/pull/28817";>#28817
   Clarify docs on JNDI properties in Servlet environment https