[jira] [Commented] (MDEP-956) silent parameter is not taken into account
[
https://issues.apache.org/jira/browse/MDEP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888901#comment-17888901
]
ASF GitHub Bot commented on MDEP-956:
-
elharo opened a new pull request, #436:
URL: https://github.com/apache/maven-dependency-plugin/pull/436
(no comment)
> silent parameter is not taken into account
> --
>
> Key: MDEP-956
> URL: https://issues.apache.org/jira/browse/MDEP-956
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 3.7.0, 3.7.1, 3.8.0
>Reporter: Philippe De Neve
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> When setting the {{silent}} parameter to {{{}true{}}}, the
> {{copy-dependencies}} goal remains non-silent.
> To reproduce:
> {code:bash}
> git clone https://gitlab.com/philippedn/jli.git
> cd jli/demos/jfxm
> mvn prepare-package # silent parameter set to true in pom.xml
> {code}
> Output:
> {code:bash}
> ...
> [INFO] Copying artifact 'org.openjfx:javafx-controls:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-controls:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-graphics:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-graphics:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump org.apache.maven:maven-core from 3.0 to 3.8.1 in /src/it/transitive-excludes [maven-ear-plugin]
slachiewicz merged PR #95: URL: https://github.com/apache/maven-ear-plugin/pull/95 -- 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 commons-io:commons-io from 2.11.0 to 2.14.0 in /src/it/packaging-includes [maven-ear-plugin]
dependabot[bot] opened a new pull request, #120: URL: https://github.com/apache/maven-ear-plugin/pull/120 Bumps commons-io:commons-io from 2.11.0 to 2.14.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-ear-plugin/network/alerts). -- 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.codehaus.plexus:plexus-utils from 3.5.1 to 4.0.1 [maven-ear-plugin]
slachiewicz merged PR #117: URL: https://github.com/apache/maven-ear-plugin/pull/117 -- 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 commons-io:commons-io from 2.11.0 to 2.14.0 in /src/it/skinny-wars-javaee5/war-module3 [maven-ear-plugin]
dependabot[bot] opened a new pull request, #121: URL: https://github.com/apache/maven-ear-plugin/pull/121 Bumps commons-io:commons-io from 2.11.0 to 2.14.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-ear-plugin/network/alerts). -- 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] [MRESOLVER-605] Linking support in file transporter [maven-resolver]
cstamas merged PR #578: URL: https://github.com/apache/maven-resolver/pull/578 -- 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] (MRESOLVER-605) FileTransporter should offer symlink, hardlink ops aside of existing copy (experimental)
[ https://issues.apache.org/jira/browse/MRESOLVER-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-605. - Resolution: Fixed > FileTransporter should offer symlink, hardlink ops aside of existing copy > (experimental) > > > Key: MRESOLVER-605 > URL: https://issues.apache.org/jira/browse/MRESOLVER-605 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > > FileTransport is a "remote repository" transport that is using FS, hence, is > most probably "local" to Resolver process (does not have to be, ie. use of > NFS mount or alike). > Hence, FileTransport should offer some means to not copy but link the files. > FileTranport is usually used in tests and alike, so doing this would lessen > disk store usage and even execution times. > Still, given FileTranport is "remote" transport, checksumming must happen, > hence file being transported must be read (so gain is not "just link it", is > way less). > Big fat note: this change will cause that symlinks may land in local > repository. This change does NOT enforce rest of Maven plugins knows how to > handle them, is out of scope. > Other alternative for "local test setups" is ChainedLocalRepository. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-605) FileTransporter should offer symlink, hardlink ops aside of existing copy (experimental)
[ https://issues.apache.org/jira/browse/MRESOLVER-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-605: -- Summary: FileTransporter should offer symlink, hardlink ops aside of existing copy (experimental) (was: FileTransporter should offer symlink, hardlink ops aside of existing copy) > FileTransporter should offer symlink, hardlink ops aside of existing copy > (experimental) > > > Key: MRESOLVER-605 > URL: https://issues.apache.org/jira/browse/MRESOLVER-605 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > > FileTransport is a "remote repository" transport that is using FS, hence, is > most probably "local" to Resolver process (does not have to be, ie. use of > NFS mount or alike). > Hence, FileTransport should offer some means to not copy but link the files. > FileTranport is usually used in tests and alike, so doing this would lessen > disk store usage and even execution times. > Still, given FileTranport is "remote" transport, checksumming must happen, > hence file being transported must be read (so gain is not "just link it", is > way less). > Big fat note: this change will cause that symlinks may land in local > repository. This change does NOT enforce rest of Maven plugins knows how to > handle them, is out of scope. > Other alternative for "local test setups" is ChainedLocalRepository. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEAR-324) Bump plexus-utils from 3.4.2 to 4.0.1
[ https://issues.apache.org/jira/browse/MEAR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEAR-324: -- Summary: Bump plexus-utils from 3.4.2 to 4.0.1 (was: Bump plexus-utils from 3.4.2 to 3.5.1) > Bump plexus-utils from 3.4.2 to 4.0.1 > - > > Key: MEAR-324 > URL: https://issues.apache.org/jira/browse/MEAR-324 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEAR-325) Bump maven-filtering from 3.3.0 to 3.4.0
[ https://issues.apache.org/jira/browse/MEAR-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEAR-325: -- Summary: Bump maven-filtering from 3.3.0 to 3.4.0 (was: Bump maven-filtering from 3.3.0 to 3.3.1) > Bump maven-filtering from 3.3.0 to 3.4.0 > > > Key: MEAR-325 > URL: https://issues.apache.org/jira/browse/MEAR-325 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEAR-325) Bump maven-filtering from 3.3.0 to 3.3.1
[ https://issues.apache.org/jira/browse/MEAR-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888920#comment-17888920 ] ASF GitHub Bot commented on MEAR-325: - slachiewicz merged PR #115: URL: https://github.com/apache/maven-ear-plugin/pull/115 > Bump maven-filtering from 3.3.0 to 3.3.1 > > > Key: MEAR-325 > URL: https://issues.apache.org/jira/browse/MEAR-325 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MEAR-325] Bump org.apache.maven.shared:maven-filtering from 3.3.1 to 3.4.0 [maven-ear-plugin]
slachiewicz merged PR #115: URL: https://github.com/apache/maven-ear-plugin/pull/115 -- 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] (MDEP-955) unpack ignores global fileMappers
[
https://issues.apache.org/jira/browse/MDEP-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888900#comment-17888900
]
Elliotte Rusty Harold commented on MDEP-955:
Good analysis. Thanks. Looksm like we should also remove setFileMappers and
getFileMappers from Artifactitem
> unpack ignores global fileMappers
> -
>
> Key: MDEP-955
> URL: https://issues.apache.org/jira/browse/MDEP-955
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
>Affects Versions: 3.8.0
> Environment: Windows 11, Java 21, Maven 3.8.6, Maven Dependency
> Plugin 3.8.0
>Reporter: Jonah Bauer
>Priority: Major
>
> I was trying to use the {{unpack}} goal to unpack multiple artifacts with a
> similar structure (namely webjars) and rewrite their filenames using a common
> file mapper. The {{unpack}} goal conveniently defines the property
> {{fileMappers}} which seems suited for this use case. The configuration is as
> follows
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.8.0
>
>
> unpack-libraries
> generate-resources
>
> unpack
>
>
>
>
> org.webjars.npm
> chart.js
> ${chartjs.version}
>
>
> org.webjars.npm
> chartjs-adapter-date-fns
> 3.0.0
>
>
> META-INF/resources/webjars/*/*/dist/**
>
> ${project.build.directory}/generated-resources/libraries
>
>
>
>
> ^META-INF/resources/webjars/([^/]+)/[^/]+/dist/
> ./$1/
>
>
>
>
>
>
>
> {code}
> This, however, does not work. While the artifacts are unpacked to the target
> directory, the globally configured {{fileMappers}} did not seem to take any
> effect.
> After looking into the code of {{UnpackMojo}} it seems the
> {{UnpackMojo::getFileMappers}} method is unused. In
> {{UnpackMojo::getProcessedArtifactItems}} the {{includes}} and {{excludes}}
> of each artifact item are set to the globally configured values if empty, but
> the file mappers are left unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8301) [REGRESSION] Not possible to build a project without modelVersion=4.1.0 but with 4.1.0 (beta-4) XSD
[
https://issues.apache.org/jira/browse/MNG-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders updated MNG-8301:
-
Description:
A project whose pom.xml refers to the [4.0.0-beta-4
XSD|https://maven.apache.org/xsd/maven-4.1.0-beta-4.xsd] and that lacks a
{{modelVersion}} element used to be buildable with Maven 4.0.0-beta-4. Maven
would infer from the XSD that it should use _modelVersion_ 4.1.0.
With the current snapshots of 4.0.0-beta-5, it can no longer be built:
{quote}{{[ERROR] The project org.apache.maven.its.mng8301:module-b:1-SNAPSHOT
(/Users/maarten/Code/open-source/maven/m4-no-modelversion-repro/module-b/pom.xml)
has 1 error}}
{{[ERROR] 'dependencies.dependency.version' for
org.apache.maven.repro:module-a:jar is missing. @
org.apache.maven.its.mng8301:module-b:[unknown-version],
file:///Users/maarten/Code/open-source/maven/m4-no-modelversion-repro/module-b/pom.xml,
line 17, column 9}}
{quote}
was:
A project whose pom.xml refers to the [4.0.0-beta-4
XSD|https://maven.apache.org/xsd/maven-4.1.0-beta-4.xsd] and that lacks a
{{modelVersion}} element used to be buildable with Maven 4.0.0-beta-4. Maven
would infer from the XSD that it should use _modelVersion_ 4.1.0.
With the current snapshots of 4.0.0-beta-5, it can no longer be built.
> [REGRESSION] Not possible to build a project without modelVersion=4.1.0 but
> with 4.1.0 (beta-4) XSD
> ---
>
> Key: MNG-8301
> URL: https://issues.apache.org/jira/browse/MNG-8301
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 4.0.0-beta-5
> Environment: Apache Maven 4.0.0-beta-5-SNAPSHOT
> (fee69f2f89c6f32dbef0ec55a7f6e8c071d4b6a9)
> Java version: 23, vendor: Eclipse Adoptium, runtime:
> /Library/Java/JavaVirtualMachines/temurin-23.jdk/Contents/Home
> OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac"
>Reporter: Didier Loiseau
>Priority: Major
>
> A project whose pom.xml refers to the [4.0.0-beta-4
> XSD|https://maven.apache.org/xsd/maven-4.1.0-beta-4.xsd] and that lacks a
> {{modelVersion}} element used to be buildable with Maven 4.0.0-beta-4. Maven
> would infer from the XSD that it should use _modelVersion_ 4.1.0.
> With the current snapshots of 4.0.0-beta-5, it can no longer be built:
> {quote}{{[ERROR] The project
> org.apache.maven.its.mng8301:module-b:1-SNAPSHOT
> (/Users/maarten/Code/open-source/maven/m4-no-modelversion-repro/module-b/pom.xml)
> has 1 error}}
> {{[ERROR] 'dependencies.dependency.version' for
> org.apache.maven.repro:module-a:jar is missing. @
> org.apache.maven.its.mng8301:module-b:[unknown-version],
> file:///Users/maarten/Code/open-source/maven/m4-no-modelversion-repro/module-b/pom.xml,
> line 17, column 9}}
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MEAR-327) Upgrade Parent to 43, require Maven 3.6.3
[ https://issues.apache.org/jira/browse/MEAR-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1788#comment-1788 ] ASF GitHub Bot commented on MEAR-327: - slachiewicz opened a new pull request, #119: URL: https://github.com/apache/maven-ear-plugin/pull/119 (no comment) > Upgrade Parent to 43, require Maven 3.6.3 > - > > Key: MEAR-327 > URL: https://issues.apache.org/jira/browse/MEAR-327 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEAR-327) Upgrade Parent to 43, require Maven 3.6.3
[ https://issues.apache.org/jira/browse/MEAR-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEAR-327: -- Summary: Upgrade Parent to 43, require Maven 3.6.3 (was: Upgrade Parent to 43) > Upgrade Parent to 43, require Maven 3.6.3 > - > > Key: MEAR-327 > URL: https://issues.apache.org/jira/browse/MEAR-327 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MEAR-327] Update to parent pom 43, require Maven 3.6.3 [maven-ear-plugin]
slachiewicz merged PR #119: URL: https://github.com/apache/maven-ear-plugin/pull/119 -- 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] [MEAR-327] update to parent pom 39 [maven-ear-plugin]
slachiewicz closed pull request #97: [MEAR-327] update to parent pom 39 URL: https://github.com/apache/maven-ear-plugin/pull/97 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MEAR-327] update to parent pom 39 [maven-ear-plugin]
slachiewicz commented on PR #97: URL: https://github.com/apache/maven-ear-plugin/pull/97#issuecomment-2408549596 Superseded by #119 -- 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] (MEAR-327) Upgrade Parent to 43, require Maven 3.6.3
[ https://issues.apache.org/jira/browse/MEAR-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MEAR-327: - Assignee: Sylwester Lachiewicz > Upgrade Parent to 43, require Maven 3.6.3 > - > > Key: MEAR-327 > URL: https://issues.apache.org/jira/browse/MEAR-327 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MEAR-327) Upgrade Parent to 43, require Maven 3.6.3
[ https://issues.apache.org/jira/browse/MEAR-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MEAR-327. - Resolution: Fixed > Upgrade Parent to 43, require Maven 3.6.3 > - > > Key: MEAR-327 > URL: https://issues.apache.org/jira/browse/MEAR-327 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.maven.shared:maven-filtering from 3.3.1 to 3.4.0 [maven-ear-plugin]
slachiewicz commented on PR #115: URL: https://github.com/apache/maven-ear-plugin/pull/115#issuecomment-2408551319 @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
Re: [PR] Bump commons-io:commons-io from 2.15.1 to 2.17.0 [maven-ear-plugin]
slachiewicz commented on PR #116: URL: https://github.com/apache/maven-ear-plugin/pull/116#issuecomment-2408552042 @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
Re: [PR] Bump org.apache.maven:maven-core from 3.0 to 3.8.1 in /src/it/transitive-excludes [maven-ear-plugin]
slachiewicz commented on PR #95: URL: https://github.com/apache/maven-ear-plugin/pull/95#issuecomment-2408552210 @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
Re: [PR] Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.10.0 [maven-ear-plugin]
slachiewicz commented on PR #114: URL: https://github.com/apache/maven-ear-plugin/pull/114#issuecomment-2408552103 @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
Re: [PR] Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2 [maven-ear-plugin]
slachiewicz commented on PR #111: URL: https://github.com/apache/maven-ear-plugin/pull/111#issuecomment-2408552162 @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
Re: [PR] Bump org.apache.commons:commons-lang3 from 3.15.0 to 3.17.0 [maven-resolver]
cstamas merged PR #575: URL: https://github.com/apache/maven-resolver/pull/575 -- 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-606) Bump org.apache.commons:commons-lang3 from 3.15.0 to 3.17.0
Tamas Cservenak created MRESOLVER-606: - Summary: Bump org.apache.commons:commons-lang3 from 3.15.0 to 3.17.0 Key: MRESOLVER-606 URL: https://issues.apache.org/jira/browse/MRESOLVER-606 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-956) silent parameter is not taken into account
[
https://issues.apache.org/jira/browse/MDEP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888943#comment-17888943
]
ASF GitHub Bot commented on MDEP-956:
-
elharo commented on code in PR #436:
URL:
https://github.com/apache/maven-dependency-plugin/pull/436#discussion_r1797776699
##
src/main/java/org/apache/maven/plugins/dependency/utils/CopyUtil.java:
##
@@ -51,18 +47,16 @@ public CopyUtil(BuildContext buildContext) {
}
/**
- * Does the actual copy of the artifact (file) and logging.
+ * Copies the artifact (file).
*
- * @param sourceArtifact represents the artifact (file) to copy.
- * @param destination file name of destination file.
+ * @param sourceArtifact represents the artifact (file) to copy
+ * @param destination file name of destination file
* @throws IOException if copy has failed
* @throws MojoExecutionException if artifact file is a directory (which
has not been packaged yet)
*
* @since 3.7.0
*/
public void copyArtifactFile(Artifact sourceArtifact, File destination)
throws IOException, MojoExecutionException {
-logger.info("Copying artifact '{}' ({}) to {}", sourceArtifact,
sourceArtifact.getFile(), destination);
Review Comment:
OK, done
> silent parameter is not taken into account
> --
>
> Key: MDEP-956
> URL: https://issues.apache.org/jira/browse/MDEP-956
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 3.7.0, 3.7.1, 3.8.0
>Reporter: Philippe De Neve
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> When setting the {{silent}} parameter to {{{}true{}}}, the
> {{copy-dependencies}} goal remains non-silent.
> To reproduce:
> {code:bash}
> git clone https://gitlab.com/philippedn/jli.git
> cd jli/demos/jfxm
> mvn prepare-package # silent parameter set to true in pom.xml
> {code}
> Output:
> {code:bash}
> ...
> [INFO] Copying artifact 'org.openjfx:javafx-controls:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-controls:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-graphics:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-graphics:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MDEP-956] Silence artifact copying [maven-dependency-plugin]
elharo commented on code in PR #436:
URL:
https://github.com/apache/maven-dependency-plugin/pull/436#discussion_r1797776699
##
src/main/java/org/apache/maven/plugins/dependency/utils/CopyUtil.java:
##
@@ -51,18 +47,16 @@ public CopyUtil(BuildContext buildContext) {
}
/**
- * Does the actual copy of the artifact (file) and logging.
+ * Copies the artifact (file).
*
- * @param sourceArtifact represents the artifact (file) to copy.
- * @param destination file name of destination file.
+ * @param sourceArtifact represents the artifact (file) to copy
+ * @param destination file name of destination file
* @throws IOException if copy has failed
* @throws MojoExecutionException if artifact file is a directory (which
has not been packaged yet)
*
* @since 3.7.0
*/
public void copyArtifactFile(Artifact sourceArtifact, File destination)
throws IOException, MojoExecutionException {
-logger.info("Copying artifact '{}' ({}) to {}", sourceArtifact,
sourceArtifact.getFile(), destination);
Review Comment:
OK, done
--
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] [MRESOLVER-541] S3 Transport using MinIO [maven-resolver]
cstamas merged PR #553: URL: https://github.com/apache/maven-resolver/pull/553 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-541) S3 Transport
[ https://issues.apache.org/jira/browse/MRESOLVER-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888914#comment-17888914 ] ASF GitHub Bot commented on MRESOLVER-541: -- cstamas merged PR #553: URL: https://github.com/apache/maven-resolver/pull/553 > S3 Transport > > > Key: MRESOLVER-541 > URL: https://issues.apache.org/jira/browse/MRESOLVER-541 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Labels: up-for-grabs > Fix For: 2.0.2 > > > We might want to revisit creating transport for S3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-541) S3 Transport
[ https://issues.apache.org/jira/browse/MRESOLVER-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-541. - Resolution: Fixed > S3 Transport > > > Key: MRESOLVER-541 > URL: https://issues.apache.org/jira/browse/MRESOLVER-541 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Labels: up-for-grabs > Fix For: 2.0.2 > > > We might want to revisit creating transport for S3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0 [maven-resolver]
cstamas merged PR #562: URL: https://github.com/apache/maven-resolver/pull/562 -- 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-607) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0
Tamas Cservenak created MRESOLVER-607: - Summary: Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0 Key: MRESOLVER-607 URL: https://issues.apache.org/jira/browse/MRESOLVER-607 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump maven3Version from 3.9.8 to 3.9.9 [maven-resolver]
cstamas merged PR #559: URL: https://github.com/apache/maven-resolver/pull/559 -- 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.commons:commons-compress from 1.26.2 to 1.27.1 [maven-resolver]
cstamas merged PR #561: URL: https://github.com/apache/maven-resolver/pull/561 -- 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-608) Bump org.apache.commons:commons-compress from 1.26.2 to 1.27.1
Tamas Cservenak created MRESOLVER-608: - Summary: Bump org.apache.commons:commons-compress from 1.26.2 to 1.27.1 Key: MRESOLVER-608 URL: https://issues.apache.org/jira/browse/MRESOLVER-608 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump slf4jVersion from 2.0.13 to 2.0.16 [maven-resolver]
cstamas merged PR #556: URL: https://github.com/apache/maven-resolver/pull/556 -- 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-611) Bump slf4jVersion from 2.0.13 to 2.0.16
Tamas Cservenak created MRESOLVER-611: - Summary: Bump slf4jVersion from 2.0.13 to 2.0.16 Key: MRESOLVER-611 URL: https://issues.apache.org/jira/browse/MRESOLVER-611 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-610) (build) Bump org.codehaus.mojo:exec-maven-plugin from 3.3.0 to 3.4.1
Tamas Cservenak created MRESOLVER-610: - Summary: (build) Bump org.codehaus.mojo:exec-maven-plugin from 3.3.0 to 3.4.1 Key: MRESOLVER-610 URL: https://issues.apache.org/jira/browse/MRESOLVER-610 Project: Maven Resolver Issue Type: Dependency upgrade Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.codehaus.mojo:exec-maven-plugin from 3.3.0 to 3.4.1 [maven-resolver]
cstamas merged PR #557: URL: https://github.com/apache/maven-resolver/pull/557 -- 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] (MRESOLVER-607) Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0
[ https://issues.apache.org/jira/browse/MRESOLVER-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-607: - Assignee: Tamas Cservenak > Bump com.github.siom79.japicmp:japicmp-maven-plugin from 0.22.0 to 0.23.0 > - > > Key: MRESOLVER-607 > URL: https://issues.apache.org/jira/browse/MRESOLVER-607 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-608) Bump org.apache.commons:commons-compress from 1.26.2 to 1.27.1
[ https://issues.apache.org/jira/browse/MRESOLVER-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-608. - Resolution: Fixed > Bump org.apache.commons:commons-compress from 1.26.2 to 1.27.1 > -- > > Key: MRESOLVER-608 > URL: https://issues.apache.org/jira/browse/MRESOLVER-608 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-609) Bump maven3Version from 3.9.8 to 3.9.9
[ https://issues.apache.org/jira/browse/MRESOLVER-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-609: - Assignee: Tamas Cservenak > Bump maven3Version from 3.9.8 to 3.9.9 > -- > > Key: MRESOLVER-609 > URL: https://issues.apache.org/jira/browse/MRESOLVER-609 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-611) Bump slf4jVersion from 2.0.13 to 2.0.16
[ https://issues.apache.org/jira/browse/MRESOLVER-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-611. - Resolution: Fixed > Bump slf4jVersion from 2.0.13 to 2.0.16 > --- > > Key: MRESOLVER-611 > URL: https://issues.apache.org/jira/browse/MRESOLVER-611 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-609) Bump maven3Version from 3.9.8 to 3.9.9
[ https://issues.apache.org/jira/browse/MRESOLVER-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-609. - Resolution: Fixed > Bump maven3Version from 3.9.8 to 3.9.9 > -- > > Key: MRESOLVER-609 > URL: https://issues.apache.org/jira/browse/MRESOLVER-609 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-608) Bump org.apache.commons:commons-compress from 1.26.2 to 1.27.1
[ https://issues.apache.org/jira/browse/MRESOLVER-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-608: - Assignee: Tamas Cservenak > Bump org.apache.commons:commons-compress from 1.26.2 to 1.27.1 > -- > > Key: MRESOLVER-608 > URL: https://issues.apache.org/jira/browse/MRESOLVER-608 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-600) Implement RFC 9457
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1793#comment-1793 ] ASF GitHub Bot commented on MRESOLVER-600: -- cstamas merged PR #576: URL: https://github.com/apache/maven-resolver/pull/576 > Implement RFC 9457 > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC > 9112|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 > defines the response status code to optionally include a text description > (human readable) of the reason for the status code. > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-611) Bump slf4jVersion from 2.0.13 to 2.0.16
[ https://issues.apache.org/jira/browse/MRESOLVER-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-611: - Assignee: Tamas Cservenak > Bump slf4jVersion from 2.0.13 to 2.0.16 > --- > > Key: MRESOLVER-611 > URL: https://issues.apache.org/jira/browse/MRESOLVER-611 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8301) [REGRESSION] Can't build a project without modelVersion=4.1.0 but with 4.1.0 (beta-4) XSD
[
https://issues.apache.org/jira/browse/MNG-8301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Mulders updated MNG-8301:
-
Summary: [REGRESSION] Can't build a project without modelVersion=4.1.0 but
with 4.1.0 (beta-4) XSD (was: [REGRESSION] Not possible to build a project
without modelVersion=4.1.0 but with 4.1.0 (beta-4) XSD)
> [REGRESSION] Can't build a project without modelVersion=4.1.0 but with 4.1.0
> (beta-4) XSD
> -
>
> Key: MNG-8301
> URL: https://issues.apache.org/jira/browse/MNG-8301
> Project: Maven
> Issue Type: Bug
> Components: POM
>Affects Versions: 4.0.0-beta-5
> Environment: Apache Maven 4.0.0-beta-5-SNAPSHOT
> (fee69f2f89c6f32dbef0ec55a7f6e8c071d4b6a9)
> Java version: 23, vendor: Eclipse Adoptium, runtime:
> /Library/Java/JavaVirtualMachines/temurin-23.jdk/Contents/Home
> OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac"
>Reporter: Didier Loiseau
>Priority: Major
>
> A project whose pom.xml refers to the [4.0.0-beta-4
> XSD|https://maven.apache.org/xsd/maven-4.1.0-beta-4.xsd] and that lacks a
> {{modelVersion}} element used to be buildable with Maven 4.0.0-beta-4. Maven
> would infer from the XSD that it should use _modelVersion_ 4.1.0.
> With the current snapshots of 4.0.0-beta-5, it can no longer be built:
> {quote}{{[ERROR] The project
> org.apache.maven.its.mng8301:module-b:1-SNAPSHOT
> (/Users/maarten/Code/open-source/maven/m4-no-modelversion-repro/module-b/pom.xml)
> has 1 error}}
> {{[ERROR] 'dependencies.dependency.version' for
> org.apache.maven.repro:module-a:jar is missing. @
> org.apache.maven.its.mng8301:module-b:[unknown-version],
> file:///Users/maarten/Code/open-source/maven/m4-no-modelversion-repro/module-b/pom.xml,
> line 17, column 9}}
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MRESOLVER-599] Sigstore Artifact Generator [maven-resolver]
cstamas merged PR #573: URL: https://github.com/apache/maven-resolver/pull/573 -- 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] (MRESOLVER-599) Sigstore generator
[ https://issues.apache.org/jira/browse/MRESOLVER-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-599. - Resolution: Fixed > Sigstore generator > -- > > Key: MRESOLVER-599 > URL: https://issues.apache.org/jira/browse/MRESOLVER-599 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > > Just like > [GPG|https://github.com/apache/maven-resolver/tree/master/maven-resolver-generator-gnupg] > generator, we need sigstore generator. That would remove the limitations > (but would need either to Maven include this generator by default, or users > use this new generator as extension). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-778) The unpack integration test fails with new archiver
[ https://issues.apache.org/jira/browse/MDEP-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MDEP-778. - Resolution: Not A Problem > The unpack integration test fails with new archiver > --- > > Key: MDEP-778 > URL: https://issues.apache.org/jira/browse/MDEP-778 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: unpack >Affects Versions: 3.1.1 > Environment: Mac OS >Reporter: Sylwester Lachiewicz >Priority: Minor > > When doing a clean integration test, the test case fails intermittent on Mac > OS. The command executed are: > mvn clean verify -Prun-its -Dinvoker.test=unpack,setup* > or > mvn clean install -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-956) silent parameter is not taken into account
[
https://issues.apache.org/jira/browse/MDEP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888946#comment-17888946
]
ASF GitHub Bot commented on MDEP-956:
-
elharo merged PR #436:
URL: https://github.com/apache/maven-dependency-plugin/pull/436
> silent parameter is not taken into account
> --
>
> Key: MDEP-956
> URL: https://issues.apache.org/jira/browse/MDEP-956
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 3.7.0, 3.7.1, 3.8.0
>Reporter: Philippe De Neve
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> When setting the {{silent}} parameter to {{{}true{}}}, the
> {{copy-dependencies}} goal remains non-silent.
> To reproduce:
> {code:bash}
> git clone https://gitlab.com/philippedn/jli.git
> cd jli/demos/jfxm
> mvn prepare-package # silent parameter set to true in pom.xml
> {code}
> Output:
> {code:bash}
> ...
> [INFO] Copying artifact 'org.openjfx:javafx-controls:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-controls:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-graphics:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-graphics:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MDEP-956][MDEP-932] Silence artifact copying [maven-dependency-plugin]
elharo merged PR #436: URL: https://github.com/apache/maven-dependency-plugin/pull/436 -- 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] (MDEP-932) Don't log successful file copies
[
https://issues.apache.org/jira/browse/MDEP-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold reassigned MDEP-932:
--
Assignee: Elliotte Rusty Harold
> Don't log successful file copies
>
>
> Key: MDEP-932
> URL: https://issues.apache.org/jira/browse/MDEP-932
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> In AbstractDependencyMojo
> Either a file is copied successfully and no one wants to read this message or
> it fails and an exception is thrown. Either way, the log message simply isn't
> needed and gets in the way of debugging real failures.
> /**
> * Does the actual copy of the file and logging.
> *
> * @param artifact represents the file to copy.
> * @param destFile file name of destination file.
> * @throws MojoExecutionException with a message if an error occurs.
> */
> protected void copyFile(File artifact, File destFile) throws
> MojoExecutionException {
> try {
> getLog().info("Copying "
> + (this.outputAbsoluteArtifactFilename ?
> artifact.getAbsolutePath() : artifact.getName()) + " to "
> + destFile);
> if (artifact.isDirectory()) {
> // usual case is a future jar packaging, but there are
> special cases: classifier and other packaging
> throw new MojoExecutionException("Artifact has not been
> packaged yet. When used on reactor artifact, "
> + "copy should be executed after packaging: see
> MDEP-187.");
> }
> FileUtils.copyFile(artifact, destFile);
> buildContext.refresh(destFile);
> } catch (IOException e) {
> throw new MojoExecutionException("Error copying artifact from " +
> artifact + " to " + destFile, e);
> }
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-778) The unpack integration test fails with new archiver
[ https://issues.apache.org/jira/browse/MDEP-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888945#comment-17888945 ] Elliotte Rusty Harold commented on MDEP-778: I can't reproduce this one > The unpack integration test fails with new archiver > --- > > Key: MDEP-778 > URL: https://issues.apache.org/jira/browse/MDEP-778 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: unpack >Affects Versions: 3.1.1 > Environment: Mac OS >Reporter: Sylwester Lachiewicz >Priority: Minor > > When doing a clean integration test, the test case fails intermittent on Mac > OS. The command executed are: > mvn clean verify -Prun-its -Dinvoker.test=unpack,setup* > or > mvn clean install -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MDEP-955) unpack ignores global fileMappers
[
https://issues.apache.org/jira/browse/MDEP-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MDEP-955.
Resolution: Fixed
> unpack ignores global fileMappers
> -
>
> Key: MDEP-955
> URL: https://issues.apache.org/jira/browse/MDEP-955
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
>Affects Versions: 3.8.0
> Environment: Windows 11, Java 21, Maven 3.8.6, Maven Dependency
> Plugin 3.8.0
>Reporter: Jonah Bauer
>Priority: Major
>
> I was trying to use the {{unpack}} goal to unpack multiple artifacts with a
> similar structure (namely webjars) and rewrite their filenames using a common
> file mapper. The {{unpack}} goal conveniently defines the property
> {{fileMappers}} which seems suited for this use case. The configuration is as
> follows
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 3.8.0
>
>
> unpack-libraries
> generate-resources
>
> unpack
>
>
>
>
> org.webjars.npm
> chart.js
> ${chartjs.version}
>
>
> org.webjars.npm
> chartjs-adapter-date-fns
> 3.0.0
>
>
> META-INF/resources/webjars/*/*/dist/**
>
> ${project.build.directory}/generated-resources/libraries
>
>
>
>
> ^META-INF/resources/webjars/([^/]+)/[^/]+/dist/
> ./$1/
>
>
>
>
>
>
>
> {code}
> This, however, does not work. While the artifacts are unpacked to the target
> directory, the globally configured {{fileMappers}} did not seem to take any
> effect.
> After looking into the code of {{UnpackMojo}} it seems the
> {{UnpackMojo::getFileMappers}} method is unused. In
> {{UnpackMojo::getProcessedArtifactItems}} the {{includes}} and {{excludes}}
> of each artifact item are set to the globally configured values if empty, but
> the file mappers are left unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (MDEP-932) Don't log successful file copies
[
https://issues.apache.org/jira/browse/MDEP-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MDEP-932.
Resolution: Fixed
> Don't log successful file copies
>
>
> Key: MDEP-932
> URL: https://issues.apache.org/jira/browse/MDEP-932
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Reporter: Elliotte Rusty Harold
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> In AbstractDependencyMojo
> Either a file is copied successfully and no one wants to read this message or
> it fails and an exception is thrown. Either way, the log message simply isn't
> needed and gets in the way of debugging real failures.
> /**
> * Does the actual copy of the file and logging.
> *
> * @param artifact represents the file to copy.
> * @param destFile file name of destination file.
> * @throws MojoExecutionException with a message if an error occurs.
> */
> protected void copyFile(File artifact, File destFile) throws
> MojoExecutionException {
> try {
> getLog().info("Copying "
> + (this.outputAbsoluteArtifactFilename ?
> artifact.getAbsolutePath() : artifact.getName()) + " to "
> + destFile);
> if (artifact.isDirectory()) {
> // usual case is a future jar packaging, but there are
> special cases: classifier and other packaging
> throw new MojoExecutionException("Artifact has not been
> packaged yet. When used on reactor artifact, "
> + "copy should be executed after packaging: see
> MDEP-187.");
> }
> FileUtils.copyFile(artifact, destFile);
> buildContext.refresh(destFile);
> } catch (IOException e) {
> throw new MojoExecutionException("Error copying artifact from " +
> artifact + " to " + destFile, e);
> }
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Minor copy editing [maven-dependency-plugin]
elharo merged PR #437: URL: https://github.com/apache/maven-dependency-plugin/pull/437 -- 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] (MRESOLVER-600) Implement RFC 9457 - Problem Details for HTTP APIs
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MRESOLVER-600: Description: HTTP1.1 [RFC 9112 - HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 defines the response status code to optionally include a text description (human readable) of the reason for the status code. There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to inform of a reason for the error response allowing for easier investigation. h2. Why is this important [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard and the response status only considers the [status code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] and not the reason phrase, as such important information can be lost in helping the client determine a route cause of a failure. was: HTTP1.1 [RFC 9112|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 defines the response status code to optionally include a text description (human readable) of the reason for the status code. There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to inform of a reason for the error response allowing for easier investigation. h2. Why is this important [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard and the response status only considers the [status code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] and not the reason phrase, as such important information can be lost in helping the client determine a route cause of a failure. > Implement RFC 9457 - Problem Details for HTTP APIs > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC 9112 - > HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] > section 4 defines the response status code to optionally include a text > description (human readable) of the reason for the status code. > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-600) Implement RFC 9457 - Problem Details for HTTP APIs
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MRESOLVER-600: Description: HTTP1.1 [RFC 9112 - HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 defines the response status code to optionally include a text description (human readable) of the reason for the status code. There is an additional [RFC9457 - Problem Details for HTTP APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to inform of a reason for the error response allowing for easier investigation. h2. Why is this important [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard and the response status only considers the [status code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] and not the reason phrase, as such important information can be lost in helping the client determine a route cause of a failure. was: HTTP1.1 [RFC 9112 - HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 defines the response status code to optionally include a text description (human readable) of the reason for the status code. There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to inform of a reason for the error response allowing for easier investigation. h2. Why is this important [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard and the response status only considers the [status code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] and not the reason phrase, as such important information can be lost in helping the client determine a route cause of a failure. > Implement RFC 9457 - Problem Details for HTTP APIs > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC 9112 - > HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] > section 4 defines the response status code to optionally include a text > description (human readable) of the reason for the status code. > There is an additional [RFC9457 - Problem Details for HTTP > APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to > inform of a reason for the error response allowing for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-600) Implement RFC 9457 - Problem Details for HTTP APIs
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MRESOLVER-600: Description: HTTP1.1 [RFC 9112 - HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 defines the response status code to optionally include a text description (human readable) of the reason for the status code. There is an additional [RFC9457 - Problem Details for HTTP APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to inform of a reason for the error response allowing for easier investigation. h2. Why is this important [RFC9113 - HTTP/2|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard and the response status only considers the [status code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] and not the reason phrase, as such important information can be lost in helping the client determine a route cause of a failure. was: HTTP1.1 [RFC 9112 - HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 defines the response status code to optionally include a text description (human readable) of the reason for the status code. There is an additional [RFC9457 - Problem Details for HTTP APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to inform of a reason for the error response allowing for easier investigation. h2. Why is this important [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard and the response status only considers the [status code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] and not the reason phrase, as such important information can be lost in helping the client determine a route cause of a failure. > Implement RFC 9457 - Problem Details for HTTP APIs > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC 9112 - > HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] > section 4 defines the response status code to optionally include a text > description (human readable) of the reason for the status code. > There is an additional [RFC9457 - Problem Details for HTTP > APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to > inform of a reason for the error response allowing for easier investigation. > h2. Why is this important > [RFC9113 - HTTP/2|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 > protocol standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-600) Implement RFC 9457 - Problem Details for HTTP APIs
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MRESOLVER-600: Summary: Implement RFC 9457 - Problem Details for HTTP APIs (was: Implement RFC 9457) > Implement RFC 9457 - Problem Details for HTTP APIs > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC > 9112|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 > defines the response status code to optionally include a text description > (human readable) of the reason for the status code. > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MDEP-956] Silence artifact copying [maven-dependency-plugin]
michael-o commented on code in PR #436:
URL:
https://github.com/apache/maven-dependency-plugin/pull/436#discussion_r1797755849
##
src/main/java/org/apache/maven/plugins/dependency/utils/CopyUtil.java:
##
@@ -51,18 +47,16 @@ public CopyUtil(BuildContext buildContext) {
}
/**
- * Does the actual copy of the artifact (file) and logging.
+ * Copies the artifact (file).
*
- * @param sourceArtifact represents the artifact (file) to copy.
- * @param destination file name of destination file.
+ * @param sourceArtifact represents the artifact (file) to copy
+ * @param destination file name of destination file
* @throws IOException if copy has failed
* @throws MojoExecutionException if artifact file is a directory (which
has not been packaged yet)
*
* @since 3.7.0
*/
public void copyArtifactFile(Artifact sourceArtifact, File destination)
throws IOException, MojoExecutionException {
-logger.info("Copying artifact '{}' ({}) to {}", sourceArtifact,
sourceArtifact.getFile(), destination);
Review Comment:
Why not move to debug level?
--
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] (MDEP-956) silent parameter is not taken into account
[
https://issues.apache.org/jira/browse/MDEP-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888931#comment-17888931
]
ASF GitHub Bot commented on MDEP-956:
-
michael-o commented on code in PR #436:
URL:
https://github.com/apache/maven-dependency-plugin/pull/436#discussion_r1797755849
##
src/main/java/org/apache/maven/plugins/dependency/utils/CopyUtil.java:
##
@@ -51,18 +47,16 @@ public CopyUtil(BuildContext buildContext) {
}
/**
- * Does the actual copy of the artifact (file) and logging.
+ * Copies the artifact (file).
*
- * @param sourceArtifact represents the artifact (file) to copy.
- * @param destination file name of destination file.
+ * @param sourceArtifact represents the artifact (file) to copy
+ * @param destination file name of destination file
* @throws IOException if copy has failed
* @throws MojoExecutionException if artifact file is a directory (which
has not been packaged yet)
*
* @since 3.7.0
*/
public void copyArtifactFile(Artifact sourceArtifact, File destination)
throws IOException, MojoExecutionException {
-logger.info("Copying artifact '{}' ({}) to {}", sourceArtifact,
sourceArtifact.getFile(), destination);
Review Comment:
Why not move to debug level?
> silent parameter is not taken into account
> --
>
> Key: MDEP-956
> URL: https://issues.apache.org/jira/browse/MDEP-956
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 3.7.0, 3.7.1, 3.8.0
>Reporter: Philippe De Neve
>Assignee: Elliotte Rusty Harold
>Priority: Minor
>
> When setting the {{silent}} parameter to {{{}true{}}}, the
> {{copy-dependencies}} goal remains non-silent.
> To reproduce:
> {code:bash}
> git clone https://gitlab.com/philippedn/jli.git
> cd jli/demos/jfxm
> mvn prepare-package # silent parameter set to true in pom.xml
> {code}
> Output:
> {code:bash}
> ...
> [INFO] Copying artifact 'org.openjfx:javafx-controls:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-controls:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-controls/22.0.2/javafx-controls-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-controls-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-graphics:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact
> 'org.openjfx:javafx-graphics:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-graphics/22.0.2/javafx-graphics-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-graphics-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> [INFO] Copying artifact 'org.openjfx:javafx-base:jar:linux:22.0.2:compile'
> (/mnt/storage/maven-repository/org/openjfx/javafx-base/22.0.2/javafx-base-22.0.2-linux.jar)
> to
> /mnt/storage/code/scripts/jli/demos/jfxm/target/jars/javafx-base-22.0.2.jar
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSHARED-1438) Provide protected method for XRef location construction
[ https://issues.apache.org/jira/browse/MSHARED-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1438: Summary: Provide protected method for XRef location construction (was: Resolve Code Duplication for XRef Link generation) > Provide protected method for XRef location construction > --- > > Key: MSHARED-1438 > URL: https://issues.apache.org/jira/browse/MSHARED-1438 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-reporting-impl >Affects Versions: maven-reporting-impl-4.0.0-M15 >Reporter: Andreas Dangel >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0 > > > PMD, Checkstyle and Surefire all have the same code to determine the xref > code location for reporting and linking to the source code. > See MPMD-128 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1438) Provide protected methods for XRef location construction
[ https://issues.apache.org/jira/browse/MSHARED-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1438: Summary: Provide protected methods for XRef location construction (was: Provide protected method for XRef location construction) > Provide protected methods for XRef location construction > > > Key: MSHARED-1438 > URL: https://issues.apache.org/jira/browse/MSHARED-1438 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-reporting-impl >Affects Versions: maven-reporting-impl-4.0.0-M15 >Reporter: Andreas Dangel >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-impl-4.0.0 > > > PMD, Checkstyle and Surefire all have the same code to determine the xref > code location for reporting and linking to the source code. > See MPMD-128 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-602) Documentation for aether.priority. has disappeared
[
https://issues.apache.org/jira/browse/MRESOLVER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak reassigned MRESOLVER-602:
-
Assignee: Tamas Cservenak
> Documentation for aether.priority. has disappeared
> -
>
> Key: MRESOLVER-602
> URL: https://issues.apache.org/jira/browse/MRESOLVER-602
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.1
>Reporter: Didier Loiseau
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.2
>
>
> Property {{aether.priority.}} is not documented any more [in v2.0.1 of
> the
> documentation|https://maven.apache.org/resolver-archives/resolver-2.0.1/configuration.html],
> but it was [in version
> 1.9|https://maven.apache.org/resolver-archives/resolver-1.9.22/configuration.html].
> This change appears to be coming from commit
> [7318c95|https://github.com/apache/maven-resolver/commit/7318c95ae28df9a49d962a1a2c748d628f512ae2]
> which has regenerated the documentation (according to commit message).
> Note that the previous documentation was not very good already, since it did
> not give any pointers to what are the possible {{}} values, nor what
> kind of values it expects:
> {quote}The priority to use for a certain extension class. {{class}} can
> either be the fully qualified name or the simple name stands for fully
> qualified class name. If the class name ends with {{Factory}} that suffix
> could optionally be left out.
> {quote}
> For resolver 1.9, I found some possible values
> [here|https://github.com/apache/maven/blob/a98d530e338b54dadefc45b37c40094a84d12ae7/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L111-L117],
> more specifically {{WagonTransporterFactory}} has a default priority of -1
> and {{HttpTransporterFactory}} has 5 (more transporters are available in
> maven-resolver 2.x). I also found that {{DefaultTransporterProvider}} will
> log the used transporter class name when running maven with {{{}-X{}}}, using
> a message like
> {quote}Using transporter WagonTransporter with priority 1000.0
> {quote}
> Expected values appear to be float numbers.
> I didn’t check if other properties are missing (I wouldn’t know if they are
> still be relevant in 2.x anyway).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MSHARED-1439) Upgrade to Parent 43
[ https://issues.apache.org/jira/browse/MSHARED-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1439. --- Resolution: Fixed Fixed with [d72bcbc64720412c9a9b9da844c5d6420490afce|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=d72bcbc64720412c9a9b9da844c5d6420490afce]. > Upgrade to Parent 43 > > > Key: MSHARED-1439 > URL: https://issues.apache.org/jira/browse/MSHARED-1439 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1441) Upgrade to Maven Reporting API 4.0.0
[ https://issues.apache.org/jira/browse/MSHARED-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1441. --- Resolution: Fixed Fixed with [2460cc7e6c4dd200d012314c5fd0a20a3051543f|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=2460cc7e6c4dd200d012314c5fd0a20a3051543f]. > Upgrade to Maven Reporting API 4.0.0 > > > Key: MSHARED-1441 > URL: https://issues.apache.org/jira/browse/MSHARED-1441 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1440) Upgrade to Doxia 2.0.0
[ https://issues.apache.org/jira/browse/MSHARED-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1440. --- Resolution: Fixed Fixed with [0a00a86e7c0d7aa8027a5de78fe90039d4171cbb|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=0a00a86e7c0d7aa8027a5de78fe90039d4171cbb]. > Upgrade to Doxia 2.0.0 > -- > > Key: MSHARED-1440 > URL: https://issues.apache.org/jira/browse/MSHARED-1440 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MSHARED-1442) Upgrade to Doxia Sitetools 2.0.0
[ https://issues.apache.org/jira/browse/MSHARED-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-1442. --- Resolution: Fixed Fixed with [5abbbfbf64cc290f1d04f4adbb7775e6853afaa6|https://gitbox.apache.org/repos/asf?p=maven-reporting-exec.git;a=commit;h=5abbbfbf64cc290f1d04f4adbb7775e6853afaa6]. > Upgrade to Doxia Sitetools 2.0.0 > > > Key: MSHARED-1442 > URL: https://issues.apache.org/jira/browse/MSHARED-1442 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1443) Upgrade plugins and components (in ITs)
[ https://issues.apache.org/jira/browse/MSHARED-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHARED-1443: Description: * Upgrade to Maven Site Plugin 3.20.0 * Upgrade to Maven Project Info Reports Plugin 3.7.0 * Upgrade to Maven Javadoc Plugin 3.10.1 * Upgrade to Maven Checkstyle Plugin 3.5.0 * Upgrade to Maven Plugin Tools 3.15.0 * Upgrade to Maven Reporting Impl 4.0.0 > Upgrade plugins and components (in ITs) > --- > > Key: MSHARED-1443 > URL: https://issues.apache.org/jira/browse/MSHARED-1443 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-reporting-exec >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: maven-reporting-exec-2.0.0 > > > * Upgrade to Maven Site Plugin 3.20.0 > * Upgrade to Maven Project Info Reports Plugin 3.7.0 > * Upgrade to Maven Javadoc Plugin 3.10.1 > * Upgrade to Maven Checkstyle Plugin 3.5.0 > * Upgrade to Maven Plugin Tools 3.15.0 > * Upgrade to Maven Reporting Impl 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-602][MRESOLVER-603] Expose redirect config for apache transport [maven-resolver]
cstamas merged PR #581: URL: https://github.com/apache/maven-resolver/pull/581 -- 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] Simplify a few usages of StringBuilder - use plain String or StringJoiner [maven-compiler-plugin]
turbanoff closed pull request #260: Simplify a few usages of StringBuilder - use plain String or StringJoiner URL: https://github.com/apache/maven-compiler-plugin/pull/260 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-602) Documentation for aether.priority. has disappeared
[
https://issues.apache.org/jira/browse/MRESOLVER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888940#comment-17888940
]
ASF GitHub Bot commented on MRESOLVER-602:
--
cstamas merged PR #581:
URL: https://github.com/apache/maven-resolver/pull/581
> Documentation for aether.priority. has disappeared
> -
>
> Key: MRESOLVER-602
> URL: https://issues.apache.org/jira/browse/MRESOLVER-602
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.1
>Reporter: Didier Loiseau
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.2
>
>
> Property {{aether.priority.}} is not documented any more [in v2.0.1 of
> the
> documentation|https://maven.apache.org/resolver-archives/resolver-2.0.1/configuration.html],
> but it was [in version
> 1.9|https://maven.apache.org/resolver-archives/resolver-1.9.22/configuration.html].
> This change appears to be coming from commit
> [7318c95|https://github.com/apache/maven-resolver/commit/7318c95ae28df9a49d962a1a2c748d628f512ae2]
> which has regenerated the documentation (according to commit message).
> Note that the previous documentation was not very good already, since it did
> not give any pointers to what are the possible {{}} values, nor what
> kind of values it expects:
> {quote}The priority to use for a certain extension class. {{class}} can
> either be the fully qualified name or the simple name stands for fully
> qualified class name. If the class name ends with {{Factory}} that suffix
> could optionally be left out.
> {quote}
> For resolver 1.9, I found some possible values
> [here|https://github.com/apache/maven/blob/a98d530e338b54dadefc45b37c40094a84d12ae7/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L111-L117],
> more specifically {{WagonTransporterFactory}} has a default priority of -1
> and {{HttpTransporterFactory}} has 5 (more transporters are available in
> maven-resolver 2.x). I also found that {{DefaultTransporterProvider}} will
> log the used transporter class name when running maven with {{{}-X{}}}, using
> a message like
> {quote}Using transporter WagonTransporter with priority 1000.0
> {quote}
> Expected values appear to be float numbers.
> I didn’t check if other properties are missing (I wouldn’t know if they are
> still be relevant in 2.x anyway).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-603) Apache HTTP transport should expose config for max redirects
[
https://issues.apache.org/jira/browse/MRESOLVER-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-603.
-
Resolution: Fixed
> Apache HTTP transport should expose config for max redirects
>
>
> Key: MRESOLVER-603
> URL: https://issues.apache.org/jira/browse/MRESOLVER-603
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Affects Versions: 1.9.x
>Reporter: Didier Loiseau
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.2, 1.9.23
>
>
> Apache HttpClient allows to {{{}RequestConfig.maxRedirects{}}}. It would be
> nice to expose it through configuration as for Jetty (MRESOLVER-595) and
> Wagon.
> Also note that setting it to 0 actually sets a value of 50, so it could be
> nice to be able to disable redirects entirely (as for Jetty).
> Ideally this should be implemented in 1.9.x since it {{HttpTransport}} is the
> default in Maven 3.9. (apparently the fix version was copied from
> MRESOLVER-595 when I cloned it)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MRESOLVER-602) Documentation for aether.priority. has disappeared
[
https://issues.apache.org/jira/browse/MRESOLVER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak closed MRESOLVER-602.
-
Resolution: Fixed
> Documentation for aether.priority. has disappeared
> -
>
> Key: MRESOLVER-602
> URL: https://issues.apache.org/jira/browse/MRESOLVER-602
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Affects Versions: 2.0.1
>Reporter: Didier Loiseau
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.2
>
>
> Property {{aether.priority.}} is not documented any more [in v2.0.1 of
> the
> documentation|https://maven.apache.org/resolver-archives/resolver-2.0.1/configuration.html],
> but it was [in version
> 1.9|https://maven.apache.org/resolver-archives/resolver-1.9.22/configuration.html].
> This change appears to be coming from commit
> [7318c95|https://github.com/apache/maven-resolver/commit/7318c95ae28df9a49d962a1a2c748d628f512ae2]
> which has regenerated the documentation (according to commit message).
> Note that the previous documentation was not very good already, since it did
> not give any pointers to what are the possible {{}} values, nor what
> kind of values it expects:
> {quote}The priority to use for a certain extension class. {{class}} can
> either be the fully qualified name or the simple name stands for fully
> qualified class name. If the class name ends with {{Factory}} that suffix
> could optionally be left out.
> {quote}
> For resolver 1.9, I found some possible values
> [here|https://github.com/apache/maven/blob/a98d530e338b54dadefc45b37c40094a84d12ae7/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L111-L117],
> more specifically {{WagonTransporterFactory}} has a default priority of -1
> and {{HttpTransporterFactory}} has 5 (more transporters are available in
> maven-resolver 2.x). I also found that {{DefaultTransporterProvider}} will
> log the used transporter class name when running maven with {{{}-X{}}}, using
> a message like
> {quote}Using transporter WagonTransporter with priority 1000.0
> {quote}
> Expected values appear to be float numbers.
> I didn’t check if other properties are missing (I wouldn’t know if they are
> still be relevant in 2.x anyway).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Bump commons-io:commons-io from 2.11.0 to 2.14.0 in /src/it/skinny-wars-javaee5/war-module3 [maven-ear-plugin]
slachiewicz merged PR #121: URL: https://github.com/apache/maven-ear-plugin/pull/121 -- 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:maven-archiver from 3.6.1 to 3.6.2 [maven-ear-plugin]
slachiewicz merged PR #111: URL: https://github.com/apache/maven-ear-plugin/pull/111 -- 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] (MRESOLVER-604) Make config properties metadata available
[ https://issues.apache.org/jira/browse/MRESOLVER-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-604. - Resolution: Fixed > Make config properties metadata available > - > > Key: MRESOLVER-604 > URL: https://issues.apache.org/jira/browse/MRESOLVER-604 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 2.0.2 > > > The config properties metadata is required to be able to document them in the > maven distribution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-606) Bump org.apache.commons:commons-lang3 from 3.15.0 to 3.17.0
[ https://issues.apache.org/jira/browse/MRESOLVER-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-606. - Resolution: Fixed > Bump org.apache.commons:commons-lang3 from 3.15.0 to 3.17.0 > --- > > Key: MRESOLVER-606 > URL: https://issues.apache.org/jira/browse/MRESOLVER-606 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MRESOLVER-600) Implement RFC 9457
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-600. - Resolution: Fixed > Implement RFC 9457 > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC > 9112|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 > defines the response status code to optionally include a text description > (human readable) of the reason for the status code. > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRESOLVER-604] Make config properties metadata available [maven-resolver]
cstamas merged PR #574: URL: https://github.com/apache/maven-resolver/pull/574 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-604) Make config properties metadata available
[ https://issues.apache.org/jira/browse/MRESOLVER-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1794#comment-1794 ] ASF GitHub Bot commented on MRESOLVER-604: -- cstamas merged PR #574: URL: https://github.com/apache/maven-resolver/pull/574 > Make config properties metadata available > - > > Key: MRESOLVER-604 > URL: https://issues.apache.org/jira/browse/MRESOLVER-604 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 2.0.2 > > > The config properties metadata is required to be able to document them in the > maven distribution. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MRESOLVER-600) Implement RFC 9457
[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-600: - Assignee: Tamas Cservenak > Implement RFC 9457 > -- > > Key: MRESOLVER-600 > URL: https://issues.apache.org/jira/browse/MRESOLVER-600 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver >Reporter: Mark Dodgson >Assignee: Tamas Cservenak >Priority: Minor > Fix For: 2.0.2 > > > HTTP1.1 [RFC > 9112|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section 4 > defines the response status code to optionally include a text description > (human readable) of the reason for the status code. > There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which > makes use of the body to inform of a reason for the error response allowing > for easier investigation. > h2. Why is this important > [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol > standard and the response status only considers the [status > code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel] > and not the reason phrase, as such important information can be lost in > helping the client determine a route cause of a failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-456) Fix javadoc warnings
[ https://issues.apache.org/jira/browse/MRESOLVER-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-456: -- Fix Version/s: 2.0.3 (was: 2.0.2) > Fix javadoc warnings > > > Key: MRESOLVER-456 > URL: https://issues.apache.org/jira/browse/MRESOLVER-456 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Labels: up-for-grabs > Fix For: 2.0.3 > > > We have some warnings, those need to be fixed. > Given build-time Java is 21, maybe we just want to migrate all to new Javadoc > style? (as many of warnings are missing returns, that basically redundantly > doubles the doco) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8301) [REGRESSION] Not possible to build a project without modelVersion=4.1.0 but with 4.1.0 (beta-4) XSD
Maarten Mulders created MNG-8301:
Summary: [REGRESSION] Not possible to build a project without
modelVersion=4.1.0 but with 4.1.0 (beta-4) XSD
Key: MNG-8301
URL: https://issues.apache.org/jira/browse/MNG-8301
Project: Maven
Issue Type: Bug
Components: POM
Affects Versions: 4.0.0-beta-5
Environment: Apache Maven 4.0.0-beta-5-SNAPSHOT
(fee69f2f89c6f32dbef0ec55a7f6e8c071d4b6a9)
Java version: 23, vendor: Eclipse Adoptium, runtime:
/Library/Java/JavaVirtualMachines/temurin-23.jdk/Contents/Home
OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac"
Reporter: Didier Loiseau
A project whose pom.xml refers to the [4.0.0-beta-4
XSD|https://maven.apache.org/xsd/maven-4.1.0-beta-4.xsd] and that lacks a
{{modelVersion}} element used to be buildable with Maven 4.0.0-beta-4. Maven
would infer from the XSD that it should use _modelVersion_ 4.1.0.
With the current snapshots of 4.0.0-beta-5, it can no longer be built.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MEAR-323) Bump plexus-io from 3.4.0 to 3.4.1
[ https://issues.apache.org/jira/browse/MEAR-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888921#comment-17888921 ] ASF GitHub Bot commented on MEAR-323: - slachiewicz merged PR #116: URL: https://github.com/apache/maven-ear-plugin/pull/116 > Bump plexus-io from 3.4.0 to 3.4.1 > -- > > Key: MEAR-323 > URL: https://issues.apache.org/jira/browse/MEAR-323 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MEAR-326] Bump org.codehaus.plexus:plexus-archiver from 4.9.0 to 4.10.0 [maven-ear-plugin]
slachiewicz merged PR #114: URL: https://github.com/apache/maven-ear-plugin/pull/114 -- 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] [MEAR-323] Bump commons-io:commons-io from 2.15.1 to 2.17.0 [maven-ear-plugin]
slachiewicz merged PR #116: URL: https://github.com/apache/maven-ear-plugin/pull/116 -- 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] (MEAR-326) Bump org.codehaus.plexus:plexus-archiver from 4.5.0 to 4.8.0
[ https://issues.apache.org/jira/browse/MEAR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888922#comment-17888922 ] ASF GitHub Bot commented on MEAR-326: - slachiewicz merged PR #114: URL: https://github.com/apache/maven-ear-plugin/pull/114 > Bump org.codehaus.plexus:plexus-archiver from 4.5.0 to 4.8.0 > > > Key: MEAR-326 > URL: https://issues.apache.org/jira/browse/MEAR-326 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEAR-326) Bump org.codehaus.plexus:plexus-archiver from 4.5.0 to 4.10.0
[ https://issues.apache.org/jira/browse/MEAR-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEAR-326: -- Summary: Bump org.codehaus.plexus:plexus-archiver from 4.5.0 to 4.10.0 (was: Bump org.codehaus.plexus:plexus-archiver from 4.5.0 to 4.8.0) > Bump org.codehaus.plexus:plexus-archiver from 4.5.0 to 4.10.0 > - > > Key: MEAR-326 > URL: https://issues.apache.org/jira/browse/MEAR-326 > Project: Maven EAR Plugin > Issue Type: Dependency upgrade >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2 [maven-ear-plugin]
slachiewicz commented on PR #111: URL: https://github.com/apache/maven-ear-plugin/pull/111#issuecomment-2408617704 @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
Re: [PR] Bump commons-io:commons-io from 2.11.0 to 2.14.0 in /src/it/packaging-includes [maven-ear-plugin]
slachiewicz merged PR #120: URL: https://github.com/apache/maven-ear-plugin/pull/120 -- 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] [MRESOLVER-603] Expose redirect config for apache transport [maven-resolver]
cstamas opened a new pull request, #581: URL: https://github.com/apache/maven-resolver/pull/581 maxRedirects and followRedirects exposed. --- https://issues.apache.org/jira/browse/MRESOLVER-603 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-603) Apache HTTP transport should expose config for max redirects
[
https://issues.apache.org/jira/browse/MRESOLVER-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888925#comment-17888925
]
ASF GitHub Bot commented on MRESOLVER-603:
--
cstamas opened a new pull request, #581:
URL: https://github.com/apache/maven-resolver/pull/581
maxRedirects and followRedirects exposed.
---
https://issues.apache.org/jira/browse/MRESOLVER-603
> Apache HTTP transport should expose config for max redirects
>
>
> Key: MRESOLVER-603
> URL: https://issues.apache.org/jira/browse/MRESOLVER-603
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
>Affects Versions: 1.9.x
>Reporter: Didier Loiseau
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.2, 1.9.23
>
>
> Apache HttpClient allows to {{{}RequestConfig.maxRedirects{}}}. It would be
> nice to expose it through configuration as for Jetty (MRESOLVER-595) and
> Wagon.
> Also note that setting it to 0 actually sets a value of 50, so it could be
> nice to be able to disable redirects entirely (as for Jetty).
> Ideally this should be implemented in 1.9.x since it {{HttpTransport}} is the
> default in Maven 3.9. (apparently the fix version was copied from
> MRESOLVER-595 when I cloned it)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-8301] Can't build a project without modelVersion=4.1.0 but with 4.1.0 (beta-4) XSD [maven-integration-testing]
mthmulders commented on PR #386: URL: https://github.com/apache/maven-integration-testing/pull/386#issuecomment-2408622765 Note that the above pipeline succeeds, because it runs with Maven 3.9.7. When run with 4.0.0-beta-5-SNAPSHOT, it fails. -- 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
