Re: [PR] [MNG-8322] Use the new ToolchainsBuilder and SettingsBuilder [maven-integration-testing]
gnodet merged PR #391: URL: https://github.com/apache/maven-integration-testing/pull/391 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8322] Use the new ToolchainsBuilder and SettingsBuilder [maven]
gnodet merged PR #1778: URL: https://github.com/apache/maven/pull/1778 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8322) Use the new ToolchainsBuilder and SettingsBuilder
[ https://issues.apache.org/jira/browse/MNG-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8322. Resolution: Fixed > Use the new ToolchainsBuilder and SettingsBuilder > - > > Key: MNG-8322 > URL: https://issues.apache.org/jira/browse/MNG-8322 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1778 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8315] Failure of mvn.cmd if a .mvn folder is located at drive root [maven]
gnodet merged PR #1806: URL: https://github.com/apache/maven/pull/1806 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8315] Fix MAVEN_PROJECTBASEDIR in mvn.cmd when .mvn is at drive root [maven]
gnodet merged PR #1808: URL: https://github.com/apache/maven/pull/1808 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNG-8315) Failure of mvn.cmd if a .mvn directory is located at drive root
[
https://issues.apache.org/jira/browse/MNG-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8315.
Resolution: Fixed
> Failure of mvn.cmd if a .mvn directory is located at drive root
> ---
>
> Key: MNG-8315
> URL: https://issues.apache.org/jira/browse/MNG-8315
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.9.9
> Environment: Windows 10
>Reporter: Francois MAROT
>Assignee: Guillaume Nodet
>Priority: Minor
> Labels: easyfix
> Fix For: 3.9.10, 4.0.0-beta-5
>
>
> When .mvn is located on filesystem root, on Windows, the command line created
> (in mvn.cmd) to run java fails.
> This is because the part concerning multiModuleProjectDirectory ends with a
> slash before the double quote which certainly means escaping and it messes
> the whole command. Example for drive o: :
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\"{code}
> In this case, java.exe displays its usage help as it thinks the command is
> wrong.
> The workaround is to add an additional escaping backslash:
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\\"{code}
> Note: this only happens in case there is a .mvn at root.
>
> This simple line added just before calling "%JAVACMD%" seems to do the job:
> {code:java}
> if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
> "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
> A workaround for users facing the problem is to define MAVEN_BASEDIR to the
> drive root with 2 backslash before running Maven:
> {code:java}
> set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump maven.resolver.version from 2.0.1 to 2.0.2 [maven-mvnd]
dependabot[bot] opened a new pull request, #1172: URL: https://github.com/apache/maven-mvnd/pull/1172 Bumps `maven.resolver.version` from 2.0.1 to 2.0.2. Updates `org.apache.maven.resolver:maven-resolver-api` from 2.0.1 to 2.0.2 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.1...maven-resolver-2.0.2";>compare view Updates `org.apache.maven.resolver:maven-resolver-impl` from 2.0.1 to 2.0.2 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-impl's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.1...maven-resolver-2.0.2";
[jira] [Moved] (MCOMPILER-602) Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities from dependencies: CVE-2021-26291
[ https://issues.apache.org/jira/browse/MCOMPILER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet moved MNG-8319 to MCOMPILER-602: Component/s: (was: POM) Key: MCOMPILER-602 (was: MNG-8319) Project: Maven Compiler Plugin (was: Maven) > Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities > from dependencies: CVE-2021-26291 > --- > > Key: MCOMPILER-602 > URL: https://issues.apache.org/jira/browse/MCOMPILER-602 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: henry James NR >Priority: Critical > > Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities > from dependencies: CVE-2021-26291 > [Maven Repository: org.apache.maven.plugins » maven-compiler-plugin » 3.13.0 > (mvnrepository.com)|https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-compiler-plugin/3.13.0] > > Below are some of the maven libraries this plugin refers to and these has > Vulnerabilities. > |gav://org.codehaus.plexus:plexus-utils:2.0.5| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.apache.maven:maven-core:2.0.9| > |gav://org.codehaus.plexus:plexus-utils:1.1| > |gav://org.codehaus.plexus:plexus-archiver:2.1| > |gav://org.codehaus.plexus:plexus-utils:3.0| > |gav://org.codehaus.plexus:plexus-utils:3.0.5| > |gav://org.codehaus.plexus:plexus-utils:2.0.5| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Moved] (MCOMPILER-601) Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities from dependencies: CVE-2021-26291
[ https://issues.apache.org/jira/browse/MCOMPILER-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet moved MNG-8321 to MCOMPILER-601: Component/s: (was: POM) Key: MCOMPILER-601 (was: MNG-8321) Project: Maven Compiler Plugin (was: Maven) > Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities > from dependencies: CVE-2021-26291 > --- > > Key: MCOMPILER-601 > URL: https://issues.apache.org/jira/browse/MCOMPILER-601 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: Hari Prakash >Priority: Critical > > Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities > from dependencies: CVE-2021-26291 > [Maven Repository: org.apache.maven.plugins » maven-compiler-plugin » 3.13.0 > (mvnrepository.com)|https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-compiler-plugin/3.13.0] > Below are some of the maven libraries this plugin refers to and these has > Vulnerabilities. > |gav://org.codehaus.plexus:plexus-utils:2.0.5| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.apache.maven:maven-core:2.0.9| > |gav://org.codehaus.plexus:plexus-utils:1.1| > |gav://org.codehaus.plexus:plexus-archiver:2.1| > |gav://org.codehaus.plexus:plexus-utils:3.0| > |gav://org.codehaus.plexus:plexus-utils:3.0.5| > |gav://org.codehaus.plexus:plexus-utils:2.0.5| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8322) Use the new ToolchainsBuilder and SettingsBuilder
Guillaume Nodet created MNG-8322: Summary: Use the new ToolchainsBuilder and SettingsBuilder Key: MNG-8322 URL: https://issues.apache.org/jira/browse/MNG-8322 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1778 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Fix exports and move help in place [maven-mvnd]
cstamas merged PR #1166: URL: https://github.com/apache/maven-mvnd/pull/1166 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MNG-8322) Use the new ToolchainsBuilder and SettingsBuilder
[ https://issues.apache.org/jira/browse/MNG-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8322: Assignee: Guillaume Nodet > Use the new ToolchainsBuilder and SettingsBuilder > - > > Key: MNG-8322 > URL: https://issues.apache.org/jira/browse/MNG-8322 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > > GitHub Pull Request: https://github.com/apache/maven/pull/1778 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8322) Use the new ToolchainsBuilder and SettingsBuilder
[ https://issues.apache.org/jira/browse/MNG-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8322: - Fix Version/s: 4.0.0-beta-5 > Use the new ToolchainsBuilder and SettingsBuilder > - > > Key: MNG-8322 > URL: https://issues.apache.org/jira/browse/MNG-8322 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1778 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8313) Resolver 2.0.2
[ https://issues.apache.org/jira/browse/MNG-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8313. Resolution: Fixed > Resolver 2.0.2 > -- > > Key: MNG-8313 > URL: https://issues.apache.org/jira/browse/MNG-8313 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8302] Warn when appropriate [maven]
cstamas commented on PR #1810: URL: https://github.com/apache/maven/pull/1810#issuecomment-2418853122 > Should we create an IT to check the various use cases ? We could, but this is really minimal impact and more "user experience", nothing biggie IMO. -- 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-5988) Dependency mediation should prioritize transitive dependencies based on scope.
[
https://issues.apache.org/jira/browse/MNG-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890355#comment-17890355
]
ASF GitHub Bot commented on MNG-5988:
-
MLabusquiere commented on PR #442:
URL:
https://github.com/apache/maven-dependency-plugin/pull/442#issuecomment-2418851353
Thanks @elharo, this seems indeed a better solution!
Will you release it once merged?
In the mean time I close this PR in favor of
https://github.com/apache/maven-dependency-plugin/pull/445.
> Dependency mediation should prioritize transitive dependencies based on scope.
> --
>
> Key: MNG-5988
> URL: https://issues.apache.org/jira/browse/MNG-5988
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.2.3
>Reporter: Jostein Gogstad
>Priority: Critical
> Fix For: 4.0.0
>
> Attachments: Collected.svg, MNG-5988.zip, PRE.svg, Resolved.svg
>
>
> The
> [documentation|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> states that dependency mediation only supports "nearest definition",
> regardless of the scope of the parent dependency.
> If both compile- and test scoped dependencies shares the same transitive
> dependency, the test-scoped one will win if it has shallower depth. That in
> turn will lead to runtime exceptions since the transitive dependency is no
> longer on the classpath.
> Take the following pom from a typical [Spring
> Boot|http://projects.spring.io/spring-boot/] application. Since the
> {{camel-test-spring}} dependency also depends on spring, it wins and Spring
> is no longer available to the application at runtime.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.example
> bugreport
> jar
> 1.0.0-SNAPSHOT
>
>
> org.springframework.boot
> spring-boot-starter-web
> 1.3.2.RELEASE
>
>
> org.apache.camel
> camel-test-spring
> 2.16.2
> test
>
>
>
> {code}
> Now look for {{spring-beans}} or {{spring-context}} in the following
> dependency graphs:
> {code:xml|title=mvn dependency:tree (with camel-test-spring)}
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bugreport ---
> [INFO] com.example:bugreport:jar:1.0.0-SNAPSHOT
> [INFO] +-
> org.springframework.boot:spring-boot-starter-web:jar:1.3.2.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.3.2.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.3:compile
> [INFO] | | | | \- ch.qos.logback:logback-core:jar:1.1.3:compile
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.13:compile
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.13:compile
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.13:compile
> [INFO] | | \- org.yaml:snakeyaml:jar:1.16:runtime
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-core:jar:8.0.30:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-el:jar:8.0.30:compile
> [INFO] | | +-
> org.apache.tomcat.embed:tomcat-embed-logging-juli:jar:8.0.30:compile
> [INFO] | | \-
> org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.0.30:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-validation:jar:1.3.2.RELEASE:compile
> [INFO] | | \- org.hibernate:hibernate-validator:jar:5.2.2.Final:compile
> [INFO] | | +- javax.validation:validation-api:jar:1.1.0.Final:compile
> [INFO] | | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
> [INFO] | | \- com.fasterxml:classmate:jar:1.1.0:compile
> [INFO] | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile
> [INFO] | | +-
> com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile
> [INFO] | | \- com.fasterxml.jackson.core:jackson-core:jar:2.6.5:compile
> [INFO] | +- org.springframework:spring-web:jar:4.2.4.RELEASE:compile
> [INFO] | \- org.springframework:spring-webmvc:jar:4.2.4.RELEASE:compile
> [INFO] \- org.apache.camel:camel-test-spring:jar:2.16.2:test
> [INFO]+- org.apache.camel:camel-test:jar:2.16.2:test
> [INFO]| +- org.apache.camel:camel-core:jar:2.16.2:test
> [
[jira] [Updated] (MNG-8315) Failure of mvn.cmd if a .mvn directory is located at drive root
[
https://issues.apache.org/jira/browse/MNG-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8315:
-
Fix Version/s: (was: 3.9.10)
> Failure of mvn.cmd if a .mvn directory is located at drive root
> ---
>
> Key: MNG-8315
> URL: https://issues.apache.org/jira/browse/MNG-8315
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.9.9
> Environment: Windows 10
>Reporter: Francois MAROT
>Assignee: Guillaume Nodet
>Priority: Minor
> Labels: easyfix
> Fix For: 4.0.0-beta-5
>
>
> When .mvn is located on filesystem root, on Windows, the command line created
> (in mvn.cmd) to run java fails.
> This is because the part concerning multiModuleProjectDirectory ends with a
> slash before the double quote which certainly means escaping and it messes
> the whole command. Example for drive o: :
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\"{code}
> In this case, java.exe displays its usage help as it thinks the command is
> wrong.
> The workaround is to add an additional escaping backslash:
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\\"{code}
> Note: this only happens in case there is a .mvn at root.
>
> This simple line added just before calling "%JAVACMD%" seems to do the job:
> {code:java}
> if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
> "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
> A workaround for users facing the problem is to define MAVEN_BASEDIR to the
> drive root with 2 backslash before running Maven:
> {code:java}
> set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8323) (3.9.x) Failure of mvn.cmd if a .mvn directory is located at drive root
[
https://issues.apache.org/jira/browse/MNG-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8323:
-
Fix Version/s: (was: 4.0.0-beta-5)
> (3.9.x) Failure of mvn.cmd if a .mvn directory is located at drive root
> ---
>
> Key: MNG-8323
> URL: https://issues.apache.org/jira/browse/MNG-8323
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.9.9
> Environment: Windows 10
>Reporter: Francois MAROT
>Assignee: Guillaume Nodet
>Priority: Minor
> Labels: easyfix
> Fix For: 3.9.10
>
>
> When .mvn is located on filesystem root, on Windows, the command line created
> (in mvn.cmd) to run java fails.
> This is because the part concerning multiModuleProjectDirectory ends with a
> slash before the double quote which certainly means escaping and it messes
> the whole command. Example for drive o: :
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\"{code}
> In this case, java.exe displays its usage help as it thinks the command is
> wrong.
> The workaround is to add an additional escaping backslash:
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\\"{code}
> Note: this only happens in case there is a .mvn at root.
>
> This simple line added just before calling "%JAVACMD%" seems to do the job:
> {code:java}
> if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
> "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
> A workaround for users facing the problem is to define MAVEN_BASEDIR to the
> drive root with 2 backslash before running Maven:
> {code:java}
> set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5988) Dependency mediation should prioritize transitive dependencies based on scope.
[
https://issues.apache.org/jira/browse/MNG-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890354#comment-17890354
]
ASF GitHub Bot commented on MNG-5988:
-
MLabusquiere closed pull request #442: [MNG-5988] Drop `commons-io` from
explicit test dependencies
URL: https://github.com/apache/maven-dependency-plugin/pull/442
> Dependency mediation should prioritize transitive dependencies based on scope.
> --
>
> Key: MNG-5988
> URL: https://issues.apache.org/jira/browse/MNG-5988
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.2.3
>Reporter: Jostein Gogstad
>Priority: Critical
> Fix For: 4.0.0
>
> Attachments: Collected.svg, MNG-5988.zip, PRE.svg, Resolved.svg
>
>
> The
> [documentation|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> states that dependency mediation only supports "nearest definition",
> regardless of the scope of the parent dependency.
> If both compile- and test scoped dependencies shares the same transitive
> dependency, the test-scoped one will win if it has shallower depth. That in
> turn will lead to runtime exceptions since the transitive dependency is no
> longer on the classpath.
> Take the following pom from a typical [Spring
> Boot|http://projects.spring.io/spring-boot/] application. Since the
> {{camel-test-spring}} dependency also depends on spring, it wins and Spring
> is no longer available to the application at runtime.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.example
> bugreport
> jar
> 1.0.0-SNAPSHOT
>
>
> org.springframework.boot
> spring-boot-starter-web
> 1.3.2.RELEASE
>
>
> org.apache.camel
> camel-test-spring
> 2.16.2
> test
>
>
>
> {code}
> Now look for {{spring-beans}} or {{spring-context}} in the following
> dependency graphs:
> {code:xml|title=mvn dependency:tree (with camel-test-spring)}
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bugreport ---
> [INFO] com.example:bugreport:jar:1.0.0-SNAPSHOT
> [INFO] +-
> org.springframework.boot:spring-boot-starter-web:jar:1.3.2.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.3.2.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.3:compile
> [INFO] | | | | \- ch.qos.logback:logback-core:jar:1.1.3:compile
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.13:compile
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.13:compile
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.13:compile
> [INFO] | | \- org.yaml:snakeyaml:jar:1.16:runtime
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-core:jar:8.0.30:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-el:jar:8.0.30:compile
> [INFO] | | +-
> org.apache.tomcat.embed:tomcat-embed-logging-juli:jar:8.0.30:compile
> [INFO] | | \-
> org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.0.30:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-validation:jar:1.3.2.RELEASE:compile
> [INFO] | | \- org.hibernate:hibernate-validator:jar:5.2.2.Final:compile
> [INFO] | | +- javax.validation:validation-api:jar:1.1.0.Final:compile
> [INFO] | | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
> [INFO] | | \- com.fasterxml:classmate:jar:1.1.0:compile
> [INFO] | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile
> [INFO] | | +-
> com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile
> [INFO] | | \- com.fasterxml.jackson.core:jackson-core:jar:2.6.5:compile
> [INFO] | +- org.springframework:spring-web:jar:4.2.4.RELEASE:compile
> [INFO] | \- org.springframework:spring-webmvc:jar:4.2.4.RELEASE:compile
> [INFO] \- org.apache.camel:camel-test-spring:jar:2.16.2:test
> [INFO]+- org.apache.camel:camel-test:jar:2.16.2:test
> [INFO]| +- org.apache.camel:camel-core:jar:2.16.2:test
> [INFO]| | \- org.slf4j:slf4j-api:jar:1.6.6:compile
> [INFO]| \- junit:junit:jar:4.11:test
> [INFO]| \- org.hamcrest:hamcrest-core:jar:1.3:test
> [INF
Re: [PR] [MNG-8302] Warn when appropriate [maven]
cstamas merged PR #1810: URL: https://github.com/apache/maven/pull/1810 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8313] Upgrade to Resolver 2.0.2 [maven]
cstamas merged PR #1796: URL: https://github.com/apache/maven/pull/1796 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-5988] Drop `commons-io` from explicit test dependencies [maven-dependency-plugin]
MLabusquiere closed pull request #442: [MNG-5988] Drop `commons-io` from explicit test dependencies URL: https://github.com/apache/maven-dependency-plugin/pull/442 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-5988] Drop `commons-io` from explicit test dependencies [maven-dependency-plugin]
MLabusquiere commented on PR #442: URL: https://github.com/apache/maven-dependency-plugin/pull/442#issuecomment-2418851353 Thanks @elharo, this seems indeed a better solution! Will you release it once merged? In the mean time I close this PR in favor of https://github.com/apache/maven-dependency-plugin/pull/445. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (MNG-8310) Use --debug option instead of a specific mvnDebug script
[ https://issues.apache.org/jira/browse/MNG-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned MNG-8310: Assignee: Guillaume Nodet (was: Tamas Cservenak) > Use --debug option instead of a specific mvnDebug script > > > Key: MNG-8310 > URL: https://issues.apache.org/jira/browse/MNG-8310 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8315) Failure of mvn.cmd if a .mvn directory is located at drive root
[
https://issues.apache.org/jira/browse/MNG-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned MNG-8315:
Assignee: Guillaume Nodet
> Failure of mvn.cmd if a .mvn directory is located at drive root
> ---
>
> Key: MNG-8315
> URL: https://issues.apache.org/jira/browse/MNG-8315
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.9.9
> Environment: Windows 10
>Reporter: Francois MAROT
>Assignee: Guillaume Nodet
>Priority: Minor
> Labels: easyfix
> Fix For: 3.9.10, 4.0.0-beta-5
>
>
> When .mvn is located on filesystem root, on Windows, the command line created
> (in mvn.cmd) to run java fails.
> This is because the part concerning multiModuleProjectDirectory ends with a
> slash before the double quote which certainly means escaping and it messes
> the whole command. Example for drive o: :
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\"{code}
> In this case, java.exe displays its usage help as it thinks the command is
> wrong.
> The workaround is to add an additional escaping backslash:
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\\"{code}
> Note: this only happens in case there is a .mvn at root.
>
> This simple line added just before calling "%JAVACMD%" seems to do the job:
> {code:java}
> if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
> "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
> A workaround for users facing the problem is to define MAVEN_BASEDIR to the
> drive root with 2 backslash before running Maven:
> {code:java}
> set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-8323) (3.9.x) Failure of mvn.cmd if a .mvn directory is located at drive root
Tamas Cservenak created MNG-8323:
Summary: (3.9.x) Failure of mvn.cmd if a .mvn directory is located
at drive root
Key: MNG-8323
URL: https://issues.apache.org/jira/browse/MNG-8323
Project: Maven
Issue Type: Bug
Components: Command Line
Affects Versions: 3.9.9
Environment: Windows 10
Reporter: Francois MAROT
Assignee: Guillaume Nodet
Fix For: 3.9.10, 4.0.0-beta-5
When .mvn is located on filesystem root, on Windows, the command line created
(in mvn.cmd) to run java fails.
This is because the part concerning multiModuleProjectDirectory ends with a
slash before the double quote which certainly means escaping and it messes the
whole command. Example for drive o: :
{code:java}
"-Dmaven.multiModuleProjectDirectory=o:\"{code}
In this case, java.exe displays its usage help as it thinks the command is
wrong.
The workaround is to add an additional escaping backslash:
{code:java}
"-Dmaven.multiModuleProjectDirectory=o:\\"{code}
Note: this only happens in case there is a .mvn at root.
This simple line added just before calling "%JAVACMD%" seems to do the job:
{code:java}
if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
"MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
A workaround for users facing the problem is to define MAVEN_BASEDIR to the
drive root with 2 backslash before running Maven:
{code:java}
set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-5988) Dependency mediation should prioritize transitive dependencies based on scope.
[
https://issues.apache.org/jira/browse/MNG-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890359#comment-17890359
]
Guillaume Nodet edited comment on MNG-5988 at 10/17/24 8:15 AM:
[~elharo] The commons-io MDEP problem seems completely unrelated to this issue.
was (Author: gnt):
The commons-io MDEP problem seems completely unrelated to this issue.
> Dependency mediation should prioritize transitive dependencies based on scope.
> --
>
> Key: MNG-5988
> URL: https://issues.apache.org/jira/browse/MNG-5988
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.2.3
>Reporter: Jostein Gogstad
>Priority: Critical
> Fix For: 4.0.0
>
> Attachments: Collected.svg, MNG-5988.zip, PRE.svg, Resolved.svg
>
>
> The
> [documentation|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> states that dependency mediation only supports "nearest definition",
> regardless of the scope of the parent dependency.
> If both compile- and test scoped dependencies shares the same transitive
> dependency, the test-scoped one will win if it has shallower depth. That in
> turn will lead to runtime exceptions since the transitive dependency is no
> longer on the classpath.
> Take the following pom from a typical [Spring
> Boot|http://projects.spring.io/spring-boot/] application. Since the
> {{camel-test-spring}} dependency also depends on spring, it wins and Spring
> is no longer available to the application at runtime.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.example
> bugreport
> jar
> 1.0.0-SNAPSHOT
>
>
> org.springframework.boot
> spring-boot-starter-web
> 1.3.2.RELEASE
>
>
> org.apache.camel
> camel-test-spring
> 2.16.2
> test
>
>
>
> {code}
> Now look for {{spring-beans}} or {{spring-context}} in the following
> dependency graphs:
> {code:xml|title=mvn dependency:tree (with camel-test-spring)}
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bugreport ---
> [INFO] com.example:bugreport:jar:1.0.0-SNAPSHOT
> [INFO] +-
> org.springframework.boot:spring-boot-starter-web:jar:1.3.2.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.3.2.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.3:compile
> [INFO] | | | | \- ch.qos.logback:logback-core:jar:1.1.3:compile
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.13:compile
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.13:compile
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.13:compile
> [INFO] | | \- org.yaml:snakeyaml:jar:1.16:runtime
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-core:jar:8.0.30:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-el:jar:8.0.30:compile
> [INFO] | | +-
> org.apache.tomcat.embed:tomcat-embed-logging-juli:jar:8.0.30:compile
> [INFO] | | \-
> org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.0.30:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-validation:jar:1.3.2.RELEASE:compile
> [INFO] | | \- org.hibernate:hibernate-validator:jar:5.2.2.Final:compile
> [INFO] | | +- javax.validation:validation-api:jar:1.1.0.Final:compile
> [INFO] | | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
> [INFO] | | \- com.fasterxml:classmate:jar:1.1.0:compile
> [INFO] | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile
> [INFO] | | +-
> com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile
> [INFO] | | \- com.fasterxml.jackson.core:jackson-core:jar:2.6.5:compile
> [INFO] | +- org.springframework:spring-web:jar:4.2.4.RELEASE:compile
> [INFO] | \- org.springframework:spring-webmvc:jar:4.2.4.RELEASE:compile
> [INFO] \- org.apache.camel:camel-test-spring:jar:2.16.2:test
> [INFO]+- org.apache.camel:camel-test:jar:2.16.2:test
> [INFO]| +- org.apache.camel:camel-core:jar:2.16.2:test
> [INFO]| | \- org.slf4j:slf4j-api:jar:1.6.6:compile
> [INFO]| \- junit:junit:jar:4.11:test
> [INFO]
[jira] [Commented] (MNG-5988) Dependency mediation should prioritize transitive dependencies based on scope.
[
https://issues.apache.org/jira/browse/MNG-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890359#comment-17890359
]
Guillaume Nodet commented on MNG-5988:
--
The commons-io MDEP problem seems completely unrelated to this issue.
> Dependency mediation should prioritize transitive dependencies based on scope.
> --
>
> Key: MNG-5988
> URL: https://issues.apache.org/jira/browse/MNG-5988
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.2.3
>Reporter: Jostein Gogstad
>Priority: Critical
> Fix For: 4.0.0
>
> Attachments: Collected.svg, MNG-5988.zip, PRE.svg, Resolved.svg
>
>
> The
> [documentation|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> states that dependency mediation only supports "nearest definition",
> regardless of the scope of the parent dependency.
> If both compile- and test scoped dependencies shares the same transitive
> dependency, the test-scoped one will win if it has shallower depth. That in
> turn will lead to runtime exceptions since the transitive dependency is no
> longer on the classpath.
> Take the following pom from a typical [Spring
> Boot|http://projects.spring.io/spring-boot/] application. Since the
> {{camel-test-spring}} dependency also depends on spring, it wins and Spring
> is no longer available to the application at runtime.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.example
> bugreport
> jar
> 1.0.0-SNAPSHOT
>
>
> org.springframework.boot
> spring-boot-starter-web
> 1.3.2.RELEASE
>
>
> org.apache.camel
> camel-test-spring
> 2.16.2
> test
>
>
>
> {code}
> Now look for {{spring-beans}} or {{spring-context}} in the following
> dependency graphs:
> {code:xml|title=mvn dependency:tree (with camel-test-spring)}
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bugreport ---
> [INFO] com.example:bugreport:jar:1.0.0-SNAPSHOT
> [INFO] +-
> org.springframework.boot:spring-boot-starter-web:jar:1.3.2.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.3.2.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.3:compile
> [INFO] | | | | \- ch.qos.logback:logback-core:jar:1.1.3:compile
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.13:compile
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.13:compile
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.13:compile
> [INFO] | | \- org.yaml:snakeyaml:jar:1.16:runtime
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-core:jar:8.0.30:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-el:jar:8.0.30:compile
> [INFO] | | +-
> org.apache.tomcat.embed:tomcat-embed-logging-juli:jar:8.0.30:compile
> [INFO] | | \-
> org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.0.30:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-validation:jar:1.3.2.RELEASE:compile
> [INFO] | | \- org.hibernate:hibernate-validator:jar:5.2.2.Final:compile
> [INFO] | | +- javax.validation:validation-api:jar:1.1.0.Final:compile
> [INFO] | | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
> [INFO] | | \- com.fasterxml:classmate:jar:1.1.0:compile
> [INFO] | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile
> [INFO] | | +-
> com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile
> [INFO] | | \- com.fasterxml.jackson.core:jackson-core:jar:2.6.5:compile
> [INFO] | +- org.springframework:spring-web:jar:4.2.4.RELEASE:compile
> [INFO] | \- org.springframework:spring-webmvc:jar:4.2.4.RELEASE:compile
> [INFO] \- org.apache.camel:camel-test-spring:jar:2.16.2:test
> [INFO]+- org.apache.camel:camel-test:jar:2.16.2:test
> [INFO]| +- org.apache.camel:camel-core:jar:2.16.2:test
> [INFO]| | \- org.slf4j:slf4j-api:jar:1.6.6:compile
> [INFO]| \- junit:junit:jar:4.11:test
> [INFO]| \- org.hamcrest:hamcrest-core:jar:1.3:test
> [INFO]+- org.apache.camel:camel-spring:jar:2.16.2:test
> [INFO]+- org.springframework:spring
Re: [PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
ottlinger closed pull request #208: Fix typos in history.apt and faq.fml URL: https://github.com/apache/maven-site-plugin/pull/208 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
ottlinger commented on PR #208: URL: https://github.com/apache/maven-site-plugin/pull/208#issuecomment-2419086028 Will try to open a new PR - sry4the mess. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
ottlinger opened a new pull request, #209: URL: https://github.com/apache/maven-site-plugin/pull/209 Trivial changes in the documentation. - [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) @michael-o hoipefully everything works now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
ottlinger commented on PR #208: URL: https://github.com/apache/maven-site-plugin/pull/208#issuecomment-2419104305 https://github.com/apache/maven-site-plugin/pull/209 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
michael-o commented on PR #209: URL: https://github.com/apache/maven-site-plugin/pull/209#issuecomment-2419118229 Thanks, merged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
michael-o merged PR #209: URL: https://github.com/apache/maven-site-plugin/pull/209 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] The EventSpy receives the new settings request/result [maven-integration-testing]
gnodet opened a new pull request, #391: URL: https://github.com/apache/maven-integration-testing/pull/391 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8312] Generate the BOM automatically [maven]
gnodet commented on PR #1797: URL: https://github.com/apache/maven/pull/1797#issuecomment-2418942536 Skinny BOM: https://gist.github.com/gnodet/53bf123caa20845752a9b842686acf44 Fat BOM: https://gist.github.com/gnodet/f366cb07e3876184c20d96212924e418 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix typos in history.apt and faq.fml [maven-site-plugin]
ottlinger commented on PR #208: URL: https://github.com/apache/maven-site-plugin/pull/208#issuecomment-2418948992 @michael-o I have no configuration option when syncing my fork . I thought you would get rid of my 5 commits during merging my PR? Where is my misunderstanding of your request ? -- 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] [Deleted] (MNG-8323) (3.9.x) Failure of mvn.cmd if a .mvn directory is located at drive root
[
https://issues.apache.org/jira/browse/MNG-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak deleted MNG-8323:
-
> (3.9.x) Failure of mvn.cmd if a .mvn directory is located at drive root
> ---
>
> Key: MNG-8323
> URL: https://issues.apache.org/jira/browse/MNG-8323
> Project: Maven
> Issue Type: Bug
> Environment: Windows 10
>Reporter: Francois MAROT
>Assignee: Guillaume Nodet
>Priority: Minor
> Labels: easyfix
>
> When .mvn is located on filesystem root, on Windows, the command line created
> (in mvn.cmd) to run java fails.
> This is because the part concerning multiModuleProjectDirectory ends with a
> slash before the double quote which certainly means escaping and it messes
> the whole command. Example for drive o: :
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\"{code}
> In this case, java.exe displays its usage help as it thinks the command is
> wrong.
> The workaround is to add an additional escaping backslash:
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\\"{code}
> Note: this only happens in case there is a .mvn at root.
>
> This simple line added just before calling "%JAVACMD%" seems to do the job:
> {code:java}
> if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
> "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
> A workaround for users facing the problem is to define MAVEN_BASEDIR to the
> drive root with 2 backslash before running Maven:
> {code:java}
> set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8315) Failure of mvn.cmd if a .mvn directory is located at drive root
[
https://issues.apache.org/jira/browse/MNG-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8315:
-
Fix Version/s: 3.9.10
> Failure of mvn.cmd if a .mvn directory is located at drive root
> ---
>
> Key: MNG-8315
> URL: https://issues.apache.org/jira/browse/MNG-8315
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.9.9
> Environment: Windows 10
>Reporter: Francois MAROT
>Assignee: Guillaume Nodet
>Priority: Minor
> Labels: easyfix
> Fix For: 3.9.10, 4.0.0-beta-5
>
>
> When .mvn is located on filesystem root, on Windows, the command line created
> (in mvn.cmd) to run java fails.
> This is because the part concerning multiModuleProjectDirectory ends with a
> slash before the double quote which certainly means escaping and it messes
> the whole command. Example for drive o: :
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\"{code}
> In this case, java.exe displays its usage help as it thinks the command is
> wrong.
> The workaround is to add an additional escaping backslash:
> {code:java}
> "-Dmaven.multiModuleProjectDirectory=o:\\"{code}
> Note: this only happens in case there is a .mvn at root.
>
> This simple line added just before calling "%JAVACMD%" seems to do the job:
> {code:java}
> if "%MAVEN_PROJECTBASEDIR:~-1%"=="\" set
> "MAVEN_PROJECTBASEDIR=%MAVEN_PROJECTBASEDIR%\"{code}
> A workaround for users facing the problem is to define MAVEN_BASEDIR to the
> drive root with 2 backslash before running Maven:
> {code:java}
> set MAVEN_BASEDIR=%tempDriveLetter%:\\{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Force apache transport [maven-mvnd]
cstamas opened a new pull request, #1171: URL: https://github.com/apache/maven-mvnd/pull/1171 Just a desperate PR to figure out why MacOS GH runners keep failing with transport related (SSL handshake abort, HTTP timeouts) errors. -- 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] [Deleted] (MCOMPILER-602) Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities from dependencies: CVE-2021-26291
[ https://issues.apache.org/jira/browse/MCOMPILER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov deleted MCOMPILER-602: - > Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities > from dependencies: CVE-2021-26291 > --- > > Key: MCOMPILER-602 > URL: https://issues.apache.org/jira/browse/MCOMPILER-602 > Project: Maven Compiler Plugin > Issue Type: Bug >Reporter: henry James NR >Priority: Critical > > Apache Maven Compiler Plugin 3.13.0 and lower version has Vulnerabilities > from dependencies: CVE-2021-26291 > [Maven Repository: org.apache.maven.plugins » maven-compiler-plugin » 3.13.0 > (mvnrepository.com)|https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-compiler-plugin/3.13.0] > > Below are some of the maven libraries this plugin refers to and these has > Vulnerabilities. > |gav://org.codehaus.plexus:plexus-utils:2.0.5| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.apache.maven:maven-core:2.0.9| > |gav://org.codehaus.plexus:plexus-utils:1.1| > |gav://org.codehaus.plexus:plexus-archiver:2.1| > |gav://org.codehaus.plexus:plexus-utils:3.0| > |gav://org.codehaus.plexus:plexus-utils:3.0.5| > |gav://org.codehaus.plexus:plexus-utils:2.0.5| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| > |gav://org.codehaus.plexus:plexus-utils:3.0.8| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-5988) Dependency mediation should prioritize transitive dependencies based on scope.
[
https://issues.apache.org/jira/browse/MNG-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890413#comment-17890413
]
Elliotte Rusty Harold commented on MNG-5988:
Au contraire, I think it's exactly this issue. The dependency plugin breaks
because a test scope dependency on commons-io overrides a compile scope
dependency further down the tree. The PR fixes this problem by removing the
dependency.
> Dependency mediation should prioritize transitive dependencies based on scope.
> --
>
> Key: MNG-5988
> URL: https://issues.apache.org/jira/browse/MNG-5988
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.2.3
>Reporter: Jostein Gogstad
>Priority: Critical
> Fix For: 4.0.0
>
> Attachments: Collected.svg, MNG-5988.zip, PRE.svg, Resolved.svg
>
>
> The
> [documentation|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html]
> states that dependency mediation only supports "nearest definition",
> regardless of the scope of the parent dependency.
> If both compile- and test scoped dependencies shares the same transitive
> dependency, the test-scoped one will win if it has shallower depth. That in
> turn will lead to runtime exceptions since the transitive dependency is no
> longer on the classpath.
> Take the following pom from a typical [Spring
> Boot|http://projects.spring.io/spring-boot/] application. Since the
> {{camel-test-spring}} dependency also depends on spring, it wins and Spring
> is no longer available to the application at runtime.
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.example
> bugreport
> jar
> 1.0.0-SNAPSHOT
>
>
> org.springframework.boot
> spring-boot-starter-web
> 1.3.2.RELEASE
>
>
> org.apache.camel
> camel-test-spring
> 2.16.2
> test
>
>
>
> {code}
> Now look for {{spring-beans}} or {{spring-context}} in the following
> dependency graphs:
> {code:xml|title=mvn dependency:tree (with camel-test-spring)}
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ bugreport ---
> [INFO] com.example:bugreport:jar:1.0.0-SNAPSHOT
> [INFO] +-
> org.springframework.boot:spring-boot-starter-web:jar:1.3.2.RELEASE:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.springframework.boot:spring-boot:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-autoconfigure:jar:1.3.2.RELEASE:compile
> [INFO] | | +-
> org.springframework.boot:spring-boot-starter-logging:jar:1.3.2.RELEASE:compile
> [INFO] | | | +- ch.qos.logback:logback-classic:jar:1.1.3:compile
> [INFO] | | | | \- ch.qos.logback:logback-core:jar:1.1.3:compile
> [INFO] | | | +- org.slf4j:jcl-over-slf4j:jar:1.7.13:compile
> [INFO] | | | +- org.slf4j:jul-to-slf4j:jar:1.7.13:compile
> [INFO] | | | \- org.slf4j:log4j-over-slf4j:jar:1.7.13:compile
> [INFO] | | \- org.yaml:snakeyaml:jar:1.16:runtime
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:1.3.2.RELEASE:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-core:jar:8.0.30:compile
> [INFO] | | +- org.apache.tomcat.embed:tomcat-embed-el:jar:8.0.30:compile
> [INFO] | | +-
> org.apache.tomcat.embed:tomcat-embed-logging-juli:jar:8.0.30:compile
> [INFO] | | \-
> org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.0.30:compile
> [INFO] | +-
> org.springframework.boot:spring-boot-starter-validation:jar:1.3.2.RELEASE:compile
> [INFO] | | \- org.hibernate:hibernate-validator:jar:5.2.2.Final:compile
> [INFO] | | +- javax.validation:validation-api:jar:1.1.0.Final:compile
> [INFO] | | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
> [INFO] | | \- com.fasterxml:classmate:jar:1.1.0:compile
> [INFO] | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.5:compile
> [INFO] | | +-
> com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile
> [INFO] | | \- com.fasterxml.jackson.core:jackson-core:jar:2.6.5:compile
> [INFO] | +- org.springframework:spring-web:jar:4.2.4.RELEASE:compile
> [INFO] | \- org.springframework:spring-webmvc:jar:4.2.4.RELEASE:compile
> [INFO] \- org.apache.camel:camel-test-spring:jar:2.16.2:test
> [INFO]+- org.apache.camel:camel-test:jar:2.16.2:test
> [INFO]| +- org.apache.camel:camel-core:jar:2.16.2:test
> [INFO]| | \- org.slf4j:slf4j-api:jar:1.6.6:compile
> [INFO]| \- junit:j
[PR] [MNG-8258] Change the fixed reproducible build outputTimestamp to 1 Feb 1080 [maven]
stokito opened a new pull request, #1813: URL: https://github.com/apache/maven/pull/1813 The Maven used the own inception year 2001. But the Gradle already use the 1 Feb 1980 for preserveFileTimestamps. The 1 Jan 1980 is a minimal date in Zip archive but the 1 Jan has some special treatment by Java that's why the Gradle team used the 1 Feb. See more detailed description in CONSTANT_TIME_FOR_ZIP_ENTRIES https://github.com/gradle/gradle/blob/master/platforms/core-runtime/files/src/main/java/org/gradle/api/internal/file/archive/ZipEntryConstants.java#L39 The change was first proposed in the https://github.com/apache/maven/pull/1726#issuecomment-2376407039 and also slightly discussed in the MSHARED-1430 > @hboutemy: > many people have many opinions: there are even more opinions than people > The default value has been added in [MNG-8258](https://issues.apache.org/jira/browse/MNG-8258) with a Maven-specific timestamp (no reason to try to mimic others: there is no perfect or wrong choice) > @stokito: > Sure, but a standardization always improves and simplifies things (if done right). Having the same value 1 Feb 1980 will simplify search "Why my jar has the weird date? You have the reproducible build. Ah, ok, ty". But also I switch from Gradle to Maven then if would be less differences in artifacts. Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MNG-8258) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. - [x] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`. Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the [Core IT][core-its] successfully. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). [core-its]: https://maven.apache.org/core-its/core-it-suite/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8258) activate Reproducible Builds by default
[
https://issues.apache.org/jira/browse/MNG-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890426#comment-17890426
]
Sergey Ponomarev commented on MNG-8258:
---
I created a PR to change the 1 Jan 2001 to the Gradle's 1 Feb 1080
https://github.com/apache/maven/pull/1813
> activate Reproducible Builds by default
> ---
>
> Key: MNG-8258
> URL: https://issues.apache.org/jira/browse/MNG-8258
> Project: Maven
> Issue Type: New Feature
> Components: Core
>Affects Versions: 3.9.9, 4.0.0-beta-4
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.9.x-candidate, 4.0.0-beta-5
>
>
> Reproducible Builds is a good practice that is easy to enable: it would be
> nice to enable it by default, and have projects
> - either disable it
> ({{x}}) if
> they really have a problem with the default Reproducible behaviour
> - or customize locally the value of the default Maven core-provided
> timestamp, to have a project-specific value
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] mvnd IT: increase connectTimeout for ITs [maven-mvnd]
cstamas merged PR #1171: URL: https://github.com/apache/maven-mvnd/pull/1171 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.resolver.version from 2.0.1 to 2.0.2 [maven-mvnd]
cstamas commented on PR #1172: URL: https://github.com/apache/maven-mvnd/pull/1172#issuecomment-2419358759 @dependabot rebase -- 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] (ARCHETYPE-689) Archetype Plugin 3.3.0 introduced incompatibilities
[
https://issues.apache.org/jira/browse/ARCHETYPE-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890438#comment-17890438
]
Slawomir Jaranowski commented on ARCHETYPE-689:
---
[~barchetta] did you look at PR ... I would like to merge and release next
version
> Archetype Plugin 3.3.0 introduced incompatibilities
> ---
>
> Key: ARCHETYPE-689
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-689
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator, Plugin
>Affects Versions: 3.3.0
>Reporter: Joe DiPol
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> Archetype Plugin 3.3.0 introduced API incompatibilities that can break
> existing maven archetypes. This is significant because when the plugin is
> invoked by users the version of the plugin is rarely specified. An example of
> such a breakage is [https://github.com/helidon-io/helidon/issues/9305] (where
> all previously shipped versions of our maven archetypes broke).
> The incompatibilities were introduced by
> [https://github.com/apache/maven-archetype/pull/211] and
> [https://github.com/apache/maven-archetype/pull/215]
> Changes that broke our archetypes:
> # The removal of {{ArchetypeGenerationRequest.getProjectBuildingRequest()}}
> # The changing of the return type of
> {{ArchetypeGenerationRequest.getRemoteArtifactRepositories()}} from
> {{List}} to {{List}}
> It also looks like a number of other methods were removed from
> {{ArchetypeGenerationRequest}}.
> As documented in
> [https://maven.apache.org/archetype/maven-archetype-plugin/advanced-usage.html#post-generation-script]
> the {{ArchetypeGenerationRequest}} object is the primary API for
> customization by a post-generation groovy script. And the changed/removed
> methods were not marked for deprecation. Any archetype released before 3.3.0
> that relied on this class is potentially broken.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Upgraded plugins and components in ITs [maven-scm-publish-plugin]
CogitoKunal opened a new pull request, #38: URL: https://github.com/apache/maven-scm-publish-plugin/pull/38 I have Upgraded plugins and components in ITs 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/MSCMPUBLISH) 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 `[MSCMPUBLISH-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSCMPUBLISH-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify -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 licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MRESOLVER-612) Align connect and request timeout interpretation by HTTP transports
Tamas Cservenak created MRESOLVER-612:
-
Summary: Align connect and request timeout interpretation by HTTP
transports
Key: MRESOLVER-612
URL: https://issues.apache.org/jira/browse/MRESOLVER-612
Project: Maven Resolver
Issue Type: Bug
Components: Resolver
Reporter: Tamas Cservenak
Fix For: 2.0.3
By default, {{jetty}} and {{jdk}} are fully (almost) aligned how they interpret
these two timeouts, but {{apache}} was totally off.
Make sure all HTTP transport can work in same way, as regards timeouts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-612) Align connect and request timeout interpretation by HTTP transports
[
https://issues.apache.org/jira/browse/MRESOLVER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MRESOLVER-612:
-
Assignee: Tamas Cservenak
> Align connect and request timeout interpretation by HTTP transports
> ---
>
> Key: MRESOLVER-612
> URL: https://issues.apache.org/jira/browse/MRESOLVER-612
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.3
>
>
> By default, {{jetty}} and {{jdk}} are fully (almost) aligned how they
> interpret these two timeouts, but {{apache}} was totally off.
> Make sure all HTTP transport can work in same way, as regards timeouts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8312] Generate the BOM automatically [maven]
cstamas commented on PR #1797: URL: https://github.com/apache/maven/pull/1797#issuecomment-2419597819 I love the "fat" one! No more "locked to maven" comment on properties in plugins! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Transport: apache hard timeout [maven-resolver]
cstamas opened a new pull request, #584: URL: https://github.com/apache/maven-resolver/pull/584 All transports EXCEPT Apache have "hard timeout", that is configured via `ConfigurationProperties.REQUEST_TIMEOUT` and guarantees that HTTP Transaction takes max that long (or fail). Apache on the other hand does not have such guarantee natively. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump net.bytebuddy:byte-buddy from 1.14.18 to 1.15.5 [maven-plugin-tools]
dependabot[bot] opened a new pull request, #332: URL: https://github.com/apache/maven-plugin-tools/pull/332 Bumps [net.bytebuddy:byte-buddy](https://github.com/raphw/byte-buddy) from 1.14.18 to 1.15.5. Release notes Sourced from https://github.com/raphw/byte-buddy/releases";>net.bytebuddy:byte-buddy's releases. Byte Buddy 1.15.5 Publish Byte Buddy and Byte Buddy agent artifacts as multi-release jars to support CDS and faster validation. Byte Buddy 1.15.4 Add non-experimental support for Java 24. Byte Buddy 1.15.3 Treat multi-release class files that are newer than the supported version as regular resources. Allow overriding the multi-release class file version from Maven and Gradle plugin. Correctly resolve multi-release class files in Android. Byte Buddy 1.15.2 Add support for multi-release JAR files in ClassFileLocators and Plugin.Engine.Default. Add Gradle task for transforming multiple jar files with ByteBuddyJarsTask. Avoid validation of JarFile when extracting individual entries. Rework discovery in ByteBuddyMojo. Byte Buddy 1.15.1 Revert default EntryPoint for Android Gradle plugin to use DECORATE unless explicitly specified due to many generic type errors in Kotlin classes. Byte Buddy 1.15.0 Introduce AsmClassWriter and AsmClassReader abstractions that allow for plugging different implementations of readers and writers. Add configuration extension to the Android Gradle plugin and make it behave like regular Gradle plugin with standard configuration. Throw TypeNotPresentException upon discovering undeclared type variables as it was recently fixed on the JVM. byte-buddy-1.14.19 Add Maven Mojo for transforming jars and for transforming dependencies folder. Better error handling for unresolved type variables. Allow loading arguments of the instrumented method in MemberSubstitution. Fix checks for method visibility. Changelog Sourced from https://github.com/raphw/byte-buddy/blob/master/release-notes.md";>net.bytebuddy:byte-buddy's changelog. Byte Buddy release notes 9. October 2024: version 1.15.4 Add non-experimental support for Java 24. 26. September 2024: version 1.15.3 Treat multi-release class files that are newer than the supported version as regular resources. Allow overriding the multi-release class file version from Maven and Gradle plugin. Correctly resolve multi-release class files in Android. 25. September 2024: version 1.15.2 Add support for multi-release JAR files in ClassFileLocators and Plugin.Engine.Default. Add Gradle task for transforming multiple jar files with ByteBuddyJarsTask. Avoid validation of JarFile when extracting individual entries. Rework discovery in ByteBuddyMojo. 29. August 2024: version 1.15.1 Revert default EntryPoint for Android Gradle plugin to use DECORATE unless explicitly specified due to many generic type errors in Kotlin classes. 23. August 2024: version 1.15.0 Introduce AsmClassWriter and AsmClassReader abstractions that allow for plugging different implementations of readers and writers. Add configuration extension to the Android Gradle plugin and make it behave like regular Gradle plugin with standard configuration. Throw TypeNotPresentException upon discovering undeclared type variables as it was recently fixed on the JVM. 16. August 2024: version 1.14.19 Add Maven Mojo for transforming jars and for transforming dependencies folder. Better error handling for unresolved type variables. Allow loading arguments of the instrumented method in MemberSubstitution. Fix checks for method visibility. Commits https://github.com/raphw/byte-buddy/commit/ec6af4f7c3c1ca5b8e4b5ca719e1156ac452c33b";>ec6af4f [maven-release-plugin] prepare release byte-buddy-1.15.5 https://github.com/raphw/byte-buddy/commit/35b385696e501f47961f744c479673d8590b6aac";>35b3856 [release] Release new version https://github.com/raphw/byte-buddy/commit/9ba938e3c98e99fe18f3d01be89903727401913e";>9ba938e [release] Release new version https://github.com/raphw/byte-buddy/commit/f44bc5f5792665f2f16e33e708a1230713e0";>f44bc5f Oppdaterer checksums. https://github.com/raphw/byte-buddy/commit/a6a286da95012d0fe6a0176101bceea39dff4b41";>a6a286d Mr java8 (https://redirect.github.com/raphw/byte-buddy/issues/1719";>#1719) https://github.com/raphw/byte-buddy/commit/8a38f33e912fd7fa5a21d7a66bda2ca928161665";>8a38f33 Bump commons-io:commons-io in /byte-buddy-maven-plugin (https://redirect.github.com/raphw/byte-buddy/issues/1717";>#1717) https://github.com/raphw/byte-buddy/commit/e252dd89c0f2c9ee8cefe73983d4f06e11d5414d";>e252dd8 Update internal Byte Buddy and release notes. https://github.com/raphw/byte-buddy/commit/d2e1861d6656c7eebaa1c1be3a776c26905b
Re: [PR] Bump net.bytebuddy:byte-buddy from 1.14.18 to 1.15.4 [maven-plugin-tools]
dependabot[bot] closed pull request #331: Bump net.bytebuddy:byte-buddy from 1.14.18 to 1.15.4 URL: https://github.com/apache/maven-plugin-tools/pull/331 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump net.bytebuddy:byte-buddy from 1.14.18 to 1.15.4 [maven-plugin-tools]
dependabot[bot] commented on PR #331: URL: https://github.com/apache/maven-plugin-tools/pull/331#issuecomment-2419522585 Superseded by #332. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.resolver.version from 2.0.1 to 2.0.2 [maven-mvnd]
cstamas merged PR #1172: URL: https://github.com/apache/maven-mvnd/pull/1172 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Remove unused exclusions [maven]
cstamas opened a new pull request, #1814: URL: https://github.com/apache/maven/pull/1814 These exclusions were here for historical reasons, but are not needed anymore. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Delete obsolete commented code [maven-dependency-plugin]
elharo merged PR #446: URL: https://github.com/apache/maven-dependency-plugin/pull/446 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Maven Daemon doesn't download Core Extensions from pluginRepository defined in settings.xml [maven-mvnd]
cstamas commented on issue #1174: URL: https://github.com/apache/maven-mvnd/issues/1174#issuecomment-2420335902 Is there ANY chance to try your build by current master of mvnd? I know it is Maven 4 (not Maven 3 as in 1.0.2), but still... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Drop unused excludes [maven-mvnd]
cstamas merged PR #1173: URL: https://github.com/apache/maven-mvnd/pull/1173 -- 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] (MDEP-960) Silent logging somewhat broken in AbstractDependencyMojo
Elliotte Rusty Harold created MDEP-960: -- Summary: Silent logging somewhat broken in AbstractDependencyMojo Key: MDEP-960 URL: https://issues.apache.org/jira/browse/MDEP-960 Project: Maven Dependency Plugin Issue Type: Bug Reporter: Elliotte Rusty Harold Assignee: Elliotte Rusty Harold There's confusion between different SilentLogger classes, as well as a failure to reset the logger to non-silent when asked. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump net.bytebuddy:byte-buddy from 1.15.4 to 1.15.5 [maven]
dependabot[bot] opened a new pull request, #1817: URL: https://github.com/apache/maven/pull/1817 Bumps [net.bytebuddy:byte-buddy](https://github.com/raphw/byte-buddy) from 1.15.4 to 1.15.5. Release notes Sourced from https://github.com/raphw/byte-buddy/releases";>net.bytebuddy:byte-buddy's releases. Byte Buddy 1.15.5 Publish Byte Buddy and Byte Buddy agent artifacts as multi-release jars to support CDS and faster validation. Changelog Sourced from https://github.com/raphw/byte-buddy/blob/master/release-notes.md";>net.bytebuddy:byte-buddy's changelog. Byte Buddy release notes Commits https://github.com/raphw/byte-buddy/commit/ec6af4f7c3c1ca5b8e4b5ca719e1156ac452c33b";>ec6af4f [maven-release-plugin] prepare release byte-buddy-1.15.5 https://github.com/raphw/byte-buddy/commit/35b385696e501f47961f744c479673d8590b6aac";>35b3856 [release] Release new version https://github.com/raphw/byte-buddy/commit/9ba938e3c98e99fe18f3d01be89903727401913e";>9ba938e [release] Release new version https://github.com/raphw/byte-buddy/commit/f44bc5f5792665f2f16e33e708a1230713e0";>f44bc5f Oppdaterer checksums. https://github.com/raphw/byte-buddy/commit/a6a286da95012d0fe6a0176101bceea39dff4b41";>a6a286d Mr java8 (https://redirect.github.com/raphw/byte-buddy/issues/1719";>#1719) https://github.com/raphw/byte-buddy/commit/8a38f33e912fd7fa5a21d7a66bda2ca928161665";>8a38f33 Bump commons-io:commons-io in /byte-buddy-maven-plugin (https://redirect.github.com/raphw/byte-buddy/issues/1717";>#1717) https://github.com/raphw/byte-buddy/commit/e252dd89c0f2c9ee8cefe73983d4f06e11d5414d";>e252dd8 Update internal Byte Buddy and release notes. https://github.com/raphw/byte-buddy/commit/d2e1861d6656c7eebaa1c1be3a776c26905bca48";>d2e1861 [maven-release-plugin] prepare for next development iteration See full diff in https://github.com/raphw/byte-buddy/compare/byte-buddy-1.15.4...byte-buddy-1.15.5";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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
[PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.20 to 2.0.2 [maven-wrapper]
dependabot[bot] opened a new pull request, #156: URL: https://github.com/apache/maven-wrapper/pull/156 Bumps [org.apache.maven.resolver:maven-resolver-api](https://github.com/apache/maven-resolver) from 1.9.20 to 2.0.2. Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.20...maven-resolver-2.0.2";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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
Re: [PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.20 to 2.0.1 [maven-wrapper]
dependabot[bot] commented on PR #150: URL: https://github.com/apache/maven-wrapper/pull/150#issuecomment-2421077707 Superseded by #156. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven.resolver:maven-resolver-api from 1.9.20 to 2.0.1 [maven-wrapper]
dependabot[bot] closed pull request #150: Bump org.apache.maven.resolver:maven-resolver-api from 1.9.20 to 2.0.1 URL: https://github.com/apache/maven-wrapper/pull/150 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8320] Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR [maven]
cdouillard commented on PR #1729: URL: https://github.com/apache/maven/pull/1729#issuecomment-2420706679 Hi @gnodet, is the aim of this version change to use the multi-release jar ? From what I see in the tag notes ([2.0.1.MR Service Release (jakarta.inject) ](https://github.com/jakartaee/inject/releases/tag/2.0.1.MR)) : > This is an experimental release to allow users to choose between this format of a modularized api jar and the 2.0.1 release that has the module-info.class in the root of the jar as is the convention adopted for EE10. Unless there is user feedback that this format has sufficient advantages over the 2.0.1 release format, this is not a format we intend to support in the future. Since Maven 4 requires Java 17, I don't think this version change is necessary. Tags notes are avalaible here : - [2.0.1 Service Release (jakarta.inject)](https://github.com/jakartaee/inject/releases/tag/2.0.1) - [2.0.1.MR Service Release (jakarta.inject)](https://github.com/jakartaee/inject/releases/tag/2.0.1.MR) -- 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] (MPH-193) Document charset for evaluate goal file output
[
https://issues.apache.org/jira/browse/MPH-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-193:
---
Fix Version/s: 3.5.1
> Document charset for evaluate goal file output
> --
>
> Key: MPH-193
> URL: https://issues.apache.org/jira/browse/MPH-193
> Project: Maven Help Plugin
> Issue Type: Improvement
> Components: evaluate
>Affects Versions: 3.3.0
>Reporter: Garret Wilson
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.1
>
>
> I'm using Java 17 on Windows with
> `org.apache.maven.plugins:maven-help-plugin:3.3.0`. The
> [{{}}|https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html#output]
> option allows the evaluated information to be sent to a file. But the
> documentation does not say which charset will be used!
> I was afraid that you might be using the system default charset (which would
> be very bad). But I did a test:
> {code:xml}
>
>
>
> …
>
> org.apache.maven.plugins
> maven-help-plugin
>
>
> foobar
> generate-resources
>
> evaluate
>
>
> foo
> ${project.build.directory}/foo.xml
>
>
>
>
> {code}
> It was a huge relief to find that the output file {{foo.xml}} contained the
> word "touché" followed by a smiley face emoticon, encoded in UTF-8!
> It is a very good thing that you are encoding the file output in UTF-8 and
> not some arbitrary, per-system encoding. But this needs to be documented so
> we'll know that we can depend on that. Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPH-193) Document charset for evaluate goal file output
[
https://issues.apache.org/jira/browse/MPH-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890812#comment-17890812
]
ASF GitHub Bot commented on MPH-193:
michael-o opened a new pull request, #123:
URL: https://github.com/apache/maven-help-plugin/pull/123
This closes #123
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MPH) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line
and body.
- [ ] Format the pull request title like `[MPH-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MPH-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.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [ ] You have run the integration tests successfully (`mvn -Prun-its clean
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] 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).
> Document charset for evaluate goal file output
> --
>
> Key: MPH-193
> URL: https://issues.apache.org/jira/browse/MPH-193
> Project: Maven Help Plugin
> Issue Type: Improvement
> Components: evaluate
>Affects Versions: 3.3.0
>Reporter: Garret Wilson
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.1
>
>
> I'm using Java 17 on Windows with
> `org.apache.maven.plugins:maven-help-plugin:3.3.0`. The
> [{{}}|https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html#output]
> option allows the evaluated information to be sent to a file. But the
> documentation does not say which charset will be used!
> I was afraid that you might be using the system default charset (which would
> be very bad). But I did a test:
> {code:xml}
>
>
>
> …
>
> org.apache.maven.plugins
> maven-help-plugin
>
>
> foobar
> generate-resources
>
> evaluate
>
>
> foo
> ${project.build.directory}/foo.xml
>
>
>
>
> {code}
> It was a huge relief to find that the output file {{foo.xml}} contained the
> word "touché" followed by a smiley face emoticon, encoded in UTF-8!
> It is a very good thing that you are encoding the file output in UTF-8 and
> not some arbitrary, per-system encoding. But this needs to be documented so
> we'll know that we can depend on that. Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [MPH-193] Document charset for evaluate goal file output [maven-help-plugin]
michael-o opened a new pull request, #123: URL: https://github.com/apache/maven-help-plugin/pull/123 This closes #123 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPH) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MPH-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MPH-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. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] 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] [Created] (MNG-8325) The ReactorReader should know about build/consumer POMs
Guillaume Nodet created MNG-8325: Summary: The ReactorReader should know about build/consumer POMs Key: MNG-8325 URL: https://issues.apache.org/jira/browse/MNG-8325 Project: Maven Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0-beta-5 When loading a model from the project local repository, the ReactorReader should know about build/consumer POM and return the consumer POM. The build model may be missing some information. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MPH-193) Document charset for evaluate goal file output.
[
https://issues.apache.org/jira/browse/MPH-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPH-193:
---
Priority: Minor (was: Major)
> Document charset for evaluate goal file output.
> ---
>
> Key: MPH-193
> URL: https://issues.apache.org/jira/browse/MPH-193
> Project: Maven Help Plugin
> Issue Type: Improvement
> Components: evaluate
>Affects Versions: 3.3.0
>Reporter: Garret Wilson
>Assignee: Michael Osipov
>Priority: Minor
>
> I'm using Java 17 on Windows with
> `org.apache.maven.plugins:maven-help-plugin:3.3.0`. The
> [{{}}|https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html#output]
> option allows the evaluated information to be sent to a file. But the
> documentation does not say which charset will be used!
> I was afraid that you might be using the system default charset (which would
> be very bad). But I did a test:
> {code:xml}
>
>
>
> …
>
> org.apache.maven.plugins
> maven-help-plugin
>
>
> foobar
> generate-resources
>
> evaluate
>
>
> foo
> ${project.build.directory}/foo.xml
>
>
>
>
> {code}
> It was a huge relief to find that the output file {{foo.xml}} contained the
> word "touché" followed by a smiley face emoticon, encoded in UTF-8!
> It is a very good thing that you are encoding the file output in UTF-8 and
> not some arbitrary, per-system encoding. But this needs to be documented so
> we'll know that we can depend on that. Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MPH-193) Document charset for evaluate goal file output.
[
https://issues.apache.org/jira/browse/MPH-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPH-193:
--
Assignee: Michael Osipov
> Document charset for evaluate goal file output.
> ---
>
> Key: MPH-193
> URL: https://issues.apache.org/jira/browse/MPH-193
> Project: Maven Help Plugin
> Issue Type: Improvement
> Components: evaluate
>Affects Versions: 3.3.0
>Reporter: Garret Wilson
>Assignee: Michael Osipov
>Priority: Major
>
> I'm using Java 17 on Windows with
> `org.apache.maven.plugins:maven-help-plugin:3.3.0`. The
> [{{}}|https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html#output]
> option allows the evaluated information to be sent to a file. But the
> documentation does not say which charset will be used!
> I was afraid that you might be using the system default charset (which would
> be very bad). But I did a test:
> {code:xml}
>
>
>
> …
>
> org.apache.maven.plugins
> maven-help-plugin
>
>
> foobar
> generate-resources
>
> evaluate
>
>
> foo
> ${project.build.directory}/foo.xml
>
>
>
>
> {code}
> It was a huge relief to find that the output file {{foo.xml}} contained the
> word "touché" followed by a smiley face emoticon, encoded in UTF-8!
> It is a very good thing that you are encoding the file output in UTF-8 and
> not some arbitrary, per-system encoding. But this needs to be documented so
> we'll know that we can depend on that. Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPH-193) Document charset for evaluate goal file output
[
https://issues.apache.org/jira/browse/MPH-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890813#comment-17890813
]
ASF GitHub Bot commented on MPH-193:
michael-o commented on PR #123:
URL:
https://github.com/apache/maven-help-plugin/pull/123#issuecomment-2421585042
No change in behavior, but simply swapped the Plexus wrapper for Java NIO
class.
> Document charset for evaluate goal file output
> --
>
> Key: MPH-193
> URL: https://issues.apache.org/jira/browse/MPH-193
> Project: Maven Help Plugin
> Issue Type: Improvement
> Components: evaluate
>Affects Versions: 3.3.0
>Reporter: Garret Wilson
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.1
>
>
> I'm using Java 17 on Windows with
> `org.apache.maven.plugins:maven-help-plugin:3.3.0`. The
> [{{}}|https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html#output]
> option allows the evaluated information to be sent to a file. But the
> documentation does not say which charset will be used!
> I was afraid that you might be using the system default charset (which would
> be very bad). But I did a test:
> {code:xml}
>
>
>
> …
>
> org.apache.maven.plugins
> maven-help-plugin
>
>
> foobar
> generate-resources
>
> evaluate
>
>
> foo
> ${project.build.directory}/foo.xml
>
>
>
>
> {code}
> It was a huge relief to find that the output file {{foo.xml}} contained the
> word "touché" followed by a smiley face emoticon, encoded in UTF-8!
> It is a very good thing that you are encoding the file output in UTF-8 and
> not some arbitrary, per-system encoding. But this needs to be documented so
> we'll know that we can depend on that. Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8320) Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR
[ https://issues.apache.org/jira/browse/MNG-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8320: - Fix Version/s: wontfix-candidate (was: 4.0.0-beta-5) > Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR > - > > Key: MNG-8320 > URL: https://issues.apache.org/jira/browse/MNG-8320 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: wontfix-candidate > > > GitHub Pull Request: https://github.com/apache/maven/pull/1729 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (MNG-8320) Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR
[ https://issues.apache.org/jira/browse/MNG-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reopened MNG-8320: -- > Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR > - > > Key: MNG-8320 > URL: https://issues.apache.org/jira/browse/MNG-8320 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1729 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump resolver.version from 1.9.22 to 2.0.2 [maven-indexer]
dependabot[bot] opened a new pull request, #391: URL: https://github.com/apache/maven-indexer/pull/391 Bumps `resolver.version` from 1.9.22 to 2.0.2. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.22 to 2.0.2 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.22...maven-resolver-2.0.2";>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.22 to 2.0.2 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-util's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.22...maven-resolver-2.0.2";
Re: [PR] Bump org.apache.maven.resolver:maven-resolver-api from 2.0.0 to 2.0.1 [maven-install-plugin]
dependabot[bot] commented on PR #78: URL: https://github.com/apache/maven-install-plugin/pull/78#issuecomment-2421369677 Superseded by #87. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.apache.maven.resolver:maven-resolver-api from 2.0.0 to 2.0.2 [maven-install-plugin]
dependabot[bot] opened a new pull request, #87: URL: https://github.com/apache/maven-install-plugin/pull/87 Bumps [org.apache.maven.resolver:maven-resolver-api](https://github.com/apache/maven-resolver) from 2.0.0 to 2.0.2. Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.0...maven-resolver-2.0.2";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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
Re: [PR] Bump org.apache.maven.resolver:maven-resolver-api from 2.0.0 to 2.0.1 [maven-install-plugin]
dependabot[bot] closed pull request #78: Bump org.apache.maven.resolver:maven-resolver-api from 2.0.0 to 2.0.1 URL: https://github.com/apache/maven-install-plugin/pull/78 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump resolver.version from 1.9.20 to 2.0.1 [maven-indexer]
dependabot[bot] closed pull request #381: Bump resolver.version from 1.9.20 to 2.0.1 URL: https://github.com/apache/maven-indexer/pull/381 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump resolver.version from 1.9.20 to 2.0.1 [maven-indexer]
dependabot[bot] commented on PR #381: URL: https://github.com/apache/maven-indexer/pull/381#issuecomment-2421369147 Superseded by #391. -- 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] (MPH-204) Use pluginRepositories not repositories
[ https://issues.apache.org/jira/browse/MPH-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890804#comment-17890804 ] Michael Osipov commented on MPH-204: Is this still an issue? > Use pluginRepositories not repositories > --- > > Key: MPH-204 > URL: https://issues.apache.org/jira/browse/MPH-204 > Project: Maven Help Plugin > Issue Type: Bug > Components: describe >Affects Versions: 3.4.0 >Reporter: Delany >Priority: Major > Labels: up-for-grabs > > The describe goal should retrieve the requested artifact from the available > pluginRepositories, not from repositories. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8326) The ModelBuilder cannot import BOM with classifiers
Guillaume Nodet created MNG-8326: Summary: The ModelBuilder cannot import BOM with classifiers Key: MNG-8326 URL: https://issues.apache.org/jira/browse/MNG-8326 Project: Maven Issue Type: Bug Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.0.0-beta-5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump resolverVersion from 1.9.20 to 2.0.2 [maven-artifact-plugin]
dependabot[bot] opened a new pull request, #64: URL: https://github.com/apache/maven-artifact-plugin/pull/64 Bumps `resolverVersion` from 1.9.20 to 2.0.2. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.20 to 2.0.2 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-api's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.20...maven-resolver-2.0.2";>compare view Updates `org.apache.maven.resolver:maven-resolver-util` from 1.9.20 to 2.0.2 Release notes Sourced from https://github.com/apache/maven-resolver/releases";>org.apache.maven.resolver:maven-resolver-util's releases. 2.0.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354988";>Release Notes - Maven Resolver - Version 2.0.2 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/2f112ff3ff45c153bd1714120c7c9a225b3ab3f2";>2f112ff [maven-release-plugin] prepare release maven-resolver-2.0.2 https://github.com/apache/maven-resolver/commit/fdefb394952c81754568b64a2d3b34194d3bb0ba";>fdefb39 Update CI maven to 3.9.9 https://github.com/apache/maven-resolver/commit/f65d0ac76a04e0be9153caff5828ca00dc9d15ac";>f65d0ac [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport (#... https://github.com/apache/maven-resolver/commit/2089216fc558ae185f16dbb629d9d480b5abe4f4";>2089216 Last minute update of minio https://github.com/apache/maven-resolver/commit/8b0c7ff87886f395aab509ee13e094d2faaca455";>8b0c7ff [MRESOLVER-605] Linking support in file transporter (https://redirect.github.com/apache/maven-resolver/issues/578";>#578) https://github.com/apache/maven-resolver/commit/7b9214f0a8c3adc9f286cb01fa8d81dc0d91b2bd";>7b9214f [MRESOLVER-599] Sigstore Artifact Generator (https://redirect.github.com/apache/maven-resolver/issues/573";>#573) https://github.com/apache/maven-resolver/commit/0b163cdf2863271feb30f746f49e2b4d51cb23ac";>0b163cd Add since per package https://github.com/apache/maven-resolver/commit/7eb537860997bc9127d5d86e41964dcbf15b8e87";>7eb5378 [MRESOLVER-541] S3 Transport using MinIO (https://redirect.github.com/apache/maven-resolver/issues/553";>#553) https://github.com/apache/maven-resolver/commit/1200b9f524ecb005d94a43e02546448ff3893ed2";>1200b9f [MRESOLVER-604] Make config properties metadata available (https://redirect.github.com/apache/maven-resolver/issues/574";>#574) https://github.com/apache/maven-resolver/commit/92b46ba9daf7f29cea812397d098288e568e1e7e";>92b46ba [MRESOLVER-600] RFC9457 Implementation (https://redirect.github.com/apache/maven-resolver/issues/576";>#576) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.20...maven-resolver-2.
Re: [PR] [MNG-8320] Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR [maven]
gnodet commented on PR #1729: URL: https://github.com/apache/maven/pull/1729#issuecomment-2421140460 > Hi @gnodet, is the aim of this version change to use the multi-release jar ? > > From what I see in the tag notes ([2.0.1.MR Service Release (jakarta.inject) ](https://github.com/jakartaee/inject/releases/tag/2.0.1.MR)) : > > > This is an experimental release to allow users to choose between this format of a modularized api jar and the 2.0.1 release that has the module-info.class in the root of the jar as is the convention adopted for EE10. Unless there is user feedback that this format has sufficient advantages over the 2.0.1 release format, this is not a format we intend to support in the future. > > Since Maven 4 requires Java 17, I don't think this version change is necessary. > > Tags notes are avalaible here : > > * [2.0.1 Service Release (jakarta.inject)](https://github.com/jakartaee/inject/releases/tag/2.0.1) > * [2.0.1.MR Service Release (jakarta.inject)](https://github.com/jakartaee/inject/releases/tag/2.0.1.MR) You're absolutely right, I misread the release notes. -- 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-8320) Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR
[ https://issues.apache.org/jira/browse/MNG-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890779#comment-17890779 ] Guillaume Nodet commented on MNG-8320: -- Reverted > Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR > - > > Key: MNG-8320 > URL: https://issues.apache.org/jira/browse/MNG-8320 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: wontfix-candidate > > > GitHub Pull Request: https://github.com/apache/maven/pull/1729 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8320) Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR
[ https://issues.apache.org/jira/browse/MNG-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8320. Resolution: Won't Fix > Bump jakarta.inject:jakarta.inject-api from 2.0.1 to 2.0.1.MR > - > > Key: MNG-8320 > URL: https://issues.apache.org/jira/browse/MNG-8320 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: wontfix-candidate > > > GitHub Pull Request: https://github.com/apache/maven/pull/1729 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8324) Bump net.bytebuddy:byte-buddy from 1.15.4 to 1.15.5
Guillaume Nodet created MNG-8324: Summary: Bump net.bytebuddy:byte-buddy from 1.15.4 to 1.15.5 Key: MNG-8324 URL: https://issues.apache.org/jira/browse/MNG-8324 Project: Maven Issue Type: Task Reporter: Guillaume Nodet GitHub Pull Request: https://github.com/apache/maven/pull/1817 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-8324) Bump net.bytebuddy:byte-buddy from 1.15.4 to 1.15.5
[ https://issues.apache.org/jira/browse/MNG-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet closed MNG-8324. Fix Version/s: 4.0.0-beta-5 Assignee: Guillaume Nodet Resolution: Fixed > Bump net.bytebuddy:byte-buddy from 1.15.4 to 1.15.5 > --- > > Key: MNG-8324 > URL: https://issues.apache.org/jira/browse/MNG-8324 > Project: Maven > Issue Type: Task >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-beta-5 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1817 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8324] Bump net.bytebuddy:byte-buddy from 1.15.4 to 1.15.5 [maven]
gnodet merged PR #1817: URL: https://github.com/apache/maven/pull/1817 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1 [maven-mvnd]
gnodet commented on PR #1065: URL: https://github.com/apache/maven-mvnd/pull/1065#issuecomment-2421219343 @dependabot reopen -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1 [maven-mvnd]
dependabot[bot] opened a new pull request, #1065: URL: https://github.com/apache/maven-mvnd/pull/1065 Bumps [jakarta.inject:jakarta.inject-api](https://github.com/eclipse-ee4j/injection-api) from 1.0 to 2.0.1. Release notes Sourced from https://github.com/eclipse-ee4j/injection-api/releases";>jakarta.inject:jakarta.inject-api's releases. 2.0.1.RC1 Service Release This release add an explicit module-info class, and Java 8 source/target levels. https://redirect.github.com/eclipse-ee4j/injection-api/issues/17";>#17 https://redirect.github.com/eclipse-ee4j/injection-api/issues/18";>#18 RC for Jakarta EE 9 Effort This is an initial release candidate for the javax to jakarta package namespace change for Jakarta EE 9 1.0.3 Service Release This release corrects the 1.0.2 release which was incorrectly done from the master branch with the jakarta.* packages. It adds the Automatic-Module-Name=java.inject to the api jar manifest. 1.0.2 Service Release A service release that addresses: Address https://redirect.github.com/eclipse-ee4j/injection-api/issues/14";>#14 , set Automatic-Module-Name to java.inject Address https://redirect.github.com/eclipse-ee4j/injection-api/issues/15";>#15 , add OSGi bundle headers Commits https://github.com/jakartaee/inject/commit/80c9e1267db53d0d5fd7b2afb2fe6a6283a3f43a";>80c9e12 [maven-release-plugin] prepare release 2.0.1 https://github.com/jakartaee/inject/commit/7c66336a5801f2520a5b372c35c48a2c6917b390";>7c66336 Merge pull request https://redirect.github.com/eclipse-ee4j/injection-api/issues/25";>#25 from jakartaredhat/root-mi https://github.com/jakartaee/inject/commit/75d0db99f19562add74faa9a098d83a85b33160b";>75d0db9 An alternate way to build Java 8 source/target jar with Java 8 module-info.class https://github.com/jakartaee/inject/commit/fced20c7b55ba7d3884842bccf2c749ceb2a537a";>fced20c [maven-release-plugin] prepare for next development iteration https://github.com/jakartaee/inject/commit/f32706e1cf7e4836aa30669bb07512ef3533109c";>f32706e [maven-release-plugin] prepare release 2.0.1.RC1 https://github.com/jakartaee/inject/commit/f0905374c201fe40d51d41b33a99ea8c4dd04b65";>f090537 Merge pull request https://redirect.github.com/eclipse-ee4j/injection-api/issues/22";>#22 from rbygrave/feature/javadoc-tt-to-code https://github.com/jakartaee/inject/commit/ca549ae367166ece1f2588fe8ab44169f7fdc509";>ca549ae Merge pull request https://redirect.github.com/eclipse-ee4j/injection-api/issues/20";>#20 from rbygrave/feature/moditech-module-info https://github.com/jakartaee/inject/commit/afb602b3ee35faf2da8a3d9eb4c128018f71f44a";>afb602b Build as multi-release jar https://github.com/jakartaee/inject/commit/777bb396cdae9f24a79c87180e4438c77d082279";>777bb39 https://redirect.github.com/eclipse-ee4j/injection-api/issues/20";>#20 add module-info without multi-version jar https://github.com/jakartaee/inject/commit/f32375cc1094e85a135185e01de71c352d4ba888";>f32375c Change javadocAdditional commits viewable in https://github.com/eclipse-ee4j/injection-api/compare/1.0...2.0.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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
Re: [PR] Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1.MR [maven-mvnd]
gnodet closed pull request #1142: Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1.MR URL: https://github.com/apache/maven-mvnd/pull/1142 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1.MR [maven-mvnd]
dependabot[bot] commented on PR #1142: URL: https://github.com/apache/maven-mvnd/pull/1142#issuecomment-2421219512 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Import w/ classifier [maven]
cstamas opened a new pull request, #1815: URL: https://github.com/apache/maven/pull/1815 Only from Model 4.1.0+ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Remove unused exclusions [maven]
cstamas merged PR #1814: URL: https://github.com/apache/maven/pull/1814 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Import w/ classifier [maven]
cstamas closed pull request #1815: Import w/ classifier URL: https://github.com/apache/maven/pull/1815 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] The mvnd client does not honour properties from `maven.properties` [maven-mvnd]
gnodet commented on issue #1165: URL: https://github.com/apache/maven-mvnd/issues/1165#issuecomment-2419909979 I suppose it should work now, I need to double check -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] The mvnd client does not honour properties from `maven.properties` [maven-mvnd]
gnodet closed issue #1165: The mvnd client does not honour properties from `maven.properties` URL: https://github.com/apache/maven-mvnd/issues/1165 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] The mvnd client does not honour properties from `maven.properties` [maven-mvnd]
gnodet commented on issue #1165: URL: https://github.com/apache/maven-mvnd/issues/1165#issuecomment-2419984001 Yes, it's working. -- 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
