[jira] [Created] (MNG-8434) Recursive variable reference
Delany created MNG-8434:
---
Summary: Recursive variable reference
Key: MNG-8434
URL: https://issues.apache.org/jira/browse/MNG-8434
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-rc-2
Reporter: Delany
With project wrapper/maven-wrapper.properties
{code:java}
wrapperVersion=3.3.2
distributionType=only-script
distributionUrl=https://repository.apache.org/content/repositories/maven-2256/org/apache/maven/apache-maven/4.0.0-rc-2/apache-maven-4.0.0-rc-2-bin.zip{code}
a settings file profile
{code:java}
stage
stage
staging
Maven Staging
https://repository.apache.org/content/repositories/maven-${stage}/
staging-plugin
Maven Staging
https://repository.apache.org/content/repositories/maven-${stage}/
{code}
and command
{code:java}
./mvnw -N clean -Dstage=2256 -e{code}
I get this error
{code:java}
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs
at
org.apache.maven.project.DefaultProjectBuilder$BuildSession.build(DefaultProjectBuilder.java:464)
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:184)
at
org.apache.maven.project.collector.DefaultProjectsSelector.selectProjects(DefaultProjectsSelector.java:61)
at
org.apache.maven.project.collector.RequestPomCollectionStrategy.collectProjects(RequestPomCollectionStrategy.java:49)
at
org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:364)
at
org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:100)
at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:629)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:250)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:225)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:149)
at
org.apache.maven.cling.invoker.mvn.MavenInvoker.doExecute(MavenInvoker.java:470)
at
org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:95)
at
org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:85)
at
org.apache.maven.cling.invoker.LookupInvoker.doInvoke(LookupInvoker.java:145)
at
org.apache.maven.cling.invoker.LookupInvoker.invoke(LookupInvoker.java:116)
at org.apache.maven.cling.ClingSupport.run(ClingSupport.java:64)
at org.apache.maven.cling.MavenCling.main(MavenCling.java:51)
at
jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.lang.reflect.Method.invoke(Method.java:580)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
[ERROR]
[ERROR] The project com.rushmore:rushmore-parent:2.4.1-SNAPSHOT
(/git/rushmore/pom.xml) has 1 error
[ERROR] recursive variable reference: build.finalName
org.apache.maven.api.services.InterpolatorException: recursive variable
reference: build.finalName
at
org.apache.maven.internal.impl.model.DefaultInterpolator.resolveVariable(DefaultInterpolator.java:374)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.processSubstitution(DefaultInterpolator.java:312)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.doSubstVars(DefaultInterpolator.java:271)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.resolveVariable(DefaultInterpolator.java:385)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.processSubstitution(DefaultInterpolator.java:312)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.doSubstVars(DefaultInterpolator.java:271)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.substVars(DefaultInterpolator.java:206)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.interpolate(DefaultInterpolator.java:86)
at
org.apache.maven.internal.impl.model.DefaultInterpolator.interpolate(DefaultInterpolator.java:75)
at
org.apache.maven.internal.impl.model.DefaultModelInterpolator.lambda$createInterpolator$3(DefaultModelInterpolator.java:117)
at
org.apache.maven.model.v4.MavenTransformer.transform(MavenTransformer.java:93)
at
org.apache.maven.model.v4.MavenTransformer.transformBuildBase_FinalName(MavenTransformer.java:467)
at
org.apache.maven.model.v4.MavenTransformer.transformBuild(MavenTransformer.java:502)
at
org.apache.maven.model.v4.MavenTransformer.transformModel_Build(Ma
[jira] [Created] (MPH-220) Evaluating an expression for use in a script fails on Maven 4.0.0-rc-1
Nils Breunese created MPH-220:
-
Summary: Evaluating an expression for use in a script fails on
Maven 4.0.0-rc-1
Key: MPH-220
URL: https://issues.apache.org/jira/browse/MPH-220
Project: Maven Help Plugin
Issue Type: Bug
Components: evaluate
Affects Versions: 3.5.1
Reporter: Nils Breunese
https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html shows
that to use the value of an expression in a script, you can use this:
{code}
mvn help:evaluate -Dexpression=project.version -q -DforceStdout
{code}
I use a variant of this in a project and it works fine with Maven 3.9.9, but
when I try it with Maven 4.0.0-rc-1, I no longer get the expected output.
Here is a small reproducer POM:
{code}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
com.example
foo
${revision}
pom
1.0.0-SNAPSHOT
org.apache.maven.plugins
maven-help-plugin
3.5.1
{code}
This returns {{1.0.0-SNAPSHOT}} with Maven 3.9.9:
{code}
❯ mvn help:evaluate -Dexpression=project.version -q -DforceStdout
1.0.0-SNAPSHOT
{code}
But there is no output with Maven 4.0.0-rc-1:
{code}
❯ mvn help:evaluate -Dexpression=project.version -q -DforceStdout
{code}
Note that when I omit the {{-q}} flag, then I do see the expected version in
the output, but that output is of course not usable in an automated script.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-383) PMD should fail when there is a processing error
[
https://issues.apache.org/jira/browse/MPMD-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906116#comment-17906116
]
Thomas Nikolay commented on MPMD-383:
-
[~elharo]
If a tool like PMD is used in a project, then the tool becomes the norm in that
project.
If the tool then fails, it is a mistake because it violates the standard
expectations. The expectation is that the code has been checked.
Higher-level standards, such as ISO 27001, even specify that static code
analyses be performed. If the tool fails and no one notices, this can lead to
serious problems.
> PMD should fail when there is a processing error
>
>
> Key: MPMD-383
> URL: https://issues.apache.org/jira/browse/MPMD-383
> Project: Maven PMD Plugin
> Issue Type: Wish
> Components: PMD
>Affects Versions: 3.21.0
>Reporter: Thomas Nikolay
>Priority: Major
> Attachments: image-2023-07-28-13-34-28-717.png
>
>
> We had the case that PMD can't process some processing error but the build
> does not fail.
>
> {noformat}
> [2023-07-28T10:59:44.102Z] [INFO] --- maven-pmd-plugin:3.20.0:pmd (pmd) @
> mod-config-client-cst ---
> [2023-07-28T10:59:44.692Z] [INFO] PMD version: 6.53.0
> [2023-07-28T10:59:45.672Z] [WARNING] Removed misconfigured rule:
> GK-SAP-ApacheLoggerDeniedRule cause: missing value
> [2023-07-28T10:59:45.672Z] [WARNING] There are 3 PMD processing errors:
> [2023-07-28T10:59:45.672Z] [WARNING]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/cst/client/AppInfoProviderImpl_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/test/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST_Test.java
> [2023-07-28T10:59:45.948Z]
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java:
> PMDException: Error while processing
> /var/lib/hudson-slave/workspace/hmr.MAIN.00-FEATURE-BRANCHES/pos/config/mod-config-client-cst/src/main/java/com/gk_software/pos/api/model/config/component/client/print/additional_printout/Trigger_CFH_CST.java
> [2023-07-28T10:59:45.948Z] [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> [2023-07-28T10:59:46.210Z] [INFO]
> [2023-07-28T10:59:46.210Z] [INFO] <<< maven-pmd-plugin:3.20.0:check
> (pmd-check) < :pmd @ mod-config-client-cst <<<
> {noformat}
>
> My expectation would be that the build failed when there a processing errors.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-968) analyze-exclusions crashes on POM project
[
https://issues.apache.org/jira/browse/MDEP-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906104#comment-17906104
]
Hack Kampbjørn commented on MDEP-968:
-
In my case, this did not affect pom packaging used in parent modules, but only
jar packaging child modules without any dependency management.
My workaround is to add an empty dependency management tag like
{code:java}
{code}
> analyze-exclusions crashes on POM project
> -
>
> Key: MDEP-968
> URL: https://issues.apache.org/jira/browse/MDEP-968
> Project: Maven Dependency Plugin
> Issue Type: Bug
>Reporter: Jakub Bochenski
>Priority: Major
>
> ```
> Execution analyze-exclusions of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.8.1:analyze-exclusions
> failed: Cannot invoke
> "org.apache.maven.model.DependencyManagement.getDependencies()" because the
> return value of
> "org.apache.maven.project.MavenProject.getDependencyManagement()" is null
> ```
> Makes it impossible to use this rule in multimodule project unless you use
> some hacks to disable it in parent only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] GitHub Convention [maven-site]
slawekjaranowski commented on code in PR #588: URL: https://github.com/apache/maven-site/pull/588#discussion_r1887303500 ## content/markdown/developers/conventions/github.md: ## @@ -0,0 +1,106 @@ + +# Maven GitHub Conventions + +This document describes how Maven developers and contributors should use GitHub Issues and Pull Request. + +## GitHub Issue, Pull Request - Recommendations. + +**Minor changes** such as code reformatting, documentation fixes, etc. that aren't going to impact other users +can be committed without a GitHub Issue, but Pull Request is recommended. + +**Larger changes** such as bug fixes, API changes, significant refactoring, new classes, and pretty much any change +of more than 100 lines, and **New feature** should have GitHub Issue in order to first discus planed change. + +GitHub Issue should be referenced in commit message by `#issue-number`. + +GitHub Issue and Pull Request should have a label with type, like `bug`, `enhancement` and so on. +Pull Request without labels will be not categorized in Release Notes. + +Closed GitHub Issue and Pull Request should have milestone in which was resolved. + +Pull Request title is used to generate Release Notes - should be similar or the same as merged commit. + +Simply we should always provide changes by Pull Request. Direct commits will be not visible in Release Notes. + +## Release Notes + +Only Pull Request wits status **Merged** will be visible in Release Notes. + +We use GitHub Release Notes. + +We use the [Release Drafter Action](https://github.com/marketplace/actions/release-drafter) +for automatically preparing Release Notes. + +Default labels configurations are in [maven-gh-actions-shared](https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml) project. + +## How To Use Issue and Pull Request Details? + +### Assignee + +Committers can assign an GitHub Issue, Pull Request to a specific committer that person seems +to be well-placed to address it. + +Merged Pull Request should be assigned to committer who merge it. Review Comment: removed -- 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] Feature/convert to md [maven-doxia-site]
kwin merged PR #41: URL: https://github.com/apache/maven-doxia-site/pull/41 -- 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] [MRRESOURCES-146] Bump org.apache.maven.plugins:maven-plugins from 41 to 43 [maven-remote-resources-plugin]
slawekjaranowski merged PR #61: URL: https://github.com/apache/maven-remote-resources-plugin/pull/61 -- 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] (MRRESOURCES-146) Upgrade Parent to 43
[ https://issues.apache.org/jira/browse/MRRESOURCES-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MRRESOURCES-146. --- Resolution: Fixed > Upgrade Parent to 43 > > > Key: MRRESOURCES-146 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-146 > Project: Maven Remote Resources 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] (MRRESOURCES-146) Upgrade Parent to 43
[ https://issues.apache.org/jira/browse/MRRESOURCES-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906141#comment-17906141 ] ASF GitHub Bot commented on MRRESOURCES-146: slawekjaranowski merged PR #61: URL: https://github.com/apache/maven-remote-resources-plugin/pull/61 > Upgrade Parent to 43 > > > Key: MRRESOURCES-146 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-146 > Project: Maven Remote Resources 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 commons-io:commons-io from 2.16.1 to 2.17.0 [maven-shared-utils]
dependabot[bot] closed pull request #182: Bump commons-io:commons-io from 2.16.1 to 2.17.0 URL: https://github.com/apache/maven-shared-utils/pull/182 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.apache.commons:commons-text from 1.11.0 to 1.13.0 [maven-shared-utils]
dependabot[bot] opened a new pull request, #183: URL: https://github.com/apache/maven-shared-utils/pull/183 Bumps org.apache.commons:commons-text from 1.11.0 to 1.13.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) -- 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-text from 1.11.0 to 1.12.0 [maven-shared-utils]
dependabot[bot] closed pull request #177: Bump org.apache.commons:commons-text from 1.11.0 to 1.12.0 URL: https://github.com/apache/maven-shared-utils/pull/177 -- 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.16.1 to 2.18.0 [maven-shared-utils]
dependabot[bot] opened a new pull request, #184: URL: https://github.com/apache/maven-shared-utils/pull/184 Bumps commons-io:commons-io from 2.16.1 to 2.18.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) -- 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-text from 1.11.0 to 1.12.0 [maven-shared-utils]
dependabot[bot] commented on PR #177: URL: https://github.com/apache/maven-shared-utils/pull/177#issuecomment-2546599062 Superseded by #183. -- 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.16.1 to 2.17.0 [maven-shared-utils]
dependabot[bot] commented on PR #182: URL: https://github.com/apache/maven-shared-utils/pull/182#issuecomment-2546599132 Superseded by #184. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8284) Re-enable s390x Jenkins CI
[ https://issues.apache.org/jira/browse/MNG-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906201#comment-17906201 ] Tamas Cservenak commented on MNG-8284: -- Hi Namrata, any news about these runners? > Re-enable s390x Jenkins CI > -- > > Key: MNG-8284 > URL: https://issues.apache.org/jira/browse/MNG-8284 > Project: Maven > Issue Type: Task >Reporter: Namrata Bhave >Priority: Major > Labels: CI/CD, Jenkins > > Hi, > s390x CI started failing since a few days ago with error : > error: invalid flag: -proc:full > [https://ci-maven.apache.org/job/Maven/job/maven-core.s390x/job/master/] > > We had raised issue with apache infra team to update java version to fix this > error and it is resolved now. > However with PR [https://github.com/apache/maven/pull/1761] Jenkins seems to > have been disabled for all archs. > Can you please re enable the Jenkins CI for s390x? > We are looking forward to keep this CI active as it helps in catching issues > early on s390x. > > Thank you for your support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRRESOURCES-147) Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0
Slawomir Jaranowski created MRRESOURCES-147: --- Summary: Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0 Key: MRRESOURCES-147 URL: https://issues.apache.org/jira/browse/MRRESOURCES-147 Project: Maven Remote Resources Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MRRESOURCES-147] Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0 [maven-remote-resources-plugin]
slawekjaranowski merged PR #62: URL: https://github.com/apache/maven-remote-resources-plugin/pull/62 -- 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] (MRRESOURCES-147) Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0
[ https://issues.apache.org/jira/browse/MRRESOURCES-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MRRESOURCES-147. --- Resolution: Fixed > Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0 > > > Key: MRRESOURCES-147 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-147 > Project: Maven Remote Resources 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] (MRRESOURCES-147) Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0
[ https://issues.apache.org/jira/browse/MRRESOURCES-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906202#comment-17906202 ] ASF GitHub Bot commented on MRRESOURCES-147: slawekjaranowski merged PR #62: URL: https://github.com/apache/maven-remote-resources-plugin/pull/62 > Bump org.apache.maven.shared:maven-filtering from 3.3.2 to 3.4.0 > > > Key: MRRESOURCES-147 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-147 > Project: Maven Remote Resources 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] [Assigned] (MNG-8435) (test) Bump net.bytebuddy:byte-buddy from 1.15.10 to 1.15.11
[ https://issues.apache.org/jira/browse/MNG-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8435: Assignee: Tamas Cservenak > (test) Bump net.bytebuddy:byte-buddy from 1.15.10 to 1.15.11 > > > Key: MNG-8435 > URL: https://issues.apache.org/jira/browse/MNG-8435 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRRESOURCES-148) Bump org.apache.velocity:velocity-engine-core from 2.3 to 2.4.1
Slawomir Jaranowski created MRRESOURCES-148: --- Summary: Bump org.apache.velocity:velocity-engine-core from 2.3 to 2.4.1 Key: MRRESOURCES-148 URL: https://issues.apache.org/jira/browse/MRRESOURCES-148 Project: Maven Remote Resources Plugin Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump org.junit:junit-bom from 5.11.3 to 5.11.4 [maven-toolchains-plugin]
dependabot[bot] opened a new pull request, #47: URL: https://github.com/apache/maven-toolchains-plugin/pull/47 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.11.3 to 5.11.4. Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit:junit-bom's releases. JUnit 5.11.4 = Platform 1.11.4 + Jupiter 5.11.4 + Vintage 5.11.4 See http://junit.org/junit5/docs/5.11.4/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.11.3...r5.11.4";>https://github.com/junit-team/junit5/compare/r5.11.3...r5.11.4 Commits https://github.com/junit-team/junit5/commit/6430ba4f653f6ae42f326cd0731b259ee699c719";>6430ba4 Release 5.11.4 https://github.com/junit-team/junit5/commit/d09312174e38e36ec7ac9b35f7033d6a2b693125";>d093121 Finalize 5.11.4 release notes https://github.com/junit-team/junit5/commit/0444353084f7c47bb29e785b10cf3e835454c2da";>0444353 Fix Maven integration tests on JDK 24 https://github.com/junit-team/junit5/commit/b5c7f4eeaff5b8a654e9ea6b78227cf90345b0ae";>b5c7f4e Move https://redirect.github.com/junit-team/junit5/issues/4153";>#4153 to 5.11.4 release notes https://github.com/junit-team/junit5/commit/b20c4e2eaed8a97536d48f7bb084a4bd828a56a9";>b20c4e2 Ensure the XMLStreamWriter is closed after use https://github.com/junit-team/junit5/commit/6376f0ab367f1ac17ce75b5410e68090b03b9d9b";>6376f0a Configure Git username and email https://github.com/junit-team/junit5/commit/2b485c4286531fe7f3aa70367a27cf141c669a12";>2b485c4 Set reference repo URI https://github.com/junit-team/junit5/commit/500b5a06b5964a477e65719877653bae0e2496fc";>500b5a0 Inject username and password via new DSL https://github.com/junit-team/junit5/commit/d67196188fb63fa5a35f63caf168dc42cecfaca8";>d671961 Update plugin gitPublish to v5 https://github.com/junit-team/junit5/commit/3d11279dbaae5aac0ab5f28d8283272bdbca924f";>3d11279 Add JAVA_25 to JRE enum Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.11.3...r5.11.4";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Maven 4 Compatibility Testing [maven]
gnodet closed pull request #1986: Maven 4 Compatibility Testing URL: https://github.com/apache/maven/pull/1986 -- 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] Maven 4 Compatibility Testing [maven]
gnodet commented on PR #1986: URL: https://github.com/apache/maven/pull/1986#issuecomment-2547006984 > We can also enable Maven4 by default in our builds - https://github.com/apache/maven-gh-actions-shared?tab=readme-ov-file#testing-with-maven-4 I'm currently mostly interested in finding issues in Maven 4 rather than fixing our own builds, so I don't want to focus on Maven projects only. I've created https://github.com/gnodet/maven4-testing whith in-progress testing results at https://github.com/gnodet/maven4-testing/issues/133 -- 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] Maven 4 Compatibility Testing [maven]
cstamas commented on PR #1986: URL: https://github.com/apache/maven/pull/1986#issuecomment-2547011782 We may want to add tool based on your findings, like: * up enforcer (if under some version) to the version that works with mvn4 (not to "latest") * same for exec-m-p * and so on... All input on this are welcome! -- 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] update shared utils [maven-surefire]
elharo closed pull request #652: update shared utils URL: https://github.com/apache/maven-surefire/pull/652 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-8403) Make ITs support all CLI commands
[ https://issues.apache.org/jira/browse/MNG-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8403: - Issue Type: Improvement (was: Task) > Make ITs support all CLI commands > - > > Key: MNG-8403 > URL: https://issues.apache.org/jira/browse/MNG-8403 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-2 > > > The change results in simplified IT infrastructure, from IT classpath removed > stuff are: > * maven-shared-utils > * maven-verifier > And new IT infrastructure relies on maven-executor module introduced with > CLIng (maven-cli and maven-executor are two new modules). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8394) Event bridge and properties fix
[ https://issues.apache.org/jira/browse/MNG-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8394: - Issue Type: Improvement (was: Task) > Event bridge and properties fix > --- > > Key: MNG-8394 > URL: https://issues.apache.org/jira/browse/MNG-8394 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-2 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1937 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8406) IT suite proper isolation
[ https://issues.apache.org/jira/browse/MNG-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8406: - Issue Type: Improvement (was: Task) > IT suite proper isolation > - > > Key: MNG-8406 > URL: https://issues.apache.org/jira/browse/MNG-8406 > Project: Maven > Issue Type: Improvement > Components: Integration Tests >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-2 > > > The Maven ITs were never properly isolated, in a sense they use real user > home, hence user settings.xml, and whatever user env may contain are picked > up (and this is today quite wrong, as we can have user wide extensions as > well). > The ITs should run in proper "sandbox" instead, in fully isolated "IT user > home" instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8404) ModelValidator: add unit tests and simplify a bit
[ https://issues.apache.org/jira/browse/MNG-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8404: - Issue Type: Improvement (was: Task) > ModelValidator: add unit tests and simplify a bit > - > > Key: MNG-8404 > URL: https://issues.apache.org/jira/browse/MNG-8404 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-rc-2 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1948 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8415) Add constant for the security settings xml file
[ https://issues.apache.org/jira/browse/MNG-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated MNG-8415: - Issue Type: Improvement (was: Task) > Add constant for the security settings xml file > --- > > Key: MNG-8415 > URL: https://issues.apache.org/jira/browse/MNG-8415 > Project: Maven > Issue Type: Improvement >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.0.0-rc-2 > > > GitHub Pull Request: https://github.com/apache/maven/pull/1956 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Remove dependency on commons-lang *2* [maven-changelog-plugin]
elharo opened a new pull request, #31: URL: https://github.com/apache/maven-changelog-plugin/pull/31 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] MCHANGELOG-151 - Migrate plugin to Maven 3.0.5 [maven-changelog-plugin]
elharo closed pull request #1: MCHANGELOG-151 - Migrate plugin to Maven 3.0.5 URL: https://github.com/apache/maven-changelog-plugin/pull/1 -- 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] MCHANGELOG-151 - Migrate plugin to Maven 3.0.5 [maven-changelog-plugin]
elharo commented on PR #1: URL: https://github.com/apache/maven-changelog-plugin/pull/1#issuecomment-2547125057 pretty sure this one is obsolete -- 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] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906219#comment-17906219 ] ASF GitHub Bot commented on MCHANGELOG-151: --- elharo closed pull request #1: MCHANGELOG-151 - Migrate plugin to Maven 3.0.5 URL: https://github.com/apache/maven-changelog-plugin/pull/1 > Migrate plugin to Maven 3.6.3 > - > > Key: MCHANGELOG-151 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-151 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > > * Replacing usage of deprecated APIs > * Renaming the packages to org.apache.maven.plugins > * Removing Maven 2 specific code > * Fixing Javadoc comments > * Removing the use of raw types where possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906220#comment-17906220 ] ASF GitHub Bot commented on MCHANGELOG-151: --- elharo commented on PR #1: URL: https://github.com/apache/maven-changelog-plugin/pull/1#issuecomment-2547125057 pretty sure this one is obsolete > Migrate plugin to Maven 3.6.3 > - > > Key: MCHANGELOG-151 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-151 > Project: Maven Changelog Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.0.0 > > > * Replacing usage of deprecated APIs > * Renaming the packages to org.apache.maven.plugins > * Removing Maven 2 specific code > * Fixing Javadoc comments > * Removing the use of raw types where possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8439) mvnenc init is busted
[ https://issues.apache.org/jira/browse/MNG-8439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8439: Assignee: Tamas Cservenak > mvnenc init is busted > - > > Key: MNG-8439 > URL: https://issues.apache.org/jira/browse/MNG-8439 > Project: Maven > Issue Type: Bug >Affects Versions: 4.0.0-rc-2 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > > The upgrade to JLine3 3.28.0 caused a breakage in mvnenc init, as > ConsolePrompt got incompatible changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8439) mvnenc init is busted
Tamas Cservenak created MNG-8439: Summary: mvnenc init is busted Key: MNG-8439 URL: https://issues.apache.org/jira/browse/MNG-8439 Project: Maven Issue Type: Bug Affects Versions: 4.0.0-rc-2 Reporter: Tamas Cservenak Fix For: 4.0.0-rc-3 The upgrade to JLine3 3.28.0 caused a breakage in mvnenc init, as ConsolePrompt got incompatible changes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] #MNGSITE-539 Add Maven CI Friendly Versions to menu [maven-site]
Bukama commented on PR #594: URL: https://github.com/apache/maven-site/pull/594#issuecomment-2545916380 > Can you split the PR so that we can review the reformat / actual changes ? Yeah sure. Opened #595 to just contain the formatting of the effected files. Will then rebase/redo the actual changes to add the guide to the menu etc. -- 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] (MNGSITE-539) The maven site does not contain a link to ci friendly
[ https://issues.apache.org/jira/browse/MNGSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906085#comment-17906085 ] ASF GitHub Bot commented on MNGSITE-539: Bukama commented on PR #594: URL: https://github.com/apache/maven-site/pull/594#issuecomment-2545916380 > Can you split the PR so that we can review the reformat / actual changes ? Yeah sure. Opened #595 to just contain the formatting of the effected files. Will then rebase/redo the actual changes to add the guide to the menu etc. > The maven site does not contain a link to ci friendly > - > > Key: MNGSITE-539 > URL: https://issues.apache.org/jira/browse/MNGSITE-539 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > > The whole maven.apache.org site does not contain a link either from users / > index etc. to the https://maven.apache.org/maven-ci-friendly.html page... yes > it's part of the release notes ... but it should be references somewhere else > as well... -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8370] Add maven.repo.local.head [maven]
slawekjaranowski merged PR #1915: URL: https://github.com/apache/maven/pull/1915 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-8370) Introduce maven.repo.local.head
[ https://issues.apache.org/jira/browse/MNG-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MNG-8370: - Fix Version/s: 3.9.10 > Introduce maven.repo.local.head > --- > > Key: MNG-8370 > URL: https://issues.apache.org/jira/browse/MNG-8370 > Project: Maven > Issue Type: Improvement > Components: Command Line >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.10, 4.0.0-rc-1 > > > Similar to maven.repo.local.tail, but this one "prepend" and instead of > "append". -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.apache.maven.plugins:maven-plugins from 42 to 43 [maven-doap-plugin]
elharo commented on PR #27: URL: https://github.com/apache/maven-doap-plugin/pull/27#issuecomment-2545483756 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8435) (test) Bump net.bytebuddy:byte-buddy from 1.15.10 to 1.15.11
Tamas Cservenak created MNG-8435: Summary: (test) Bump net.bytebuddy:byte-buddy from 1.15.10 to 1.15.11 Key: MNG-8435 URL: https://issues.apache.org/jira/browse/MNG-8435 Project: Maven Issue Type: Dependency upgrade Components: Dependencies Reporter: Tamas Cservenak Fix For: 4.0.0-rc-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8437) New tool: mvnsh
[ https://issues.apache.org/jira/browse/MNG-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8437: Assignee: Tamas Cservenak > New tool: mvnsh > --- > > Key: MNG-8437 > URL: https://issues.apache.org/jira/browse/MNG-8437 > Project: Maven > Issue Type: New Feature > Components: Command Line >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > > Introduce new tool: mvnsh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8437) New tool: mvnsh
Tamas Cservenak created MNG-8437: Summary: New tool: mvnsh Key: MNG-8437 URL: https://issues.apache.org/jira/browse/MNG-8437 Project: Maven Issue Type: New Feature Components: Command Line Reporter: Tamas Cservenak Fix For: 4.0.0-rc-3 Introduce new tool: mvnsh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Maven 4 Compatibility Testing [maven]
gnodet opened a new pull request, #1986: URL: https://github.com/apache/maven/pull/1986 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use try with resources [maven-doap-plugin]
elharo commented on code in PR #28:
URL: https://github.com/apache/maven-doap-plugin/pull/28#discussion_r1886952613
##
src/main/java/org/apache/maven/plugin/doap/DoapUtil.java:
##
@@ -688,24 +684,18 @@ private static String getLowerCaseString(I18N i18n,
String key) {
*/
private static String getPluginVersion() {
Properties pomProperties = new Properties();
-InputStream is = null;
-try {
-is = DoapUtil.class.getResourceAsStream(
-"/META-INF/maven/org.apache.maven.plugins/" +
"maven-doap-plugin/pom.properties");
+
+try (InputStream is = DoapUtil.class.getResourceAsStream(
Review Comment:
If you mean in the implicit finally block, don't think so. That's one of the
things try with resources handles. It doesn't invoke on null.
https://stackoverflow.com/questions/35372148/try-with-resource-when-autocloseable-is-null
If you see a an exception on some other path, I'm not seeing it yet.
--
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.plugins:maven-plugins from 42 to 43 [maven-doap-plugin]
dependabot[bot] commented on PR #27: URL: https://github.com/apache/maven-doap-plugin/pull/27#issuecomment-2545841345 Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request `@dependabot recreate`. -- 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-interpolation from 1.26 to 1.27 [maven-doap-plugin]
elharo commented on PR #21: URL: https://github.com/apache/maven-doap-plugin/pull/21#issuecomment-2545840224 https://github.com/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.plugins:maven-plugins from 42 to 43 [maven-doap-plugin]
elharo commented on PR #27: URL: https://github.com/apache/maven-doap-plugin/pull/27#issuecomment-2545841117 @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 net.bytebuddy:byte-buddy from 1.15.5 to 1.15.10 [maven-plugin-tools]
dependabot[bot] commented on PR #342: URL: https://github.com/apache/maven-plugin-tools/pull/342#issuecomment-2545662497 Superseded by #347. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.10 [maven-plugin-tools]
dependabot[bot] closed pull request #342: Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.10 URL: https://github.com/apache/maven-plugin-tools/pull/342 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump net.bytebuddy:byte-buddy from 1.15.5 to 1.15.11 [maven-plugin-tools]
dependabot[bot] opened a new pull request, #347: URL: https://github.com/apache/maven-plugin-tools/pull/347 Bumps [net.bytebuddy:byte-buddy](https://github.com/raphw/byte-buddy) from 1.15.5 to 1.15.11. Release notes Sourced from https://github.com/raphw/byte-buddy/releases";>net.bytebuddy:byte-buddy's releases. Byte Buddy 1.15.11 Avoid dependency of CachedReturnPlugin on precompiled class files. Add NOP instruction when Advice is used on void methods as those might be empty which results on a frame being written to the same offset, causing an exception. Allow Plugin.Enging to link files instead of copying. Adjust validator code to avoid compiler bug that was reported by multiple users. Allow injection of class path as File[] to Plugin constructors. Allow for configuring variants when using the Android Gradle plugin. Byte Buddy 1.15.10 Fix Java 8 patterns for multi-release jars to avoid that inner classes are excluded. Byte Buddy 1.15.9 Additional release after time out during previous Gradle plugin release. Byte Buddy 1.15.8 Extend ClassInjector API to support lazy resolution of class files. Extend DynamicType API to support lazy resolution of auxiliary types. Extend AgentBuilder.Transformer.ForAdvice to support injection of new classes by their name. Byte Buddy 1.15.7 Additional release after time out during previous Gradle plugin release. Byte Buddy 1.15.6 Add ConstructorResolver to Super annotation for MethodDelegation to allow for dynamic constructor resolution. Add Java 8 versions of shaded ASM to allow for faster class file validation and CDS support. Changelog Sourced from https://github.com/raphw/byte-buddy/blob/master/release-notes.md";>net.bytebuddy:byte-buddy's changelog. 15. December 2024: version 1.15.11 Avoid dependency of CachedReturnPlugin on precompiled class files. Add NOP instruction when Advice is used on void methods as those might be empty which results on a frame being written to the same offset, causing an exception. Allow Plugin.Enging to link files instead of copying. Adjust validator code to avoid compiler bug that was reported by multiple users. Allow injection of class path as File[] to Plugin constructors. Allow for configuring variants when using the Android Gradle plugin. 4. November 2024: version 1.15.10 Fix Java 8 patterns for multi-release jars to avoid that inner classes are excluded. 3. November 2024: version 1.15.9 Additional release after time out during previous Gradle plugin release. 1. November 2024: version 1.15.8 Extend ClassInjector API to support lazy resolution of class files. Extend DynamicType API to support lazy resolution of auxiliary types. Extend AgentBuilder.Transformer.ForAdvice to support injection of new classes by their name. 23. October 2024: version 1.15.7 Additional release after time out during previous Gradle plugin release. 21. October 2024: version 1.15.6 Add ConstructorResolver to Super annotation for MethodDelegation to allow for dynamic constructor resolution. Add Java 8 versions of shaded ASM to allow for faster class file validation and CDS support. Commits https://github.com/raphw/byte-buddy/commit/08578b9b02c9837ef811fdbe1ec55949bc522fee";>08578b9 [maven-release-plugin] prepare release byte-buddy-1.15.11 https://github.com/raphw/byte-buddy/commit/8b4485f34205f47a4c9e797eee43dbfc4c750db5";>8b4485f [release] Release new version https://github.com/raphw/byte-buddy/commit/e9bde621ea67f47436818264aa713c3ef1640fc8";>e9bde62 Add checksums for new release plugin. https://github.com/raphw/byte-buddy/commit/268bf967378d9194a244a87423c7e15392a869f9";>268bf96 [release] Release new version https://github.com/raphw/byte-buddy/commit/c15c880139bc434d8d8df246402b6ee540b307e6";>c15c880 Clean up build and remove access to projects from Maven and Gradle plugins as... https://github.com/raphw/byte-buddy/commit/efbd6cb453a8c37ec610bbdaeb8c382c0eaac139";>efbd6cb Remove debug output. https://github.com/raphw/byte-buddy/commit/5237719ef1bd7c33f6bc0017dbb66299e476fb69";>5237719 Clean up code according to existing conventions. https://github.com/raphw/byte-buddy/commit/ea9ad3df1aa256cdc2db0f373b0899b93603fdd7";>ea9ad3d Config avoidance (https://redirect.github.com/raphw/byte-buddy/issues/1737";>#1737) https://github.com/raphw/byte-buddy/commit/f071a02cb82229bdfe1a97042eff538b6569d641";>f071a02 Add additional arguments to plugins. https://github.com/raphw/byte-buddy/commit/01d06f97b1207d4f4d72c97e157233ada56bdd8c";>01d06f9 Avoid JIT compilation bug in validator. Additional commits viewable in https://github.com/raphw/byte-buddy/compare/byte-buddy-1.15.5...byte-buddy-1.15.11";>compare view [![De
Re: [PR] Prefer Guice injection [maven-jdeps-plugin]
elharo merged PR #19: URL: https://github.com/apache/maven-jdeps-plugin/pull/19 -- 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] (MNGSITE-539) The maven site does not contain a link to ci friendly
[ https://issues.apache.org/jira/browse/MNGSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906084#comment-17906084 ] ASF GitHub Bot commented on MNGSITE-539: Bukama opened a new pull request, #595: URL: https://github.com/apache/maven-site/pull/595 This PR formats the files that will later be updated with the actual content for MNGSITE-539, so the formatting is split. > The maven site does not contain a link to ci friendly > - > > Key: MNGSITE-539 > URL: https://issues.apache.org/jira/browse/MNGSITE-539 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > > The whole maven.apache.org site does not contain a link either from users / > index etc. to the https://maven.apache.org/maven-ci-friendly.html page... yes > it's part of the release notes ... but it should be references somewhere else > as well... -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Remove commented code [maven-jdeps-plugin]
elharo commented on PR #17: URL: https://github.com/apache/maven-jdeps-plugin/pull/17#issuecomment-2545472617 > Tbh why simple changes like this - not simply merge it without review? 14 years at Google trained me to never merge anything without review. :-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Remove commented code [maven-jdeps-plugin]
elharo merged PR #17: URL: https://github.com/apache/maven-jdeps-plugin/pull/17 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Remove commented code [maven-jdeps-plugin]
elharo opened a new pull request, #17: URL: https://github.com/apache/maven-jdeps-plugin/pull/17 We use git -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (MDOAP-66) Don't assume latest release is "Stable"
[ https://issues.apache.org/jira/browse/MDOAP-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MDOAP-66. Fix Version/s: 3.0.0 Resolution: Fixed > Don't assume latest release is "Stable" > --- > > Key: MDOAP-66 > URL: https://issues.apache.org/jira/browse/MDOAP-66 > Project: Maven DOAP Plugin > Issue Type: Bug >Reporter: Brian Demers >Priority: Major > Fix For: 3.0.0 > > > The DOAP plugin assumes that the lastest release in the Maven metadata is > "stable". > https://github.com/apache/maven-doap-plugin/blob/04a8fb9ec390830783169701c1d60e95b7dd5bfc/src/main/java/org/apache/maven/plugin/doap/DoapMojo.java#L1337 > The term "latest" does not imply anything about stability, nor release > sequence. I could release 2.1.1 today, and 1.2.3 tomorrow. 1.2.3 would be > marked "latest stable release" > Or I could release 2.0.0-alpha1, and that would be labeled as "Latest stable > release". > My suggestion would be remove this code branch, and not make any assumptions > about the version name -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8436) Transfer speeds are off
Tamas Cservenak created MNG-8436:
Summary: Transfer speeds are off
Key: MNG-8436
URL: https://issues.apache.org/jira/browse/MNG-8436
Project: Maven
Issue Type: Bug
Affects Versions: 4.0.0-rc-2
Reporter: Tamas Cservenak
Fix For: 4.0.0-rc-3
{noformat}
Downloaded from central:
https://repo.maven.apache.org/maven2/org/graalvm/compiler/compiler/24.1.1/compiler-24.1.1.pom
(1.7 kB at 9223372036854775807 GB/s)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.codehaus.mojo:l10n-maven-plugin from 1.0.0 to 1.1.0 [maven-doap-plugin]
dependabot[bot] opened a new pull request, #29: URL: https://github.com/apache/maven-doap-plugin/pull/29 Bumps [org.codehaus.mojo:l10n-maven-plugin](https://github.com/mojohaus/l10n-maven-plugin) from 1.0.0 to 1.1.0. Commits https://github.com/mojohaus/l10n-maven-plugin/commit/844f5b1b79acbe817820e6c4af1b3001164993a5";>844f5b1 [maven-release-plugin] prepare release 1.1.0 https://github.com/mojohaus/l10n-maven-plugin/commit/73832eecbecd3222a3da583008dd72e6410e3d54";>73832ee Upgrade to site descriptor 2.x https://github.com/mojohaus/l10n-maven-plugin/commit/d93a2a77caa398b03f5abdad71b50260588c335a";>d93a2a7 Upgrade doxia to 2.x stack and code cleanups https://github.com/mojohaus/l10n-maven-plugin/commit/07d94f39e0b2285fa28bb8e149e37e15e2d005ee";>07d94f3 Require Maven 3.6.3+ https://github.com/mojohaus/l10n-maven-plugin/commit/bd19c248aa7e84eb4fc0ba589ec8a280dd31e412";>bd19c24 Code reformat https://github.com/mojohaus/l10n-maven-plugin/commit/0f968b79d7b50cfe1d9009a530e3185426338917";>0f968b7 Bump org.codehaus.mojo:mojo-parent from 78 to 86 https://github.com/mojohaus/l10n-maven-plugin/commit/dec787e2fbf7d6911d7caf44576f4c7b929ea02c";>dec787e Bump apache/maven-gh-actions-shared from 3 to 4 https://github.com/mojohaus/l10n-maven-plugin/commit/6ab01f5a9bdde18b0a125e48e4afcff21aedef80";>6ab01f5 Bump org.codehaus.mojo:mojo-parent from 72 to 78 (https://redirect.github.com/mojohaus/l10n-maven-plugin/issues/19";>#19) https://github.com/mojohaus/l10n-maven-plugin/commit/64d574e21565c09ad76e80029b677ecda3f73d2d";>64d574e Require Maven 3.5.4+ https://github.com/mojohaus/l10n-maven-plugin/commit/e03446c159c69927e37b52b1cbb6cbe5f29976da";>e03446c Bump apache/maven-gh-actions-shared from 2 to 3 Additional commits viewable in https://github.com/mojohaus/l10n-maven-plugin/compare/l10n-maven-plugin-1.0.0...1.1.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MDOAP-69) DoapMojoTest has bad exception testing that might be hiding failures
Elliotte Rusty Harold created MDOAP-69:
--
Summary: DoapMojoTest has bad exception testing that might be
hiding failures
Key: MDOAP-69
URL: https://issues.apache.org/jira/browse/MDOAP-69
Project: Maven DOAP Plugin
Issue Type: Bug
Reporter: Elliotte Rusty Harold
e.g.
try {
mojo.execute();
assertTrue("No lang checked", false);
} catch (Exception e) {
assertTrue(true);
}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.apache.commons:commons-text from 1.12.0 to 1.13.0 [maven-doxia]
dependabot[bot] opened a new pull request, #252: URL: https://github.com/apache/maven-doxia/pull/252 Bumps org.apache.commons:commons-text from 1.12.0 to 1.13.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) -- 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] (MWRAPPER-155) add jabbaw to mvnw
Stephan Kölle created MWRAPPER-155:
--
Summary: add jabbaw to mvnw
Key: MWRAPPER-155
URL: https://issues.apache.org/jira/browse/MWRAPPER-155
Project: Maven Wrapper
Issue Type: Wish
Components: Maven Wrapper Scripts
Affects Versions: 3.3.2
Reporter: Stephan Kölle
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi
{{}}
This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
[https://github.com/Jabba-Team/jabba] []|https://github.com/Jabba-Team/jabba],
specifically its "install-less" variant
([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
[https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[]|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[eam/jabba/blob/main/jabbaw.md
)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)], to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[eam/jabba/blob/main/jabbaw.md)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
to define a JDK version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [https://github.com/Jabba-Team/jabba], specifically its
> "install-less" variant
> ([https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
> [eam/jabba/blob/main/jabbaw.md
> )|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)], to define a JDK
> version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-T|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[eam/jabba/blob/main/jabbaw.md
)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)], to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[eam/jabba/blob/main/jabbaw.md
)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)], to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [https://github.com/Jabba-Team/jabba], specifically its
> "install-less" variant
> ([https://github.com/Jabba-T|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
> [eam/jabba/blob/main/jabbaw.md
> )|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)], to define a JDK
> version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[eam/jabba/blob/main/jabbaw.md)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
to define a JDK version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
[https://github.com/Jabba-Team/jabba] []|https://github.com/Jabba-Team/jabba],
specifically its "install-less" variant
([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
[https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[]|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [https://github.com/Jabba-Team/jabba], specifically its
> "install-less" variant
> ([https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
>
> [eam/jabba/blob/main/jabbaw.md)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
> to define a JDK version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
[https://github.com/Jabba-Team/jabba] []|https://github.com/Jabba-Team/jabba],
specifically its "install-less" variant
([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
[https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[]|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi
{{}}
This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
[https://github.com/Jabba-Team/jabba] []|https://github.com/Jabba-Team/jabba],
specifically its "install-less" variant
([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
[https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[]|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
> [https://github.com/Jabba-Team/jabba]
> []|https://github.com/Jabba-Team/jabba], specifically its "install-less"
> variant ([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
> [https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
>
> [Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
> []|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a
> JDK version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
(https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md[)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
to define a JDK version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-T|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[eam/jabba/blob/main/jabbaw.md
)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)], to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [https://github.com/Jabba-Team/jabba], specifically its
> "install-less" variant
> (https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md[)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
> to define a JDK version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md
|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md[])|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
to define a JDK version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
(https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md[)|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
to define a JDK version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [https://github.com/Jabba-Team/jabba], specifically its
> "install-less" variant
> ([https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md
> |https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md[])|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
> to define a JDK version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MWRAPPER-155) add jabbaw to mvnw
[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
---
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
[https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md] to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [https://github.com/Jabba-Team/jabba], specifically its
"install-less" variant
([https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md
|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md[])|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)],
to define a JDK version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> --
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Stephan Kölle
>Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [https://github.com/Jabba-Team/jabba], specifically its
> "install-less" variant
> [https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md] to define a JDK
> version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Don't assume latest release is stable [maven-doap-plugin]
elharo merged PR #14: URL: https://github.com/apache/maven-doap-plugin/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-8438) maven-jline: Migrate to Maven DI (off javax.inject)
Tamas Cservenak created MNG-8438: Summary: maven-jline: Migrate to Maven DI (off javax.inject) Key: MNG-8438 URL: https://issues.apache.org/jira/browse/MNG-8438 Project: Maven Issue Type: Task Reporter: Tamas Cservenak Fix For: 4.0.0-rc-3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8438) maven-jline: Migrate to Maven DI (off javax.inject)
[ https://issues.apache.org/jira/browse/MNG-8438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-8438: Assignee: Tamas Cservenak > maven-jline: Migrate to Maven DI (off javax.inject) > --- > > Key: MNG-8438 > URL: https://issues.apache.org/jira/browse/MNG-8438 > Project: Maven > Issue Type: Task >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-rc-3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-8436) Transfer speeds are off
[
https://issues.apache.org/jira/browse/MNG-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned MNG-8436:
Assignee: Guillaume Nodet
> Transfer speeds are off
> ---
>
> Key: MNG-8436
> URL: https://issues.apache.org/jira/browse/MNG-8436
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-2
>Reporter: Tamas Cservenak
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-rc-3
>
>
> {noformat}
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/graalvm/compiler/compiler/24.1.1/compiler-24.1.1.pom
> (1.7 kB at 9223372036854775807 GB/s)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Use try with reources [maven-doap-plugin]
michael-o commented on code in PR #28:
URL: https://github.com/apache/maven-doap-plugin/pull/28#discussion_r1886936600
##
src/main/java/org/apache/maven/plugin/doap/DoapUtil.java:
##
@@ -688,24 +684,18 @@ private static String getLowerCaseString(I18N i18n,
String key) {
*/
private static String getPluginVersion() {
Properties pomProperties = new Properties();
-InputStream is = null;
-try {
-is = DoapUtil.class.getResourceAsStream(
-"/META-INF/maven/org.apache.maven.plugins/" +
"maven-doap-plugin/pom.properties");
+
+try (InputStream is = DoapUtil.class.getResourceAsStream(
Review Comment:
Can this cause a NPE with automatic cleanup?
--
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] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MWRAPPER-146.
-
Fix Version/s: 3.3.3
Assignee: Sylwester Lachiewicz
Resolution: Fixed
> Bad substitution on Windows if MVNW_REPOURL is set on script-only
> -
>
> Key: MWRAPPER-146
> URL: https://issues.apache.org/jira/browse/MWRAPPER-146
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0, 3.3.1, 3.3.2
> Environment: Windows 10, Windows Server 2022 with powershell 5.1
>Reporter: Bruno Villegas
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.3.3
>
>
> Since version 3.3.0, we cannot download Maven distribution if we set
> MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
> script-only.
> {noformat}
> wrapperVersion=3.3.2
> distributionType=only-script
> distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip{noformat}
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) :
> « Le serveur distant a retourné une erreur : (404) Introuvable. »
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> If MVNW_VERBOSE is also set to "true" we can have some hints
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
> icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
> serveur distant a retourné une erreur:
> (404) Introuvable.»
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> $env:MVNW_REPOURL is concatened with mvnd context and the actual
> distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
> Looking at script mvnw.cmd, it seems that the following block is at fault
> {code:java}
> # apply MVNW_REPOURL and calculate MAVEN_HOME
> # maven home pattern:
> ~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
> if ($env:MVNW_REPOURL) {
> $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
> "/maven/mvnd/" }
> $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
> -replace '^.*'+$MVNW_REPO_PATTERN,'')"
> } {code}
> Two "bugs" in my opinion
> - USE_MVND evaluation is incorrect: should have been
> {code:java}
> if ($USE_MVND -eq $False){code}
> the variable USE_MVND is previously set to either $true or $false
>
> - The string substitution doesn't work correctly, the following works for my
> environment
> {code:java}
> $($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
> After fixing these two lines
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MWRAPPER-154) Bump commons-io:commons-io to 2.18.0
[ https://issues.apache.org/jira/browse/MWRAPPER-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905926#comment-17905926 ] ASF GitHub Bot commented on MWRAPPER-154: - slachiewicz merged PR #161: URL: https://github.com/apache/maven-wrapper/pull/161 > Bump commons-io:commons-io to 2.18.0 > > > Key: MWRAPPER-154 > URL: https://issues.apache.org/jira/browse/MWRAPPER-154 > Project: Maven Wrapper > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.3.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8434) Recursive variable reference
[
https://issues.apache.org/jira/browse/MNG-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905927#comment-17905927
]
Delany commented on MNG-8434:
-
My parent project sets the build element
{code:xml}
${build.finalName}
{code}
and the property
{code:xml}
${project.artifactId}-${project.version}
{code}
So it looks like Maven is now using that property even though I got there first!
It would be good if Maven could reserve a pattern for properties so we can
avoid a collision in future.
> Recursive variable reference
>
>
> Key: MNG-8434
> URL: https://issues.apache.org/jira/browse/MNG-8434
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-2
>Reporter: Delany
>Priority: Major
>
> With project wrapper/maven-wrapper.properties
> {code:java}
> wrapperVersion=3.3.2
> distributionType=only-script
> distributionUrl=https://repository.apache.org/content/repositories/maven-2256/org/apache/maven/apache-maven/4.0.0-rc-2/apache-maven-4.0.0-rc-2-bin.zip{code}
> a settings file profile
> {code:java}
>
> stage
>
>
> stage
>
>
>
>
> staging
> Maven Staging
>
> https://repository.apache.org/content/repositories/maven-${stage}/
>
>
>
>
> staging-plugin
> Maven Staging
>
> https://repository.apache.org/content/repositories/maven-${stage}/
>
>
> {code}
> and command
> {code:java}
> ./mvnw -N clean -Dstage=2256 -e{code}
> I get this error
> {code:java}
> [ERROR] The build could not read 1 project -> [Help 1]
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs
> at
> org.apache.maven.project.DefaultProjectBuilder$BuildSession.build(DefaultProjectBuilder.java:464)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:184)
> at
> org.apache.maven.project.collector.DefaultProjectsSelector.selectProjects(DefaultProjectsSelector.java:61)
> at
> org.apache.maven.project.collector.RequestPomCollectionStrategy.collectProjects(RequestPomCollectionStrategy.java:49)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:364)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:100)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:629)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:250)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:225)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:149)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.doExecute(MavenInvoker.java:470)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:95)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:85)
> at
> org.apache.maven.cling.invoker.LookupInvoker.doInvoke(LookupInvoker.java:145)
> at
> org.apache.maven.cling.invoker.LookupInvoker.invoke(LookupInvoker.java:116)
> at org.apache.maven.cling.ClingSupport.run(ClingSupport.java:64)
> at org.apache.maven.cling.MavenCling.main(MavenCling.java:51)
> at
> jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
> [ERROR]
> [ERROR] The project com.rushmore:rushmore-parent:2.4.1-SNAPSHOT
> (/git/rushmore/pom.xml) has 1 error
> [ERROR] recursive variable reference: build.finalName
> org.apache.maven.api.services.InterpolatorException: recursive variable
> reference: build.finalName
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.resolveVariable(DefaultInterpolator.java:374)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.processSubstitution(DefaultInterpolator.java:312)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.doSubstVars(DefaultInterpolator.java:271)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.resolveVariable(DefaultInterpolator.java:385)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.processSubstitution(DefaultInterpolator.java:312)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.doSubstVars(DefaultInterpolator.java:271)
> at
> org.apache.maven.internal.impl.mo
[jira] [Closed] (MWRAPPER-154) Bump commons-io:commons-io to 2.18.0
[ https://issues.apache.org/jira/browse/MWRAPPER-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MWRAPPER-154. - Resolution: Fixed > Bump commons-io:commons-io to 2.18.0 > > > Key: MWRAPPER-154 > URL: https://issues.apache.org/jira/browse/MWRAPPER-154 > Project: Maven Wrapper > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.3.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MWRAPPER-154) Bump commons-io:commons-io to 2.18.0
Sylwester Lachiewicz created MWRAPPER-154: - Summary: Bump commons-io:commons-io to 2.18.0 Key: MWRAPPER-154 URL: https://issues.apache.org/jira/browse/MWRAPPER-154 Project: Maven Wrapper Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz Fix For: 3.3.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MWRAPPER-154] Bump commons-io:commons-io from 2.16.1 to 2.18.0 [maven-wrapper]
slachiewicz merged PR #161: URL: https://github.com/apache/maven-wrapper/pull/161 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MWRAPPER-150] - Fails to validate checksums on MacOS Sequoia [maven-wrapper]
slachiewicz merged PR #155: URL: https://github.com/apache/maven-wrapper/pull/155 -- 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] (MWRAPPER-150) Fails to validate checksums on MacOS Sequoia
[
https://issues.apache.org/jira/browse/MWRAPPER-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905931#comment-17905931
]
ASF GitHub Bot commented on MWRAPPER-150:
-
slachiewicz merged PR #155:
URL: https://github.com/apache/maven-wrapper/pull/155
> Fails to validate checksums on MacOS Sequoia
>
>
> Key: MWRAPPER-150
> URL: https://issues.apache.org/jira/browse/MWRAPPER-150
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
> Environment: MacOS 15.0
>Reporter: Gonzalo Bermúdez
>Priority: Normal
>
> The command issued to check the sha256sum fails with sha256sum packaged with
> MacOS Sequoia.
> This can be reproduced with an empty project using mvnw, and adding the
> distribution's shasum on the affected OS.
>
> {code:java}
> $ mkdir test && cd test
> $ mvn wrapper:wrapper
> $ echo
> distributionSha256Sum=83aaf914c785c9faed661f223000a92d1de9553f5c82d3b4362e66d9c031625f
> >> .mvn/wrapper/maven-wrapper.properties
> $ ./mvnw compile
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-150) Fails to validate checksums on MacOS Sequoia
[
https://issues.apache.org/jira/browse/MWRAPPER-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MWRAPPER-150.
-
Fix Version/s: 3.3.3
Assignee: Sylwester Lachiewicz
Resolution: Fixed
> Fails to validate checksums on MacOS Sequoia
>
>
> Key: MWRAPPER-150
> URL: https://issues.apache.org/jira/browse/MWRAPPER-150
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
> Environment: MacOS 15.0
>Reporter: Gonzalo Bermúdez
>Assignee: Sylwester Lachiewicz
>Priority: Normal
> Fix For: 3.3.3
>
>
> The command issued to check the sha256sum fails with sha256sum packaged with
> MacOS Sequoia.
> This can be reproduced with an empty project using mvnw, and adding the
> distribution's shasum on the affected OS.
>
> {code:java}
> $ mkdir test && cd test
> $ mvn wrapper:wrapper
> $ echo
> distributionSha256Sum=83aaf914c785c9faed661f223000a92d1de9553f5c82d3b4362e66d9c031625f
> >> .mvn/wrapper/maven-wrapper.properties
> $ ./mvnw compile
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MWRAPPER-147] mvnw.cmd fails to launch maven if username contains space [maven-wrapper]
slachiewicz merged PR #152: URL: https://github.com/apache/maven-wrapper/pull/152 -- 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] (MWRAPPER-147) mvnw fails on Windows if user name contains whitespace
[
https://issues.apache.org/jira/browse/MWRAPPER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905934#comment-17905934
]
ASF GitHub Bot commented on MWRAPPER-147:
-
slachiewicz merged PR #152:
URL: https://github.com/apache/maven-wrapper/pull/152
> mvnw fails on Windows if user name contains whitespace
> --
>
> Key: MWRAPPER-147
> URL: https://issues.apache.org/jira/browse/MWRAPPER-147
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Sebastian T
>Priority: Major
>
> Calling mvnw I get:
>
> {noformat}
> > mvnw
> 'C:\Users\John' is not recognized as an internal or external command,
> operable program or batch file.
> Cannot start maven from wrapper
> {noformat}
> The command fails at line:
> {noformat}
> @IF NOT "%__MVNW_CMD__%"=="" (%__MVNW_CMD__% %*)
> {noformat}
> For debugging I changed the mvnw.cmd file and printed out the value of
> %__MVNW_CMD__% which is:
> {noformat}
> C:\Users\John
> Doe/.m2/wrapper/dists/apache-maven-3.9.9/977a63e90f436cd6ade95b4c0e10c20c/bin/mvn.cmd
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MWRAPPER-147) mvnw fails on Windows if user name contains whitespace
[
https://issues.apache.org/jira/browse/MWRAPPER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MWRAPPER-147.
-
Fix Version/s: 3.3.3
Assignee: Sylwester Lachiewicz
Resolution: Fixed
> mvnw fails on Windows if user name contains whitespace
> --
>
> Key: MWRAPPER-147
> URL: https://issues.apache.org/jira/browse/MWRAPPER-147
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.2
>Reporter: Sebastian T
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.3.3
>
>
> Calling mvnw I get:
>
> {noformat}
> > mvnw
> 'C:\Users\John' is not recognized as an internal or external command,
> operable program or batch file.
> Cannot start maven from wrapper
> {noformat}
> The command fails at line:
> {noformat}
> @IF NOT "%__MVNW_CMD__%"=="" (%__MVNW_CMD__% %*)
> {noformat}
> For debugging I changed the mvnw.cmd file and printed out the value of
> %__MVNW_CMD__% which is:
> {noformat}
> C:\Users\John
> Doe/.m2/wrapper/dists/apache-maven-3.9.9/977a63e90f436cd6ade95b4c0e10c20c/bin/mvn.cmd
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MWRAPPER-146] Bad substitution on Windows if MVNW_REPOURL is set on script-only [maven-wrapper]
slachiewicz merged PR #151: URL: https://github.com/apache/maven-wrapper/pull/151 -- 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] (MWRAPPER-146) Bad substitution on Windows if MVNW_REPOURL is set on script-only
[
https://issues.apache.org/jira/browse/MWRAPPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905936#comment-17905936
]
ASF GitHub Bot commented on MWRAPPER-146:
-
slachiewicz merged PR #151:
URL: https://github.com/apache/maven-wrapper/pull/151
> Bad substitution on Windows if MVNW_REPOURL is set on script-only
> -
>
> Key: MWRAPPER-146
> URL: https://issues.apache.org/jira/browse/MWRAPPER-146
> Project: Maven Wrapper
> Issue Type: Bug
> Components: Maven Wrapper Scripts
>Affects Versions: 3.3.0, 3.3.1, 3.3.2
> Environment: Windows 10, Windows Server 2022 with powershell 5.1
>Reporter: Bruno Villegas
>Priority: Major
>
> Since version 3.3.0, we cannot download Maven distribution if we set
> MVNW_REPOURL on Windows platforms (Windows 10, Windows Server 2022) with
> script-only.
> {noformat}
> wrapperVersion=3.3.2
> distributionType=only-script
> distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip{noformat}
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> icm : Exception lors de l'appel de « DownloadFile » avec « 2 » argument(s) :
> « Le serveur distant a retourné une erreur : (404) Introuvable. »
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> If MVNW_VERBOSE is also set to "true" we can have some hints
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/maven/mvnd/https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp950D.tmp.dir/apache-maven-3.9.9-bin.zip
> icm : Exception lors de l'appel de «DownloadFile» avec «2» argument(s): «Le
> serveur distant a retourné une erreur:
> (404) Introuvable.»
> Au caractère Ligne:1 : 72
> + ... 'mvnw.cmd'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw
> ...
> + ~
> + CategoryInfo : NotSpecified: (:) [Invoke-Command],
> MethodInvocationException
> + FullyQualifiedErrorId :
> WebException,Microsoft.PowerShell.Commands.InvokeCommandCommand
> Commande ECHO activée.
> Cannot start maven from wrapper{noformat}
> $env:MVNW_REPOURL is concatened with mvnd context and the actual
> distributionUrl defined inside .mvn/wrapper/maven-wrapper.properties
> Looking at script mvnw.cmd, it seems that the following block is at fault
> {code:java}
> # apply MVNW_REPOURL and calculate MAVEN_HOME
> # maven home pattern:
> ~/.m2/wrapper/dists/{apache-maven-,maven-mvnd--}/
> if ($env:MVNW_REPOURL) {
> $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else {
> "/maven/mvnd/" }
> $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl
> -replace '^.*'+$MVNW_REPO_PATTERN,'')"
> } {code}
> Two "bugs" in my opinion
> - USE_MVND evaluation is incorrect: should have been
> {code:java}
> if ($USE_MVND -eq $False){code}
> the variable USE_MVND is previously set to either $true or $false
>
> - The string substitution doesn't work correctly, the following works for my
> environment
> {code:java}
> $($distributionUrl -replace "^.*$MVNW_REPO_PATTERN",''){code}
> After fixing these two lines
> {noformat}
> PS C:\workspace\poc\maven-build> .\mvnw.cmd -v
> COMMENTAIRES : Couldn't find MAVEN_HOME, downloading and installing it ...
> COMMENTAIRES : Downloading from:
> https://nexus.local/repository/maven-repo/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
> COMMENTAIRES : Downloading to:
> C:\Users\jahk04\AppData\Local\Temp\tmp1DCA.tmp.dir/apache-maven-3.9.9-bin.zip
> {noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8434) Recursive variable reference
[
https://issues.apache.org/jira/browse/MNG-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed MNG-8434.
Resolution: Invalid
> Recursive variable reference
>
>
> Key: MNG-8434
> URL: https://issues.apache.org/jira/browse/MNG-8434
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-2
>Reporter: Delany
>Priority: Major
>
> With project wrapper/maven-wrapper.properties
> {code:java}
> wrapperVersion=3.3.2
> distributionType=only-script
> distributionUrl=https://repository.apache.org/content/repositories/maven-2256/org/apache/maven/apache-maven/4.0.0-rc-2/apache-maven-4.0.0-rc-2-bin.zip{code}
> a settings file profile
> {code:java}
>
> stage
>
>
> stage
>
>
>
>
> staging
> Maven Staging
>
> https://repository.apache.org/content/repositories/maven-${stage}/
>
>
>
>
> staging-plugin
> Maven Staging
>
> https://repository.apache.org/content/repositories/maven-${stage}/
>
>
> {code}
> and command
> {code:java}
> ./mvnw -N clean -Dstage=2256 -e{code}
> I get this error
> {code:java}
> [ERROR] The build could not read 1 project -> [Help 1]
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs
> at
> org.apache.maven.project.DefaultProjectBuilder$BuildSession.build(DefaultProjectBuilder.java:464)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:184)
> at
> org.apache.maven.project.collector.DefaultProjectsSelector.selectProjects(DefaultProjectsSelector.java:61)
> at
> org.apache.maven.project.collector.RequestPomCollectionStrategy.collectProjects(RequestPomCollectionStrategy.java:49)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:364)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:100)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:629)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:250)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:225)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:149)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.doExecute(MavenInvoker.java:470)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:95)
> at
> org.apache.maven.cling.invoker.mvn.MavenInvoker.execute(MavenInvoker.java:85)
> at
> org.apache.maven.cling.invoker.LookupInvoker.doInvoke(LookupInvoker.java:145)
> at
> org.apache.maven.cling.invoker.LookupInvoker.invoke(LookupInvoker.java:116)
> at org.apache.maven.cling.ClingSupport.run(ClingSupport.java:64)
> at org.apache.maven.cling.MavenCling.main(MavenCling.java:51)
> at
> jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke(Method.java:580)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
> [ERROR]
> [ERROR] The project com.rushmore:rushmore-parent:2.4.1-SNAPSHOT
> (/git/rushmore/pom.xml) has 1 error
> [ERROR] recursive variable reference: build.finalName
> org.apache.maven.api.services.InterpolatorException: recursive variable
> reference: build.finalName
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.resolveVariable(DefaultInterpolator.java:374)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.processSubstitution(DefaultInterpolator.java:312)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.doSubstVars(DefaultInterpolator.java:271)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.resolveVariable(DefaultInterpolator.java:385)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.processSubstitution(DefaultInterpolator.java:312)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.doSubstVars(DefaultInterpolator.java:271)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.substVars(DefaultInterpolator.java:206)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.interpolate(DefaultInterpolator.java:86)
> at
> org.apache.maven.internal.impl.model.DefaultInterpolator.interpolate(DefaultInterpolator.java:75)
> at
> org.apache.maven.internal.impl.model.DefaultModelInterpolator.lam
[PR] Fix wrong transfer rates displayed in console [maven]
gnodet opened a new pull request, #1985: URL: https://github.com/apache/maven/pull/1985 ``` Downloaded from central: https://repo.maven.apache.org/maven2/org/graalvm/compiler/compiler/24.1.1/compiler-24.1.1.pom (1.7 kB at 9223372036854775807 GB/s) ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8412) mvnenc bug: UI doubles selectable components
[
https://issues.apache.org/jira/browse/MNG-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905980#comment-17905980
]
Thorsten Heit commented on MNG-8412:
I have seen the same behaviour on my machine, but cannot directly reproduce it:
Re-executing {{mvnenc init --force}} and selecting the same menu sometimes
shows a correct list of menu entries (not doubled), sometimes not...
> mvnenc bug: UI doubles selectable components
>
>
> Key: MNG-8412
> URL: https://issues.apache.org/jira/browse/MNG-8412
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-rc-1
>Reporter: Tamas Cservenak
>Assignee: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0-rc-2
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Almost all of the components are doubled, screenshots attached.
> !screenshot-1.png!
> !screenshot-2.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump maven.resolver.version from 2.0.4 to 2.0.5 [maven-mvnd]
dependabot[bot] opened a new pull request, #1229: URL: https://github.com/apache/maven-mvnd/pull/1229 Bumps `maven.resolver.version` from 2.0.4 to 2.0.5. Updates `org.apache.maven.resolver:maven-resolver-api` from 2.0.4 to 2.0.5 Commits https://github.com/apache/maven-resolver/commit/94c49fa2dcec64f5b46ddd93ba5c5e71f8d50cc9";>94c49fa [maven-release-plugin] prepare release maven-resolver-2.0.5 https://github.com/apache/maven-resolver/commit/111210143d142bca48202c3552b333690c542999";>1112101 [MRESOLVER-649] Bump org.jboss.forge.roaster:roaster-jdt (https://redirect.github.com/apache/maven-resolver/issues/624";>#624) https://github.com/apache/maven-resolver/commit/1a984628347bba0f686defce91db16ba18c8875f";>1a98462 [MRESOLVER-648] Bump org.jboss.forge.roaster:roaster-api (https://redirect.github.com/apache/maven-resolver/issues/623";>#623) https://github.com/apache/maven-resolver/commit/708fc751e4a0294313a19350d32ea3ea2ed0ee11";>708fc75 [MRESOLVER-647] Bump org.redisson:redisson from 3.40.1 to 3.40.2 (https://redirect.github.com/apache/maven-resolver/issues/622";>#622) https://github.com/apache/maven-resolver/commit/c4ca019062fd0b60a063309141b2895c32d8425c";>c4ca019 [MRESOLVER-632][MRESOLVER-640] Remove unneded error cases (https://redirect.github.com/apache/maven-resolver/issues/620";>#620) https://github.com/apache/maven-resolver/commit/77e9b91f2cead907615fcdfba208a3213c316901";>77e9b91 [MRESOLVER-645] Remove repeated LRM interaction (https://redirect.github.com/apache/maven-resolver/issues/611";>#611) https://github.com/apache/maven-resolver/commit/6f70e524289b741c1c6c992c99fa44cb07ae7523";>6f70e52 [MRESOLVER-644] Artifact Transformer SPI (https://redirect.github.com/apache/maven-resolver/issues/605";>#605) https://github.com/apache/maven-resolver/commit/9711a38b5340ea92a4c27c15af7bf5dd2cab8bde";>9711a38 Update CI and Maven https://github.com/apache/maven-resolver/commit/709d753a79dd7984446ac4e016ab61e34a5897e4";>709d753 [MRESOLVER-643] Bump org.jboss.forge.roaster:roaster-jdt (https://redirect.github.com/apache/maven-resolver/issues/617";>#617) https://github.com/apache/maven-resolver/commit/b3b38aca5a1d55604f47a792b111bd92ab707938";>b3b38ac [MRESOLVER-642] Bump org.jboss.forge.roaster:roaster-api (https://redirect.github.com/apache/maven-resolver/issues/618";>#618) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.4...maven-resolver-2.0.5";>compare view Updates `org.apache.maven.resolver:maven-resolver-impl` from 2.0.4 to 2.0.5 Commits https://github.com/apache/maven-resolver/commit/94c49fa2dcec64f5b46ddd93ba5c5e71f8d50cc9";>94c49fa [maven-release-plugin] prepare release maven-resolver-2.0.5 https://github.com/apache/maven-resolver/commit/111210143d142bca48202c3552b333690c542999";>1112101 [MRESOLVER-649] Bump org.jboss.forge.roaster:roaster-jdt (https://redirect.github.com/apache/maven-resolver/issues/624";>#624) https://github.com/apache/maven-resolver/commit/1a984628347bba0f686defce91db16ba18c8875f";>1a98462 [MRESOLVER-648] Bump org.jboss.forge.roaster:roaster-api (https://redirect.github.com/apache/maven-resolver/issues/623";>#623) https://github.com/apache/maven-resolver/commit/708fc751e4a0294313a19350d32ea3ea2ed0ee11";>708fc75 [MRESOLVER-647] Bump org.redisson:redisson from 3.40.1 to 3.40.2 (https://redirect.github.com/apache/maven-resolver/issues/622";>#622) https://github.com/apache/maven-resolver/commit/c4ca019062fd0b60a063309141b2895c32d8425c";>c4ca019 [MRESOLVER-632][MRESOLVER-640] Remove unneded error cases (https://redirect.github.com/apache/maven-resolver/issues/620";>#620) https://github.com/apache/maven-resolver/commit/77e9b91f2cead907615fcdfba208a3213c316901";>77e9b91 [MRESOLVER-645] Remove repeated LRM interaction (https://redirect.github.com/apache/maven-resolver/issues/611";>#611) https://github.com/apache/maven-resolver/commit/6f70e524289b741c1c6c992c99fa44cb07ae7523";>6f70e52 [MRESOLVER-644] Artifact Transformer SPI (https://redirect.github.com/apache/maven-resolver/issues/605";>#605) https://github.com/apache/maven-resolver/commit/9711a38b5340ea92a4c27c15af7bf5dd2cab8bde";>9711a38 Update CI and Maven https://github.com/apache/maven-resolver/commit/709d753a79dd7984446ac4e016ab61e34a5897e4";>709d753 [MRESOLVER-643] Bump org.jboss.forge.roaster:roaster-jdt (https://redirect.github.com/apache/maven-resolver/issues/617";>#617) https://github.com/apache/maven-resolver/commit/b3b38aca5a1d55604f47a792b111bd92ab707938";>b3b38ac [MRESOLVER-642] Bump org.jboss.forge.roaster:roaster-api (https://redirect.github.com/apache/maven-resolver/issues/618";>#618) Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-2.0.4...maven-resolver-2.0.5";>compare view Updates `org.apache.maven.resolver:maven-resolver-spi` from 2.0.4 to 2.0.5 Commits https:
Re: [PR] Prefer Guice injection in sample [maven-resolver]
elharo merged PR #628: URL: https://github.com/apache/maven-resolver/pull/628 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Remove unused JUnit dependency [maven-scm-publish-plugin]
elharo merged PR #50: URL: https://github.com/apache/maven-scm-publish-plugin/pull/50 -- 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] Prefer try with resources [maven-scm-publish-plugin]
elharo merged PR #49: URL: https://github.com/apache/maven-scm-publish-plugin/pull/49 -- 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] [MSITE-1029] Prefer Guice to Plexus [maven-site-plugin]
elharo merged PR #215: URL: https://github.com/apache/maven-site-plugin/pull/215 -- 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
