[jira] [Created] (MDEP-927) dependency:tree excludes parameter does not work
Seva Popov created MDEP-927: --- Summary: dependency:tree excludes parameter does not work Key: MDEP-927 URL: https://issues.apache.org/jira/browse/MDEP-927 Project: Maven Dependency Plugin Issue Type: Bug Components: tree Affects Versions: 3.6.1 Reporter: Seva Popov The dependency:tree excludes parameter does not work in any plugin version available for download. Ex.: mvn org.apache.maven.plugins:maven-dependency-plugin:3.6.1:tree -s ~/.m2/settings.xml -Dexcludes=javax:javaee-api:jar:8.0.1 | grep javax.javaee [INFO] +- javax:javaee-api:jar:8.0.1:provided According to the documentation the dependency should have been excluded - https://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#excludes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SUREFIRE-951) Better handling of file.encoding system property
[
https://issues.apache.org/jira/browse/SUREFIRE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843385#comment-17843385
]
Thorsten Glaser commented on SUREFIRE-951:
--
This breaks JaCoCo. You need:
{code:java}
org.apache.maven.plugins
maven-surefire-plugin
${argLine}
-Dfile.encoding=${project.build.sourceEncoding}
{code}
> Better handling of file.encoding system property
>
>
> Key: SUREFIRE-951
> URL: https://issues.apache.org/jira/browse/SUREFIRE-951
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
>Affects Versions: 2.13
> Environment: Any environment in which the file encoding is distinct
> from ${project.build.sourceEncoding}.
>Reporter: Stephan Schroevers
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.15
>
> Attachments: file-encoding-example.tbz
>
>
> It appears that Surefire doesn't (correctly) set
> {{-Dfile.encoding=$\{project.build.sourceEncoding\}}} prior to running the
> tests. As a result the JVM will derive {{file.encoding}} from the
> environment's file encoding. This affects the return value of
> {{java.nio.charset.Charset#defaultCharset()}}, which reads the
> {{file.encoding}} system property exactly once, and is invoked very early on.
> Concretely this means that the unit tests are unnecessarily platform
> dependent.
> Thus I have two requests:
> # Make {{-Dfile.encoding=$\{project.build.sourceEncoding\}}} the default.
> That is, the following configuration setting should be implied:
> {noformat}
> -Dfile.encoding=${project.build.sourceEncoding}
> {noformat}
> # Extend the method
> {{org.apache.maven.plugin.surefire.SurefireProperties#verifyLegalSystemProperties(org.apache.maven.plugin.logging.Log)}}
> such that is warns about users attempting to set the {{file.encoding}}
> property through the {{systemPropertyVariables}} configuration setting. Like
> with {{java.library.path}}, this does _not_ work.
> I have [attached|^file-encoding-example.tbz] a sample project that
> demonstrates the issue (simply run {{`mvn test`}}). Please have a look at the
> comments I added to the POM. I have tested this sample project only on Linux,
> but a colleague has confirmed that an instance of this issue can also be
> recreated on Windows.
> TIA for looking into this!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [I] Too many open files on Mac OS with JDK 11 and mvnd 0.8.2 [maven-mvnd]
alexandru-prigoreanu commented on issue #710: URL: https://github.com/apache/maven-mvnd/issues/710#issuecomment-2093820946 hey @gnodet ! I am not able to replicate the problem with the following command **mvnd -Dmvnd.jvmArgs=-XX:-MaxFDLimit clean install** and the following configuration * mvnd 1.0-m8 * mac os x 14.4.1 maybe this can be rejected/closed now. thank you very much! -- 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-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-8115: - Component/s: Dependencies > Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Apache commons, Classword -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-555) Existence check should lax the repository update policy
[
https://issues.apache.org/jira/browse/MRESOLVER-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843367#comment-17843367
]
Tamas Cservenak commented on MRESOLVER-555:
---
This is wrong. This cannot happen in all cases...
Simply put, Resolver has no notion of "wandering artifacts", but it does try
hard to enforce error policy ("cache 404").
I think the proper solution would be to be able to assign
{{org.eclipse.aether.resolution.ResolutionErrorPolicy}} not only session-wide,
but to a RemoteRepository (code change in Resolver but also code change in
Maven). As then, solution would be:
* super POM states "do not cache 404 for Central", but
* do cache as today (per session level)
Also with this exposed, any organization could set/configure whatever setup
they have, like "by the book" setup of staging suite that ends up in releases
repo...
Ideas welcome.
> Existence check should lax the repository update policy
> ---
>
> Key: MRESOLVER-555
> URL: https://issues.apache.org/jira/browse/MRESOLVER-555
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 2.0.0, 2.0.0-beta-1
>
>
> Maybe only when update policy is "never".
> Order of events:
> * attempt a build with not-yet-released-artifact (for example resolver in
> maven)
> * as it is not in central, build will fail, and central URL will be "cached"
> as 404 for given artifact
> * fix, rinse, repeat, add staging repository, rebuild
> * build will pass ok, as staging repository will have the artifact, it is
> cached to local repository (from staging repository)
> * later, staging repository is dropped, release promoted to central.
> * rebuild: here, Resolver will nag that "artifact is present but not
> available", which is true: it was cached from staging repository
> * it will go try to see is it available in central (existence check), but:
> central has 404 cached (see step 1), and in this case update policy is being
> obeyed, that is "never"
> * due "never" update policy existence check will fail, and build will fail
> Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is
> "never" maybe? As from this situation only escape route is build with -U that
> will reset local repository state and build will pass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MRESOLVER-555) Existence check should lax the repository update policy
[ https://issues.apache.org/jira/browse/MRESOLVER-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-555: -- Description: Maybe only when update policy is "never". Order of events: * attempt a build with not-yet-released-artifact (for example resolver in maven) * as it is not in central, build will fail, and central URL will be "cached" as 404 * fix, rinse, repeat, add staging repository, rebuild * build will pass ok, as staging repository will have the artifact, it is cached to local repository (from staging repository) * later, staging repository is dropped, release promoted to central. * rebuild: here, Resolver will nag that "artifact is present but not available", which is true: it was cached from staging repository * it will go try to see is it available in central (existence check), but: central has 404 cached (see step 1), and in this case update policy is being obeyed, that is "never" * due "never" update policy existence check will fail, and build will fail Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is "never" maybe? As from this situation only escape route is build with -U that will reset local repository state and build will pass. was: Maybe only when update policy is "never". Order of events: * attempt a build with not-yet-released-artifact (for example resolver in maven) * as it is not in central, build will fail, and central URL will be "cached" as 404 * fix, rinse, repeat, add staging repository, rebuild * build will pass ok, as staging repository will have the artifact, it is cached to local repository (from staging repository) * later, staging repository is dropped, release promoted to central. * rebuild: here, Resolver will nag that "artifact is present but not available", which is true: it was cached from staging repository * it will go try to see is it available in central (existence check), but: central has 404 cached (see step 1), and in this case update policy is being obeyed, that is "never" * due "never" update policy existence check will fail, and build will fail > Existence check should lax the repository update policy > --- > > Key: MRESOLVER-555 > URL: https://issues.apache.org/jira/browse/MRESOLVER-555 > Project: Maven Resolver > Issue Type: Bug > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > Maybe only when update policy is "never". > Order of events: > * attempt a build with not-yet-released-artifact (for example resolver in > maven) > * as it is not in central, build will fail, and central URL will be "cached" > as 404 > * fix, rinse, repeat, add staging repository, rebuild > * build will pass ok, as staging repository will have the artifact, it is > cached to local repository (from staging repository) > * later, staging repository is dropped, release promoted to central. > * rebuild: here, Resolver will nag that "artifact is present but not > available", which is true: it was cached from staging repository > * it will go try to see is it available in central (existence check), but: > central has 404 cached (see step 1), and in this case update policy is being > obeyed, that is "never" > * due "never" update policy existence check will fail, and build will fail > Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is > "never" maybe? As from this situation only escape route is build with -U that > will reset local repository state and build will pass. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MRESOLVER-555) Existence check should lax the repository update policy
[ https://issues.apache.org/jira/browse/MRESOLVER-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-555: -- Description: Maybe only when update policy is "never". Order of events: * attempt a build with not-yet-released-artifact (for example resolver in maven) * as it is not in central, build will fail, and central URL will be "cached" as 404 for given artifact * fix, rinse, repeat, add staging repository, rebuild * build will pass ok, as staging repository will have the artifact, it is cached to local repository (from staging repository) * later, staging repository is dropped, release promoted to central. * rebuild: here, Resolver will nag that "artifact is present but not available", which is true: it was cached from staging repository * it will go try to see is it available in central (existence check), but: central has 404 cached (see step 1), and in this case update policy is being obeyed, that is "never" * due "never" update policy existence check will fail, and build will fail Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is "never" maybe? As from this situation only escape route is build with -U that will reset local repository state and build will pass. was: Maybe only when update policy is "never". Order of events: * attempt a build with not-yet-released-artifact (for example resolver in maven) * as it is not in central, build will fail, and central URL will be "cached" as 404 * fix, rinse, repeat, add staging repository, rebuild * build will pass ok, as staging repository will have the artifact, it is cached to local repository (from staging repository) * later, staging repository is dropped, release promoted to central. * rebuild: here, Resolver will nag that "artifact is present but not available", which is true: it was cached from staging repository * it will go try to see is it available in central (existence check), but: central has 404 cached (see step 1), and in this case update policy is being obeyed, that is "never" * due "never" update policy existence check will fail, and build will fail Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is "never" maybe? As from this situation only escape route is build with -U that will reset local repository state and build will pass. > Existence check should lax the repository update policy > --- > > Key: MRESOLVER-555 > URL: https://issues.apache.org/jira/browse/MRESOLVER-555 > Project: Maven Resolver > Issue Type: Bug > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0, 2.0.0-beta-1 > > > Maybe only when update policy is "never". > Order of events: > * attempt a build with not-yet-released-artifact (for example resolver in > maven) > * as it is not in central, build will fail, and central URL will be "cached" > as 404 for given artifact > * fix, rinse, repeat, add staging repository, rebuild > * build will pass ok, as staging repository will have the artifact, it is > cached to local repository (from staging repository) > * later, staging repository is dropped, release promoted to central. > * rebuild: here, Resolver will nag that "artifact is present but not > available", which is true: it was cached from staging repository > * it will go try to see is it available in central (existence check), but: > central has 404 cached (see step 1), and in this case update policy is being > obeyed, that is "never" > * due "never" update policy existence check will fail, and build will fail > Now, IMO, for "existence check" Resolver should lax the policy ONLY if it is > "never" maybe? As from this situation only escape route is build with -U that > will reset local repository state and build will pass. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8076) when jar in local repository from other repository id, should not reject but check if it is also available in current repository id context
[
https://issues.apache.org/jira/browse/MNG-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843360#comment-17843360
]
Tamas Cservenak commented on MNG-8076:
--
created https://issues.apache.org/jira/browse/MRESOLVER-555
> when jar in local repository from other repository id, should not reject but
> check if it is also available in current repository id context
> ---
>
> Key: MNG-8076
> URL: https://issues.apache.org/jira/browse/MNG-8076
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.6
>Reporter: Herve Boutemy
>Priority: Major
>
> precise context: Reproducible Central
> https://github.com/jvm-repo-rebuild/reproducible-central
> in the past, I rebuilt maven-shade-plugin 3.5.2 during the vote, which
> downloaded the reference jar in a staging remote repository with "reference"
> id (that's part of the artifact:compare logic in Apache staging: see
> https://github.com/jvm-repo-rebuild/reproducible-central/issues/140 for
> details on this recent Reproducible Central feature)
> When I'm trying to rebuild a project that uses this maven-shade-plugin 3.5.2
> release, I get:
> {noformat}
> [INFO] Artifact org.apache.maven.plugins:maven-shade-plugin:pom:3.5.2 is
> present in the local repository, but cached from a remote repository ID that
> is unavailable in current build context, verifying that is downloadable from
> [central (https://repo.maven.apache.org/maven2, default, releases)]
> {noformat}
> looking in the local repository, I get
> {noformat}
> cat
> ~/.m2/repository/org/apache/maven/plugins/maven-shade-plugin/3.5.2/_remote.repositories
> #NOTE: This is a Maven Resolver internal implementation file, its format can
> be changed without prior notice.
> #Sun Feb 18 15:03:27 UTC 2024
> maven-shade-plugin-3.5.2-sources.jar>reference=
> maven-shade-plugin-3.5.2.pom>reference=
> maven-shade-plugin-3.5.2.jar>reference=
> maven-shade-plugin-3.5.2-source-release.zip>reference=
> maven-shade-plugin-3.5.2-cyclonedx.xml>reference=
> maven-shade-plugin-3.5.2-cyclonedx.json>reference=
> {noformat}
> the fact that all these artifacts were initially downloaded through
> "reference" repository id does not mean that they are not *also* available
> with the "central" id
> as a precise workaround, i did not delete the _remote.repositories file but
> replaced reference with central and it works as expected. The opposite update
> can restore the failing behaviour...
> for now, I know that by rebuilding releases from Apache staging area, I'm
> polluting my local repository :/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MRESOLVER-555) Existence check should lax the repository update policy
Tamas Cservenak created MRESOLVER-555: - Summary: Existence check should lax the repository update policy Key: MRESOLVER-555 URL: https://issues.apache.org/jira/browse/MRESOLVER-555 Project: Maven Resolver Issue Type: Bug Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0, 2.0.0-beta-1 Maybe only when update policy is "never". Order of events: * attempt a build with not-yet-released-artifact (for example resolver in maven) * as it is not in central, build will fail, and central URL will be "cached" as 404 * fix, rinse, repeat, add staging repository, rebuild * build will pass ok, as staging repository will have the artifact, it is cached to local repository (from staging repository) * later, staging repository is dropped, release promoted to central. * rebuild: here, Resolver will nag that "artifact is present but not available", which is true: it was cached from staging repository * it will go try to see is it available in central (existence check), but: central has 404 cached (see step 1), and in this case update policy is being obeyed, that is "never" * due "never" update policy existence check will fail, and build will fail -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-8115: -- Description: Apache commons, Classword (was: Plexus Utils 4 Guice 6 Apache commons) > Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Apache commons, Classword -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843354#comment-17843354 ] ASF GitHub Bot commented on MNG-8115: - slachiewicz commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093729196 I've prepared a smaller set of updates, mainly Apache Commons and Classword. Plexus Utils - leave version as is, only used variable from parent. No Guava, Guice or plexus annotations updates. > Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
slachiewicz commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093729196 I've prepared a smaller set of updates, mainly Apache Commons and Classword. Plexus Utils - leave version as is, only used variable from parent. No Guava, Guice or plexus annotations updates. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
slachiewicz commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589701560 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 +1.27 +6.0.0 +33.2.0-jre +1.0.2 Review Comment: I'll drop Guava update, not sure about the impact. -- 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-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843353#comment-17843353 ] ASF GitHub Bot commented on MNG-8115: - slachiewicz commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589701560 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MSHARED-1389) Refresh download page
Slawomir Jaranowski created MSHARED-1389: Summary: Refresh download page Key: MSHARED-1389 URL: https://issues.apache.org/jira/browse/MSHARED-1389 Project: Maven Shared Components Issue Type: Task Components: maven-invoker Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-invoker-next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843348#comment-17843348 ] ASF GitHub Bot commented on MNG-8115: - slachiewicz commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589686598 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
slachiewicz commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589686598 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 Review Comment: I've updated qdox for 2.2.0 release. Also, all Plexus annotations are marked as Deprecated - ie more visible. Not sure if 3.9 would be beneficial as looks like we don't have plans to do any Plexus -> jsr330 migration. -- 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-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843344#comment-17843344 ] ASF GitHub Bot commented on MNG-8115: - cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589670907 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589670907 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 Review Comment: unsure, where is this used at all? I'd leave it as there was some issue with qdox, that am unsure was fixed or not -- 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-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843341#comment-17843341 ] ASF GitHub Bot commented on MNG-8115: - cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669971 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669971 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 +1.27 +6.0.0 +33.2.0-jre +1.0.2 3.5.3 2.0 2.0 1.3 1.9.20 1.7.36 -2.9.1 +2.10.0 Review Comment: only if does not need code change and builds ok ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 +1.27 Review Comment: +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
[jira] [Commented] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843340#comment-17843340 ] ASF GitHub Bot commented on MNG-8115: - cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669421 ## pom.xml: ## @@ -352,7 +340,7 @@ under the License. org.fusesource.jansi jansi -2.4.0 +2.4.1 Review Comment: +1 ## pom.xml: ## @@ -340,7 +328,7 @@ under the License. org.apache.maven.shared maven-shared-utils -3.3.4 +3.4.2 Review Comment: +1 > Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669421 ## pom.xml: ## @@ -352,7 +340,7 @@ under the License. org.fusesource.jansi jansi -2.4.0 +2.4.1 Review Comment: +1 ## pom.xml: ## @@ -340,7 +328,7 @@ under the License. org.apache.maven.shared maven-shared-utils -3.3.4 +3.4.2 Review Comment: +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
[jira] [Commented] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843336#comment-17843336 ] ASF GitHub Bot commented on MNG-8115: - cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589668577 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843339#comment-17843339 ] ASF GitHub Bot commented on MNG-8115: - cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669176 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843338#comment-17843338 ] ASF GitHub Bot commented on MNG-8115: - cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669015 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669176 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 +1.27 +6.0.0 +33.2.0-jre +1.0.2 Review Comment: Goes with guava, so OK -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589669015 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 +1.27 +6.0.0 +33.2.0-jre Review Comment: But, this one should be ok (Maven does not use, it is runtime dep of guice) -- just to get rid of red flags -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on code in PR #1496: URL: https://github.com/apache/maven/pull/1496#discussion_r1589668577 ## pom.xml: ## @@ -125,31 +125,25 @@ under the License. 8 -3.5.4 - -0.9.0.M2 -2.7.0 -1.5.0 -2.11.0 -3.12.0 +2.8.0 +1.7.0 +2.16.1 +3.14.0 4.13.2 2.2 4.11.0 - -2.1.0 -1.26 - -3.5.1 -5.1.0 -32.0.1-jre -1.0.1 +2.2.0 +1.27 +6.0.0 Review Comment: Nope -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093667845 Yup, definitely nothing p-u 4. Let me comment in PR what I think is OK -- 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-8115) Upgrade dependencies
[ https://issues.apache.org/jira/browse/MNG-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1784#comment-1784 ] ASF GitHub Bot commented on MNG-8115: - slachiewicz commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093665241 So plexus-utils 4 we also shouldn't have? > Upgrade dependencies > > > Key: MNG-8115 > URL: https://issues.apache.org/jira/browse/MNG-8115 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.9.7, 3.9.x-candidate > > > Plexus Utils 4 > Guice 6 > Apache commons -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
slachiewicz commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093665241 So plexus-utils 4 we also shouldn't have? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
slachiewicz commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093662276 We are using Guice 6 in tests and it just works. Same with Maven 4. Agree that for patch release this may be too much -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.resolver.version from 1.9.18 to 1.9.20 [maven-mvnd]
dependabot[bot] closed pull request #983: Bump maven.resolver.version from 1.9.18 to 1.9.20 URL: https://github.com/apache/maven-mvnd/pull/983 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.resolver.version from 1.9.18 to 1.9.20 [maven-mvnd]
dependabot[bot] commented on PR #983: URL: https://github.com/apache/maven-mvnd/pull/983#issuecomment-2093659433 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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] Align maven resolver to 2.0.0-alpha-11 [maven-mvnd]
gnodet merged PR #984: URL: https://github.com/apache/maven-mvnd/pull/984 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093655778 Hm, maybe a small subset of updates in pom.xml only... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [MNG-8115] Upgrade dependencies [maven]
cstamas commented on PR #1496: URL: https://github.com/apache/maven/pull/1496#issuecomment-2093653031 @slachiewicz I'd pass on this (in fact in whole 3.9.x line), would not budge plexus-utils, as Guillaume mention neither guice... for patch release this is simply put "too much" IMHO -- 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] (MSHARED-1382) Maven-invoker: support '--no-snapshot-updates'
[
https://issues.apache.org/jira/browse/MSHARED-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843325#comment-17843325
]
ASF GitHub Bot commented on MSHARED-1382:
-
slawekjaranowski merged PR #74:
URL: https://github.com/apache/maven-invoker/pull/74
> Maven-invoker: support '--no-snapshot-updates'
> --
>
> Key: MSHARED-1382
> URL: https://issues.apache.org/jira/browse/MSHARED-1382
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-invoker
>Affects Versions: maven-invoker-3.2.0
>Reporter: Leonid Rozenblyum
>Priority: Major
>
> Let's add support for *{{--no-snapshot-updates}}* in
> *{{org.apache.maven.shared.invoker.InvocationRequest}}*
>
> Currently *{{InvocationRequest}}* supports just the *{{-U}}* *mvn* option
> which is not enough: it's possible to force the snapshots update or keep
> default maven policy on this.
>
> But it's not possible to prevent snapshots updates which is highly desired
> under some circumstances (e.g. for CI reproducibility).
>
> NOTE: I may contribute a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1382] support a possibility to disable snapshots update. [maven-invoker]
slawekjaranowski merged PR #74: URL: https://github.com/apache/maven-invoker/pull/74 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.resolver.version from 1.9.18 to 1.9.19 [maven-mvnd]
dependabot[bot] closed pull request #958: Bump maven.resolver.version from 1.9.18 to 1.9.19 URL: https://github.com/apache/maven-mvnd/pull/958 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.resolver.version from 1.9.18 to 1.9.19 [maven-mvnd]
dependabot[bot] commented on PR #958: URL: https://github.com/apache/maven-mvnd/pull/958#issuecomment-2093614964 Superseded by #983. -- 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 maven.resolver.version from 1.9.18 to 1.9.20 [maven-mvnd]
dependabot[bot] opened a new pull request, #983: URL: https://github.com/apache/maven-mvnd/pull/983 Bumps `maven.resolver.version` from 1.9.18 to 1.9.20. Updates `org.apache.maven.resolver:maven-resolver-api` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-api's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent POM 42 (https://redirect.github.com/apache/maven-resolver/issues/484;>#484) https://github.com/apache/maven-resolver/commit/4f16d5ecd94f85e6e7d793e6b6b82f20c9afbf56;>4f16d5e [MRESOLVER-547] Just use setVersion (https://redirect.github.com/apache/maven-resolver/issues/483;>#483) https://github.com/apache/maven-resolver/commit/c1b24c699621930f4eb77721400f2f6c46930626;>c1b24c6 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-resolver/commit/c1b03574961fd2daa7a678bb3fbf9f0779afee56;>c1b0357 [maven-release-plugin] prepare release maven-resolver-1.9.19 https://github.com/apache/maven-resolver/commit/adadd42d1642f39bafedb2ddd619b044fecb12b0;>adadd42 [MRESOLVER-536] Do not belly up if FS does not support setting mtime (https://redirect.github.com/apache/maven-resolver/issues/469;>#469) https://github.com/apache/maven-resolver/commit/31df8a3dc503895172d277de56b1c4a53da0a27c;>31df8a3 [1.9.x] Update dependencies (https://redirect.github.com/apache/maven-resolver/issues/462;>#462) https://github.com/apache/maven-resolver/commit/b225076e5d5b2fe3f166a4018802ac94b7cc94f7;>b225076 [MRESOLVER-522] Improve congested file locks behaviour (https://redirect.github.com/apache/maven-resolver/issues/455;>#455) (https://redirect.github.com/apache/maven-resolver/issues/461;>#461) https://github.com/apache/maven-resolver/commit/fc969c2570041bb72c3f0141ff4957e8754f365c;>fc969c2 [1.9.x][MRESOLVER-483] Fix path concatenation logic (https://redirect.github.com/apache/maven-resolver/issues/420;>#420) https://github.com/apache/maven-resolver/commit/a3e620d6d2ab6ca58d42d264347341b31da00dde;>a3e620d Use one Maven in CI Additional commits viewable in https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.18...maven-resolver-1.9.20;>compare view Updates `org.apache.maven.resolver:maven-resolver-impl` from 1.9.18 to 1.9.20 Release notes Sourced from https://github.com/apache/maven-resolver/releases;>org.apache.maven.resolver:maven-resolver-impl's releases. 1.9.20 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12354578;>Release Notes - Maven Resolver - Version 1.9.20 What's Changed [MRESOLVER-547] Just use setVersion by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/483;>apache/maven-resolver#483 [MRESOLVER-549] Parent POM 42 by https://github.com/cstamas;>@cstamas in https://redirect.github.com/apache/maven-resolver/pull/484;>apache/maven-resolver#484 Full Changelog: https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20;>https://github.com/apache/maven-resolver/compare/maven-resolver-1.9.19...maven-resolver-1.9.20 1.9.19 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628version=12353946;>Release Notes - Maven Resolver - Version 1.9.19 ... (truncated) Commits https://github.com/apache/maven-resolver/commit/f5fbc245e64091a41ba0926a6958b98bf0b29eb3;>f5fbc24 [maven-release-plugin] prepare release maven-resolver-1.9.20 https://github.com/apache/maven-resolver/commit/446009d7073014a7d418a4b9637664a2f6d05c82;>446009d [MRESOLVER-549][MRESOLVER-550][MRESOLVER-551] Parent
Re: [PR] Bump maven.version from 4.0.0-alpha-8 to 4.0.0-alpha-13 [maven-mvnd]
dependabot[bot] closed pull request #976: Bump maven.version from 4.0.0-alpha-8 to 4.0.0-alpha-13 URL: https://github.com/apache/maven-mvnd/pull/976 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump maven.version from 4.0.0-alpha-8 to 4.0.0-alpha-13 [maven-mvnd]
dependabot[bot] commented on PR #976: URL: https://github.com/apache/maven-mvnd/pull/976#issuecomment-2093614544 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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 jline.version from 3.25.1 to 3.26.1 [maven-mvnd]
dependabot[bot] closed pull request #977: Bump jline.version from 3.25.1 to 3.26.1 URL: https://github.com/apache/maven-mvnd/pull/977 -- 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 jline.version from 3.25.1 to 3.26.1 [maven-mvnd]
dependabot[bot] commented on PR #977: URL: https://github.com/apache/maven-mvnd/pull/977#issuecomment-2093614427 Looks like these dependencies are up-to-date now, so this is no longer needed. -- 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] Upgrade to Maven 4.0.0-beta-1 [maven-mvnd]
gnodet merged PR #974: URL: https://github.com/apache/maven-mvnd/pull/974 -- 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] (MSHARED-1338) Update groovy to 4.0.16
[ https://issues.apache.org/jira/browse/MSHARED-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed MSHARED-1338. Fix Version/s: (was: waiting-for-feedback) Resolution: Invalid > Update groovy to 4.0.16 > --- > > Key: MSHARED-1338 > URL: https://issues.apache.org/jira/browse/MSHARED-1338 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-invoker >Reporter: Jorge Solórzano >Priority: Major > Labels: up-for-grabs > > Update Groovy 4.0.16 to support running on JDK 22. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8073) Generated XSD files needs to have ASL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843319#comment-17843319 ] ASF GitHub Bot commented on MNG-8073: - cstamas merged PR #1499: URL: https://github.com/apache/maven/pull/1499 > Generated XSD files needs to have ASL2.0 license headers > > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8041) Maven Core bug regarding resolution scopes for Mojos
[
https://issues.apache.org/jira/browse/MNG-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8041:
-
Fix Version/s: 4.0.0-beta-2
(was: 4.0.0-beta-1)
> Maven Core bug regarding resolution scopes for Mojos
>
>
> Key: MNG-8041
> URL: https://issues.apache.org/jira/browse/MNG-8041
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Reporter: Tamas Cservenak
>Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-2
>
>
> This bug affects all released Maven versions.
> Reproducer: [https://github.com/cstamas/MNG-8041]
> Description of the bug: when a Mojo requires Core to collect/resolve given
> ResolutionScope, Maven Core does it wrong. Problem is how
> LifecycleDependencyResolver and DefaultProjectDependenciesResolver colaborate
> plus, how Resolver works. LDR constructs the Resolver filters properly, then
> it calls into DPDR, that performs collection. To achieve that, DPDR *blindly*
> adds all the POM dependencies to Collect request (which is graph root). But
> this is wrong, as this should happen with considering requested (to be
> included or to be excluded) scopes. Next what happens, that when collect
> request is processed by Resolver, it will contain nodes from unwanted scopes
> (as Maven Core blindly added all of them from POM). Just as detail: if
> Resolver would be asked to create root, it would NOT add these in the first
> place. Due these present, conflict resolver may possibly eliminate other
> nodes (as POM ones "always wins", are the closest to graph root. Finally,
> these winners may be eliminated in subsequent step, for example due scope
> filtering. This results in incomplete resolution scope.
> Example: let's consider example where Mojo asks for "runtime" resolution
> scope. To serve this, Maven will add ALL dependencies present in POM to
> collect request (even those in scopes to be omitted, like "test" scoped
> ones), and will perform "collect" using Resolver. When Resolver returns the
> graph, it will contain nodes (as 1st level was populated by Maven) that MAY
> be contained in deeper nodes of non-test scoped ones (the guice+guava
> example). Next, "conflict resolution" happens, and naturally all the "test"
> scoped 1st level dependencies will "win", rendering removal of others.
> Finally, due "runtime" requested resolution scope, the "test" scoped
> dependencies are (rightfully) filtered out. {*}This obviously leads to
> incomplete runtime build path{*}.
> Or in other words, Maven is wrong here: it adds 1st level dependencies to
> CollectRequest that should not be there in the first place (in example above,
> the "test" scoped ones), that will cause that Resolver "collect" step build a
> graph that has "unwanted" scoped nodes closer to root than actually needed
> runtime dependencies (remember: test nodes will be not affected by filter, as
> they are already present, added by Maven, and test node children are
> collected also as "runtime", just to have "test" scope inherited later in the
> process, hence all the children of "test" node will end up in "test" scope,
> despite "exclude test" is present!), this will cause that in dependency
> conflict resolution step, they will kick out all the rightful runtime
> dependencies, and finally, all these winners are removed due scope filter.
> Implication of this bug is following important fact: the project "runtime"
> resolution scope (as when asked by Mojo) and project "runtime" resolution
> scope (as when used as a dependency on some downstream project) {*}were not
> the same{*}!
> Effects of this bug are explained in "Important Consequences" section of this
> page
> [https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/common-misconceptions.html#important-consequences]
> (that is wrongly written: all that is a consequence of this bug). Also, have
> to note, that when this bug get addressed, it will NOT render "workarounds"
> broken (ie. introduction of another module just to package "runtime"
> classpath using m-assembly-p or alike plugins), just "obsolete", as packaging
> of runtime dependencies will become possible in-situ (in the same module of
> the project).
> Exercises: check out reproducer and execute these commands:
> * {{mvn dependency:tree}} => OK, it shows "dependencies included from all
> scopes" (this is equiv to "test" build scope), guava is in test scope
> * {{mvn dependency:tree -Dscope=runtime}} => NOT OK, it will show effect of
> this bug, guava is missing from runtime resolution scope
> * install the reproducer project into local repository, and create another
> project (or use {{downstream/pom.xml}} from reproducer) that uses reproducer
> project as dependency (only one, no
[jira] [Closed] (MNG-8073) Generated XSD files needs to have ASL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-8073. Resolution: Fixed > Generated XSD files needs to have ASL2.0 license headers > > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8073] Adding ASL2 header to XSD files [maven]
cstamas merged PR #1499: URL: https://github.com/apache/maven/pull/1499 -- 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-8073) Generated XSD files needs to have ASL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843317#comment-17843317 ] ASF GitHub Bot commented on MNG-8073: - slawekjaranowski commented on code in PR #1499: URL: https://github.com/apache/maven/pull/1499#discussion_r1589627997 ## pom.xml: ## @@ -664,6 +664,25 @@ under the License. org.codehaus.modello modello-maven-plugin + 2.4.0 Review Comment: version should be removed with next parent ... we can add todo > Generated XSD files needs to have ASL2.0 license headers > > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8073] Adding ASL2 header to XSD files [maven]
slawekjaranowski commented on code in PR #1499: URL: https://github.com/apache/maven/pull/1499#discussion_r1589627997 ## pom.xml: ## @@ -664,6 +664,25 @@ under the License. org.codehaus.modello modello-maven-plugin + 2.4.0 Review Comment: version should be removed with next parent ... we can add todo -- 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-8073) Generated XSD files needs to have ASL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843311#comment-17843311 ] ASF GitHub Bot commented on MNG-8073: - cstamas commented on PR #1499: URL: https://github.com/apache/maven/pull/1499#issuecomment-2093565686  > Generated XSD files needs to have ASL2.0 license headers > > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-8073] Adding ASL2 header to XSD files [maven]
cstamas commented on PR #1499: URL: https://github.com/apache/maven/pull/1499#issuecomment-2093565686  -- 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] [MSHARED-1388] Bump org.apache.maven.shared:maven-shared-components from 41 to 42 [maven-invoker]
slawekjaranowski merged PR #73: URL: https://github.com/apache/maven-invoker/pull/73 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-8073) Generated XSD files needs to have ASL2.0 license headers
[ https://issues.apache.org/jira/browse/MNG-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843308#comment-17843308 ] ASF GitHub Bot commented on MNG-8073: - cstamas opened a new pull request, #1499: URL: https://github.com/apache/maven/pull/1499 Using latest modello release and putting license into POM. --- https://issues.apache.org/jira/browse/MNG-8073 > Generated XSD files needs to have ASL2.0 license headers > > > Key: MNG-8073 > URL: https://issues.apache.org/jira/browse/MNG-8073 > Project: Maven > Issue Type: Task >Affects Versions: 4.0.0-alpha-13 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0, 4.0.0-beta-1 > > > Currently we were adding them manually during release process. > Maybe also collecting them to single place would be handy, instead to "hunt > them down" in checkout post release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-8076) when jar in local repository from other repository id, should not reject but check if it is also available in current repository id context
[
https://issues.apache.org/jira/browse/MNG-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843307#comment-17843307
]
Tamas Cservenak commented on MNG-8076:
--
Oh, nvm: the problem is "never" update interval of Central, so it seems in this
case Resolver should be smarter?
> when jar in local repository from other repository id, should not reject but
> check if it is also available in current repository id context
> ---
>
> Key: MNG-8076
> URL: https://issues.apache.org/jira/browse/MNG-8076
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.6
>Reporter: Herve Boutemy
>Priority: Major
>
> precise context: Reproducible Central
> https://github.com/jvm-repo-rebuild/reproducible-central
> in the past, I rebuilt maven-shade-plugin 3.5.2 during the vote, which
> downloaded the reference jar in a staging remote repository with "reference"
> id (that's part of the artifact:compare logic in Apache staging: see
> https://github.com/jvm-repo-rebuild/reproducible-central/issues/140 for
> details on this recent Reproducible Central feature)
> When I'm trying to rebuild a project that uses this maven-shade-plugin 3.5.2
> release, I get:
> {noformat}
> [INFO] Artifact org.apache.maven.plugins:maven-shade-plugin:pom:3.5.2 is
> present in the local repository, but cached from a remote repository ID that
> is unavailable in current build context, verifying that is downloadable from
> [central (https://repo.maven.apache.org/maven2, default, releases)]
> {noformat}
> looking in the local repository, I get
> {noformat}
> cat
> ~/.m2/repository/org/apache/maven/plugins/maven-shade-plugin/3.5.2/_remote.repositories
> #NOTE: This is a Maven Resolver internal implementation file, its format can
> be changed without prior notice.
> #Sun Feb 18 15:03:27 UTC 2024
> maven-shade-plugin-3.5.2-sources.jar>reference=
> maven-shade-plugin-3.5.2.pom>reference=
> maven-shade-plugin-3.5.2.jar>reference=
> maven-shade-plugin-3.5.2-source-release.zip>reference=
> maven-shade-plugin-3.5.2-cyclonedx.xml>reference=
> maven-shade-plugin-3.5.2-cyclonedx.json>reference=
> {noformat}
> the fact that all these artifacts were initially downloaded through
> "reference" repository id does not mean that they are not *also* available
> with the "central" id
> as a precise workaround, i did not delete the _remote.repositories file but
> replaced reference with central and it works as expected. The opposite update
> can restore the failing behaviour...
> for now, I know that by rebuilding releases from Apache staging area, I'm
> polluting my local repository :/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8076) when jar in local repository from other repository id, should not reject but check if it is also available in current repository id context
[
https://issues.apache.org/jira/browse/MNG-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843306#comment-17843306
]
Tamas Cservenak commented on MNG-8076:
--
Something is fishy... here what happened (maybe helps to reproduce): Maven
master had merged a PR with Resolver2 alpha-11 that added staging repo (as
Resolver vote was ongoing). This state of master was built on my laptop, so
alpha-11 was present in my local repo. Fast forward a week, git update and
tried to build again. Since then Resolver vote passed, staging repo is gone,
and Resolver alpha-11 is in central. So I got message from Maven "alpha-11 is
present in local repo", but "from different repo that is not available in the
build". The next message said it "will check availability" from central (it is
available), but failed. The only thing helped was -U.
> when jar in local repository from other repository id, should not reject but
> check if it is also available in current repository id context
> ---
>
> Key: MNG-8076
> URL: https://issues.apache.org/jira/browse/MNG-8076
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.9.6
>Reporter: Herve Boutemy
>Priority: Major
>
> precise context: Reproducible Central
> https://github.com/jvm-repo-rebuild/reproducible-central
> in the past, I rebuilt maven-shade-plugin 3.5.2 during the vote, which
> downloaded the reference jar in a staging remote repository with "reference"
> id (that's part of the artifact:compare logic in Apache staging: see
> https://github.com/jvm-repo-rebuild/reproducible-central/issues/140 for
> details on this recent Reproducible Central feature)
> When I'm trying to rebuild a project that uses this maven-shade-plugin 3.5.2
> release, I get:
> {noformat}
> [INFO] Artifact org.apache.maven.plugins:maven-shade-plugin:pom:3.5.2 is
> present in the local repository, but cached from a remote repository ID that
> is unavailable in current build context, verifying that is downloadable from
> [central (https://repo.maven.apache.org/maven2, default, releases)]
> {noformat}
> looking in the local repository, I get
> {noformat}
> cat
> ~/.m2/repository/org/apache/maven/plugins/maven-shade-plugin/3.5.2/_remote.repositories
> #NOTE: This is a Maven Resolver internal implementation file, its format can
> be changed without prior notice.
> #Sun Feb 18 15:03:27 UTC 2024
> maven-shade-plugin-3.5.2-sources.jar>reference=
> maven-shade-plugin-3.5.2.pom>reference=
> maven-shade-plugin-3.5.2.jar>reference=
> maven-shade-plugin-3.5.2-source-release.zip>reference=
> maven-shade-plugin-3.5.2-cyclonedx.xml>reference=
> maven-shade-plugin-3.5.2-cyclonedx.json>reference=
> {noformat}
> the fact that all these artifacts were initially downloaded through
> "reference" repository id does not mean that they are not *also* available
> with the "central" id
> as a precise workaround, i did not delete the _remote.repositories file but
> replaced reference with central and it works as expected. The opposite update
> can restore the failing behaviour...
> for now, I know that by rebuilding releases from Apache staging area, I'm
> polluting my local repository :/
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MSHARED-1388) Upgrade Parent to 42
Slawomir Jaranowski created MSHARED-1388: Summary: Upgrade Parent to 42 Key: MSHARED-1388 URL: https://issues.apache.org/jira/browse/MSHARED-1388 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-invoker Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: maven-invoker-next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSHARED-1338) Update groovy to 4.0.16
[ https://issues.apache.org/jira/browse/MSHARED-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated MSHARED-1338: - Fix Version/s: waiting-for-feedback > Update groovy to 4.0.16 > --- > > Key: MSHARED-1338 > URL: https://issues.apache.org/jira/browse/MSHARED-1338 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-invoker >Reporter: Jorge Solórzano >Priority: Major > Labels: up-for-grabs > Fix For: waiting-for-feedback > > > Update Groovy 4.0.16 to support running on JDK 22. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843291#comment-17843291 ] ASF GitHub Bot commented on MEJB-137: - slachiewicz merged PR #31: URL: https://github.com/apache/maven-ejb-plugin/pull/31 > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MEJB-137. - Resolution: Fixed > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MEJB-137] Require Maven 3.6.3+ [maven-ejb-plugin]
slachiewicz merged PR #31: URL: https://github.com/apache/maven-ejb-plugin/pull/31 -- 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] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MEJB-138. - Resolution: Fixed > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843289#comment-17843289 ] ASF GitHub Bot commented on MEJB-138: - slachiewicz merged PR #32: URL: https://github.com/apache/maven-ejb-plugin/pull/32 > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MEJB-138] Update parent pom to 42 and dependencies [maven-ejb-plugin]
slachiewicz merged PR #32: URL: https://github.com/apache/maven-ejb-plugin/pull/32 -- 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] (MEJB-112) JDK 9 WARNING in Integration Test
[
https://issues.apache.org/jira/browse/MEJB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MEJB-112.
-
Resolution: Fixed
> JDK 9 WARNING in Integration Test
> -
>
> Key: MEJB-112
> URL: https://issues.apache.org/jira/browse/MEJB-112
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.2.2
>
>
> Currently running on JDK 9 (EA+181) give the following warning during running
> via {{mvn -Prun-its clean verify}}:
> {code}
> [INFO] ..SUCCESS (3.8 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass$3$1
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy/2.0.1/groovy-2.0.1.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass$3$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] ..SUCCESS (4.1 s)
> [INFO] Building: reactor/pom.xml
> [INFO] run script verify.bsh
> [INFO] ..SUCCESS (3.4 s)
> {code}
> Upgrading to maven-invoker-plugin:3.0.1:
> {code}
> [INFO] run post-build script verify.bsh
> [INFO] MEJB-72/pom.xml .. SUCCESS
> (3.7 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run post-build script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy-all/2.4.8/groovy-all-2.4.8.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] mejb-93/pom.xml .. SUCCESS
> (4.1 s)
> [INFO] Building: reactor/pom.xml
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MEJB-112) JDK 9 WARNING in Integration Test
[
https://issues.apache.org/jira/browse/MEJB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MEJB-112:
--
Fix Version/s: 3.2.2
(was: more-investigation)
> JDK 9 WARNING in Integration Test
> -
>
> Key: MEJB-112
> URL: https://issues.apache.org/jira/browse/MEJB-112
> Project: Maven EJB Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.2.2
>
>
> Currently running on JDK 9 (EA+181) give the following warning during running
> via {{mvn -Prun-its clean verify}}:
> {code}
> [INFO] ..SUCCESS (3.8 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass$3$1
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy/2.0.1/groovy-2.0.1.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass$3$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] ..SUCCESS (4.1 s)
> [INFO] Building: reactor/pom.xml
> [INFO] run script verify.bsh
> [INFO] ..SUCCESS (3.4 s)
> {code}
> Upgrading to maven-invoker-plugin:3.0.1:
> {code}
> [INFO] run post-build script verify.bsh
> [INFO] MEJB-72/pom.xml .. SUCCESS
> (3.7 s)
> [INFO] Building: mejb-93/pom.xml
> [INFO] run post-build script verify.groovy
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.reflection.CachedClass
> (file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy-all/2.4.8/groovy-all-2.4.8.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.codehaus.groovy.reflection.CachedClass
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] mejb-93/pom.xml .. SUCCESS
> (4.1 s)
> [INFO] Building: reactor/pom.xml
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MEJB-138: - Assignee: Sylwester Lachiewicz > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEJB-137: -- Fix Version/s: 3.2.2 > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MEJB-138: -- Fix Version/s: 3.2.2 > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MEJB-137: - Assignee: Sylwester Lachiewicz > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEJB-138) Upgrade parent POM to version 42
[ https://issues.apache.org/jira/browse/MEJB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843282#comment-17843282 ] ASF GitHub Bot commented on MEJB-138: - slachiewicz opened a new pull request, #32: URL: https://github.com/apache/maven-ejb-plugin/pull/32 (no comment) > Upgrade parent POM to version 42 > > > Key: MEJB-138 > URL: https://issues.apache.org/jira/browse/MEJB-138 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MEJB-138) Upgrade parent POM to version 42
Sylwester Lachiewicz created MEJB-138: - Summary: Upgrade parent POM to version 42 Key: MEJB-138 URL: https://issues.apache.org/jira/browse/MEJB-138 Project: Maven EJB Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MEJB-137) Require Maven 3.6.3+
[ https://issues.apache.org/jira/browse/MEJB-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843280#comment-17843280 ] ASF GitHub Bot commented on MEJB-137: - slachiewicz opened a new pull request, #31: URL: https://github.com/apache/maven-ejb-plugin/pull/31 (no comment) > Require Maven 3.6.3+ > > > Key: MEJB-137 > URL: https://issues.apache.org/jira/browse/MEJB-137 > Project: Maven EJB Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump mavenVersion from 3.2.5 to 3.9.6 [maven-ejb-plugin]
dependabot[bot] commented on PR #26: URL: https://github.com/apache/maven-ejb-plugin/pull/26#issuecomment-2093392301 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump mavenVersion from 3.2.5 to 3.9.6 [maven-ejb-plugin]
slachiewicz closed pull request #26: Bump mavenVersion from 3.2.5 to 3.9.6 URL: https://github.com/apache/maven-ejb-plugin/pull/26 -- 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.7 to 2.16.1 [maven-ejb-plugin]
slachiewicz commented on PR #28: URL: https://github.com/apache/maven-ejb-plugin/pull/28#issuecomment-2093391965 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 [maven-ejb-plugin]
dependabot[bot] commented on PR #29: URL: https://github.com/apache/maven-ejb-plugin/pull/29#issuecomment-2093388172 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 [maven-ejb-plugin]
asfgit closed pull request #29: Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 URL: https://github.com/apache/maven-ejb-plugin/pull/29 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven:maven-compat from 3.2.5 to 3.8.1 [maven-ejb-plugin]
dependabot[bot] commented on PR #30: URL: https://github.com/apache/maven-ejb-plugin/pull/30#issuecomment-2093388004 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.maven:maven-compat from 3.2.5 to 3.8.1 [maven-ejb-plugin]
asfgit closed pull request #30: Bump org.apache.maven:maven-compat from 3.2.5 to 3.8.1 URL: https://github.com/apache/maven-ejb-plugin/pull/30 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.apache.maven:maven-compat from 3.2.5 to 3.8.1 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #30: URL: https://github.com/apache/maven-ejb-plugin/pull/30 Bumps [org.apache.maven:maven-compat](https://github.com/apache/maven) from 3.2.5 to 3.8.1. Commits https://github.com/apache/maven/commit/05c21c65bdfed0f71a2f2ada8b84da59348c4c5d;>05c21c6 [maven-release-plugin] prepare release maven-3.8.1 https://github.com/apache/maven/commit/d295dc362fe7d7b189b4976a5742a17362eb51a1;>d295dc3 [MNG-7128] keep blocked attribute from mirrors in artifact repositories https://github.com/apache/maven/commit/a46906806a31edb462b935e380a657b6efde6231;>a469068 next version in branch 3.8.x is 3.8.1-SNAPSHOT https://github.com/apache/maven/commit/dad8a3e1c55f34b7949945bc622f26447ddbf4f9;>dad8a3e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/6aa1f4acf5d6323e9aa08b763cb9933dc96749b9;>6aa1f4a [maven-release-plugin] prepare release maven-3.8.0 https://github.com/apache/maven/commit/907d53ad3264718f66ff15e1363d76b07dd0c05f;>907d53a [MNG-7118] block HTTP repositories by default https://github.com/apache/maven/commit/899465aeec03753ea91e15a79579eab76369c016;>899465a [MNG-7117] add support for blocked mirror https://github.com/apache/maven/commit/fa79cb22e456cc65522b5bab8c4240fe08c5775f;>fa79cb2 [MNG-7116] add support for mirrorOf external:http:* https://github.com/apache/maven/commit/e5f6634e17362387282b3867c9b23d4b54fea871;>e5f6634 use Maven Resolver 1.6.2 https://github.com/apache/maven/commit/09f77da9b0c39848fe763bdd4a392151eec0d8c3;>09f77da [MNG-7119] Upgrade Maven Wagon to 3.4.3 Additional commits viewable in https://github.com/apache/maven/compare/maven-3.2.5...maven-3.8.1;>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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-ejb-plugin/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MEJB-137) Require Maven 3.6.3+
Sylwester Lachiewicz created MEJB-137: - Summary: Require Maven 3.6.3+ Key: MEJB-137 URL: https://issues.apache.org/jira/browse/MEJB-137 Project: Maven EJB Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump org.apache.maven:maven-core from 3.2.5 to 3.8.1 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #29: URL: https://github.com/apache/maven-ejb-plugin/pull/29 Bumps [org.apache.maven:maven-core](https://github.com/apache/maven) from 3.2.5 to 3.8.1. Commits https://github.com/apache/maven/commit/05c21c65bdfed0f71a2f2ada8b84da59348c4c5d;>05c21c6 [maven-release-plugin] prepare release maven-3.8.1 https://github.com/apache/maven/commit/d295dc362fe7d7b189b4976a5742a17362eb51a1;>d295dc3 [MNG-7128] keep blocked attribute from mirrors in artifact repositories https://github.com/apache/maven/commit/a46906806a31edb462b935e380a657b6efde6231;>a469068 next version in branch 3.8.x is 3.8.1-SNAPSHOT https://github.com/apache/maven/commit/dad8a3e1c55f34b7949945bc622f26447ddbf4f9;>dad8a3e [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven/commit/6aa1f4acf5d6323e9aa08b763cb9933dc96749b9;>6aa1f4a [maven-release-plugin] prepare release maven-3.8.0 https://github.com/apache/maven/commit/907d53ad3264718f66ff15e1363d76b07dd0c05f;>907d53a [MNG-7118] block HTTP repositories by default https://github.com/apache/maven/commit/899465aeec03753ea91e15a79579eab76369c016;>899465a [MNG-7117] add support for blocked mirror https://github.com/apache/maven/commit/fa79cb22e456cc65522b5bab8c4240fe08c5775f;>fa79cb2 [MNG-7116] add support for mirrorOf external:http:* https://github.com/apache/maven/commit/e5f6634e17362387282b3867c9b23d4b54fea871;>e5f6634 use Maven Resolver 1.6.2 https://github.com/apache/maven/commit/09f77da9b0c39848fe763bdd4a392151eec0d8c3;>09f77da [MNG-7119] Upgrade Maven Wagon to 3.4.3 Additional commits viewable in https://github.com/apache/maven/compare/maven-3.2.5...maven-3.8.1;>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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/maven-ejb-plugin/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump commons-io:commons-io from 2.7 to 2.16.1 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #28: URL: https://github.com/apache/maven-ejb-plugin/pull/28 Bumps commons-io:commons-io from 2.7 to 2.16.1. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.apache.maven.shared:maven-shared-utils from 3.3.4 to 3.4.2 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #27: URL: https://github.com/apache/maven-ejb-plugin/pull/27 Bumps [org.apache.maven.shared:maven-shared-utils](https://github.com/apache/maven-shared-utils) from 3.3.4 to 3.4.2. Release notes Sourced from https://github.com/apache/maven-shared-utils/releases;>org.apache.maven.shared:maven-shared-utils's releases. 3.4.2 Bug Fixes https://issues.apache.org/jira/browse/MSHARED-1072;>[MSHARED-1072] - Poll data from input stream (https://redirect.github.com/apache/maven-shared-utils/pull/140;>#140) https://github.com/slawekjaranowski;>@slawekjaranowski Maintenance https://issues.apache.org/jira/browse/MSHARED-1252;>[MSHARED-1252] - Bump plexus-io to 3.4.1 for maven-assembly-plugin (https://redirect.github.com/apache/maven-shared-utils/pull/141;>#141) https://github.com/slawekjaranowski;>@slawekjaranowski 3.4.1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922version=12353186;>Release Notes New features and improvements https://issues.apache.org/jira/browse/MNG-7729;>[MNG-7729] - deprecate questionable IsEmpty/IsNotEmpty methods (https://redirect.github.com/apache/maven-shared-utils/pull/136;>#136) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1014;>[MSHARED-1014] - Make Commandline.addSystemEnvironment public and deprecated (https://redirect.github.com/apache/maven-shared-utils/pull/138;>#138) https://github.com/slawekjaranowski;>@slawekjaranowski Deprecate newXmlWriter (https://redirect.github.com/apache/maven-shared-utils/pull/131;>#131) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1172;>[MSHARED-1172] - Deprecate redundant isEmptyString method (https://redirect.github.com/apache/maven-shared-utils/pull/123;>#123) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1169;>[MSHARED-1169] - deprecate join methods now available in Java 8 String class (https://redirect.github.com/apache/maven-shared-utils/pull/127;>#127) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1122;>[MSHARED-1122] - FileUtils: avoid getCanonicalPath() (https://redirect.github.com/apache/maven-shared-utils/pull/114;>#114) https://github.com/jukzi;>@jukzi https://issues.apache.org/jira/browse/MSHARED-1079;>[MSHARED-1079] - add build() method and document toString() method (https://redirect.github.com/apache/maven-shared-utils/pull/96;>#96) https://github.com/kwin;>@kwin https://issues.apache.org/jira/browse/MSHARED-1014;>[MSHARED-1014] - Optionally inherit system environment variables by Commandline (https://redirect.github.com/apache/maven-shared-utils/pull/94;>#94) https://github.com/slawekjaranowski;>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-983;>[MSHARED-983] - Drop plexus container default (https://redirect.github.com/apache/maven-shared-utils/pull/87;>#87) https://github.com/cstamas;>@cstamas Bug Fixes https://issues.apache.org/jira/browse/MSHARED-953;>[MSHARED-953] - don't trim (https://redirect.github.com/apache/maven-shared-utils/pull/124;>#124) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1072;>[MSHARED-1072] - fix blocking in StreamFeeder (https://redirect.github.com/apache/maven-shared-utils/pull/113;>#113) https://github.com/slawekjaranowski;>@slawekjaranowski https://issues.apache.org/jira/browse/MSHARED-1109;>[MSHARED-1109] - Ignore MessageUtilsTest methods on unsupported platforms (https://redirect.github.com/apache/maven-shared-utils/pull/106;>#106) https://github.com/kwin;>@kwin https://issues.apache.org/jira/browse/MSHARED-1107;>[MSHARED-1107] - Make copyFile succeed with source file having (https://redirect.github.com/apache/maven-shared-utils/pull/105;>#105) https://github.com/kwin;>@kwin https://issues.apache.org/jira/browse/MSHARED-985;>[MSHARED-985] - XmlWriterUtil platform independent and consistent (https://redirect.github.com/apache/maven-shared-utils/pull/91;>#91) https://github.com/elharo;>@elharo Dependency updates Bump maven-resources-plugin from 3.1.0 to 3.3.1 (https://redirect.github.com/apache/maven-shared-utils/pull/137;>#137) https://github.com/dependabot;>@dependabot https://issues.apache.org/jira/browse/MSHARED-1196;>[MSHARED-1196] - Bump maven-shared-components from 37 to 39 (https://redirect.github.com/apache/maven-shared-utils/pull/134;>#134) https://github.com/elharo;>@elharo https://issues.apache.org/jira/browse/MSHARED-1197;>[MSHARED-1197] - Bump plexus-utils from 3.5.0 to 3.5.1 (https://redirect.github.com/apache/maven-shared-utils/pull/132;>#132) https://github.com/dependabot;>@dependabot Bump apache/maven-gh-actions-shared from 2 to 3 (https://redirect.github.com/apache/maven-shared-utils/pull/130;>#130)
[PR] Bump mavenVersion from 3.2.5 to 3.9.6 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #26:
URL: https://github.com/apache/maven-ejb-plugin/pull/26
Bumps `mavenVersion` from 3.2.5 to 3.9.6.
Updates `org.apache.maven:maven-plugin-api` from 3.2.5 to 3.9.6
Release notes
Sourced from https://github.com/apache/maven/releases;>org.apache.maven:maven-plugin-api's
releases.
3.9.6
https://maven.apache.org/docs/3.9.6/release-notes.html;>Release
Notes - Maven - Version 3.9.6
Improvement
[https://issues.apache.org/jira/browse/MNG-7939;>MNG-7939]
- Allow to exclude plugins from validation
Dependency upgrade
[https://issues.apache.org/jira/browse/MNG-7913;>MNG-7913]
- Upgrade Sisu version to 0.9.0.M2
[https://issues.apache.org/jira/browse/MNG-7934;>MNG-7934]
- Upgrade Resolver version to 1.9.18
[https://issues.apache.org/jira/browse/MNG-7942;>MNG-7942]
- Upgrade to parent POM 41
[https://issues.apache.org/jira/browse/MNG-7943;>MNG-7943]
- Upgrade default plugin bindings
3.9.5
https://maven.apache.org/docs/3.9.5/release-notes.html;>Release
Notes - Maven - Version 3.9.5
Bug
[https://issues.apache.org/jira/browse/MNG-7851;>MNG-7851]
- Error message when modelVersion is 4.0 is confusing
Improvement
[https://issues.apache.org/jira/browse/MNG-7875;>MNG-7875]
- colorize transfer messages
[https://issues.apache.org/jira/browse/MNG-7895;>MNG-7895]
- Support ${project.basedir} in file profile activation
Task
[https://issues.apache.org/jira/browse/MNG-7856;>MNG-7856]
- Maven Resolver Provider classes ctor change
[https://issues.apache.org/jira/browse/MNG-7870;>MNG-7870]
- Undeprecate wrongly deprecated repository metadata
[https://issues.apache.org/jira/browse/MNG-7872;>MNG-7872]
- Deprecate org.apache.maven.repository.internal.MavenResolverModule
[https://issues.apache.org/jira/browse/MNG-7874;>MNG-7874]
- maven-resolver-provider: introduce NAME constants.
Dependency upgrade
[https://issues.apache.org/jira/browse/MNG-7859;>MNG-7859]
- Update to Resolver 1.9.16
3.9.4
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922version=12353369;>Release
Notes - Maven - Version 3.9.4
... (truncated)
Commits
https://github.com/apache/maven/commit/bc0240f3c744dd6b6ec2920b3cd08dcc295161ae;>bc0240f
[maven-release-plugin] prepare release maven-3.9.6
https://github.com/apache/maven/commit/e6cc6c53cb979f46e7cf97fc9bab686343500a94;>e6cc6c5
[MNG-7943] Upgrade default plugin bindings
https://github.com/apache/maven/commit/48adee3711705c65918b2c736e88093a052f30f8;>48adee3
[MNG-7934] Update to Resolver 1.9.18 (https://redirect.github.com/apache/maven/issues/1326;>#1326)
https://github.com/apache/maven/commit/da6c7e4bcac34677ad9e7d93f345d9c896866e1b;>da6c7e4
[MNG-7942] Upgrade maven-parent to 41
https://github.com/apache/maven/commit/95fa548e1db672ac7b102ff27585c82ed5ae9ed2;>95fa548
[MNG-7934] Update to Resolver 1.9.17 (https://redirect.github.com/apache/maven/issues/1321;>#1321)
https://github.com/apache/maven/commit/c54baa64b38c09c440a11285d560e47d894b2414;>c54baa6
[MNG-7939] Allow to exclude plugins from validation
https://github.com/apache/maven/commit/ecd59b7158e048a6298b8b52d44fccaba26065ad;>ecd59b7
[MNG-7913] Upgrade Sisu version (https://redirect.github.com/apache/maven/issues/1286;>#1286)
https://github.com/apache/maven/commit/53edd71c989d8f2f2b92ee0b281976772c78b927;>53edd71
Use the same branch name for ITs on Jenkins (https://redirect.github.com/apache/maven/issues/1263;>#1263)
https://github.com/apache/maven/commit/2bc44491af62fef51e17d6ad0172baff82c8d022;>2bc4449
The maven-3.9.x branch should fallback to maven-3.9.x branch of ITs
https://github.com/apache/maven/commit/6e532cd249c0413fb6885ca6dfcc67dce25f703d;>6e532cd
[maven-release-plugin] prepare for next development iteration
Additional commits viewable in https://github.com/apache/maven/compare/maven-3.2.5...maven-3.9.6;>compare
view
Updates `org.apache.maven:maven-core` from 3.2.5 to 3.9.6
Release notes
Sourced from https://github.com/apache/maven/releases;>org.apache.maven:maven-core's
releases.
3.9.6
https://maven.apache.org/docs/3.9.6/release-notes.html;>Release
Notes - Maven - Version 3.9.6
Improvement
[https://issues.apache.org/jira/browse/MNG-7939;>MNG-7939]
- Allow to exclude plugins from validation
Dependency upgrade
[https://issues.apache.org/jira/browse/MNG-7913;>MNG-7913]
- Upgrade Sisu version to 0.9.0.M2
[https://issues.apache.org/jira/browse/MNG-7934;>MNG-7934]
- Upgrade Resolver version to 1.9.18
[https://issues.apache.org/jira/browse/MNG-7942;>MNG-7942]
- Upgrade to parent POM 41
[https://issues.apache.org/jira/browse/MNG-7943;>MNG-7943]
- Upgrade default plugin bindings
3.9.5
https://maven.apache.org/docs/3.9.5/release-notes.html;>Release
Notes - Maven - Version 3.9.5
Bug
[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.2 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #25: URL: https://github.com/apache/maven-ejb-plugin/pull/25 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.2. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases;>org.codehaus.plexus:plexus-archiver's releases. 4.9.2 Dependency updates Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/325;>#325) https://github.com/dependabot;>@dependabot Bump org.codehaus.plexus:plexus from 16 to 17 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/324;>#324) https://github.com/dependabot;>@dependabot Bump org.apache.commons:commons-compress from 1.25.0 to 1.26.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/323;>#323) https://github.com/dependabot;>@dependabot Bump org.assertj:assertj-core from 3.25.2 to 3.25.3 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/322;>#322) https://github.com/dependabot;>@dependabot Bump org.assertj:assertj-core from 3.25.1 to 3.25.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/320;>#320) https://github.com/dependabot;>@dependabot Bump org.assertj:assertj-core from 3.24.2 to 3.25.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/319;>#319) https://github.com/dependabot;>@dependabot Bump org.codehaus.plexus:plexus-io from 3.4.1 to 3.4.2 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/317;>#317) https://github.com/dependabot;>@dependabot Maintenance Bump release-drafter/release-drafter from 5 to 6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/321;>#321) https://github.com/dependabot;>@dependabot 4.9.1 New features and improvements https://redirect.github.com/codehaus-plexus/plexus-archiver/issues/311;>#311 - provide fluent setter for usingDefaultExcludes flag in Abstrac… (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/312;>#312) https://github.com/redzi;>@redzi Dependency updates Bump org.codehaus.plexus:plexus from 15 to 16 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/316;>#316) https://github.com/dependabot;>@dependabot Bump com.github.luben:zstd-jni from 1.5.5-10 to 1.5.5-11 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/314;>#314) https://github.com/dependabot;>@dependabot Bump commons-io:commons-io from 2.15.0 to 2.15.1 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/313;>#313) https://github.com/dependabot;>@dependabot Bump org.apache.commons:commons-compress from 1.24.0 to 1.25.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/309;>#309) https://github.com/dependabot;>@dependabot Maintenance Reuse plexus-pom action for CI (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/315;>#315) https://github.com/slachiewicz;>@slachiewicz 4.9.0 New features and improvements Allow copy all files without timestamp checking by DirectoryArchiver (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/304;>#304) https://github.com/slawekjaranowski;>@slawekjaranowski Dependency updates Bump com.github.luben:zstd-jni from 1.5.5-6 to 1.5.5-10 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/307;>#307) https://github.com/dependabot;>@dependabot Bump commons-io:commons-io from 2.14.0 to 2.15.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/303;>#303) https://github.com/dependabot;>@dependabot Bump org.codehaus.plexus:plexus from 14 to 15 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/302;>#302) https://github.com/dependabot;>@dependabot Bump com.github.luben:zstd-jni from 1.5.5-5 to 1.5.5-6 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/301;>#301) https://github.com/dependabot;>@dependabot Bump commons-io:commons-io from 2.13.0 to 2.14.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/300;>#300) https://github.com/dependabot;>@dependabot Bump org.apache.commons:commons-compress from 1.23.0 to 1.24.0 (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/298;>#298) https://github.com/dependabot;>@dependabot Maintenance ... (truncated) Commits https://github.com/codehaus-plexus/plexus-archiver/commit/30e3a058ff1a68ad934c105e097a137e05743111;>30e3a05 [maven-release-plugin] prepare release plexus-archiver-4.9.2 https://github.com/codehaus-plexus/plexus-archiver/commit/0d2bedcfd3798fee20aa81676a4f02147d530cff;>0d2bedc Bump org.apache.commons:commons-compress from 1.26.0 to 1.26.1
[PR] Bump org.apache.maven.plugins:maven-plugins from 39 to 42 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #24: URL: https://github.com/apache/maven-ejb-plugin/pull/24 Bumps [org.apache.maven.plugins:maven-plugins](https://github.com/apache/maven-parent) from 39 to 42. Release notes Sourced from https://github.com/apache/maven-parent/releases;>org.apache.maven.plugins:maven-plugins's releases. 42 Bug [https://issues.apache.org/jira/browse/MPOM-449;>MPOM-449] - Remove the leading 1. from source/target properties Improvement [https://issues.apache.org/jira/browse/MPOM-447;>MPOM-447] - activate javac's release flag when building with JDK supporting that feature [https://issues.apache.org/jira/browse/MPOM-453;>MPOM-453] - Disable annotation processing by compiler [https://issues.apache.org/jira/browse/MPOM-454;>MPOM-454] - Warning about usage of deprecated API by compiler [https://issues.apache.org/jira/browse/MPOM-477;>MPOM-477] - Skip empty PMD reports [https://issues.apache.org/jira/browse/MPOM-478;>MPOM-478] - Remove manually maintained history from site [https://issues.apache.org/jira/browse/MPOM-483;>MPOM-483] - Make a separate module for documentation Task [https://issues.apache.org/jira/browse/MPOM-482;>MPOM-482] - Publish site descriptor with new parent Dependency upgrade [https://issues.apache.org/jira/browse/MPOM-448;>MPOM-448] - Update spotless-maven-plugin from 2.40.0 to 2.41.1 [https://issues.apache.org/jira/browse/MPOM-455;>MPOM-455] - Add dependencyManagement for JUnit 5 [https://issues.apache.org/jira/browse/MPOM-459;>MPOM-459] - Bump org.apache.maven.plugins:maven-jxr-plugin from 3.3.1 to 3.3.2 [https://issues.apache.org/jira/browse/MPOM-464;>MPOM-464] - Bump com.diffplug.spotless:spotless-maven-plugin from 2.41.1 to 2.43.0 [https://issues.apache.org/jira/browse/MPOM-473;>MPOM-473] - Bump org.cyclonedx:cyclonedx-maven-plugin from 2.7.10 to 2.7.11 [https://issues.apache.org/jira/browse/MPOM-474;>MPOM-474] - Bump org.codehaus.mojo:extra-enforcer-rules from 1.7.0 to 1.8.0 [https://issues.apache.org/jira/browse/MPOM-485;>MPOM-485] - Bump org.codehaus.plexus:plexus-utils from 4.0.0 to 4.0.1 [https://issues.apache.org/jira/browse/MPOM-487;>MPOM-487] - Bump parent to 32 41 Improvement [https://issues.apache.org/jira/browse/MPOM-426;>MPOM-426] - downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3 [https://issues.apache.org/jira/browse/MPOM-429;>MPOM-429] - Support development with Java 21 (palantirJavaFormat) [https://issues.apache.org/jira/browse/MPOM-443;>MPOM-443] - Skip empty surefire reports Task [https://issues.apache.org/jira/browse/MPOM-427;>MPOM-427] - use version.artifactId property for dependency versions (like plugins) [https://issues.apache.org/jira/browse/MPOM-436;>MPOM-436] - Remove quality-checks profile with maven-docck-plugin [https://issues.apache.org/jira/browse/MPOM-445;>MPOM-445] - Use maven-checkstyle-plugin version from parent Dependency upgrade ... (truncated) Commits See full diff in https://github.com/apache/maven-parent/commits;>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
Re: [PR] Bump apache/maven-gh-actions-shared from 2 to 4 [maven-ejb-plugin]
slachiewicz merged PR #23: URL: https://github.com/apache/maven-ejb-plugin/pull/23 -- 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 apache/maven-gh-actions-shared from 2 to 4 [maven-ejb-plugin]
dependabot[bot] opened a new pull request, #23: URL: https://github.com/apache/maven-ejb-plugin/pull/23 Bumps [apache/maven-gh-actions-shared](https://github.com/apache/maven-gh-actions-shared) from 2 to 4. Commits https://github.com/apache/maven-gh-actions-shared/commit/994eebd0d7acb406c055aed405b32ca42415df91;>994eebd Switch JDK distribution to zulu as default https://github.com/apache/maven-gh-actions-shared/commit/26f55bffc699e7bc46a512ae86187bce7d5340be;>26f55bf Apply ASF Infra GitHub Actions Policy https://github.com/apache/maven-gh-actions-shared/commit/45f4617ba01c4be9dca576ff755f548127e76086;>45f4617 Add GPG install step https://github.com/apache/maven-gh-actions-shared/commit/4b03389d55cc542bb6cf0ccc41e8fb4e1d477cc1;>4b03389 Bump release-drafter/release-drafter from 5 to 6 https://github.com/apache/maven-gh-actions-shared/commit/03cf72bd4ed6b6b3783f2866097094b35d510e3e;>03cf72b Use Maven 3.6.3, 3.9.6 in matrix build by default https://github.com/apache/maven-gh-actions-shared/commit/b896303edd9876881cfbe637d32484da127f3f01;>b896303 Restrict permissions to GITHUB_TOKEN https://github.com/apache/maven-gh-actions-shared/commit/798774c1b6422e9ba23b3ec77df0aec086ffe3ab;>798774c Add JDK 21 to default tests https://github.com/apache/maven-gh-actions-shared/commit/2e157a90fea1356a2bd0587bc725173bbc5f35f3;>2e157a9 Bump actions/upload-artifact from 3 to 4 https://github.com/apache/maven-gh-actions-shared/commit/ef4954efcdd600476254a9afab005a4d0f7c528e;>ef4954e Skip Maven Site testing on second executions https://github.com/apache/maven-gh-actions-shared/commit/564c1c43016a798d08e4115438d54292a672eab9;>564c1c4 Use Maven 3.9.6 as default Additional commits viewable in https://github.com/apache/maven-gh-actions-shared/compare/v2...v4;>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] [Closed] (MCHANGELOG-144) svn and maven-changelog-plugin results in “The filename, directory name, or volume label syntax is incorrect”
[
https://issues.apache.org/jira/browse/MCHANGELOG-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MCHANGELOG-144.
---
Resolution: Information Provided
> svn and maven-changelog-plugin results in “The filename, directory name, or
> volume label syntax is incorrect”
> -
>
> Key: MCHANGELOG-144
> URL: https://issues.apache.org/jira/browse/MCHANGELOG-144
> Project: Maven Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows Server 2016
> maven 3.5.2
>Reporter: Adrian Wyssmann
>Priority: Major
>
> We are using maven-changelog-plugin:2.3 to generate the changelog. The job is
> triggered by Jenkins but recently the job starts failing. Here is what I see
> in the log
> {code:java}
> ...
> ...
> 22:05:41 [DEBUG] Multipage report: 0 subreports
> 22:05:41 [DEBUG] Generating
> D:\jenkins\workspace\MAVEN-Company-Project\target\site\changelog.html
> 22:05:41 [INFO] Generating "Change Log" report---
> maven-changelog-plugin:2.3:changelog
> 22:05:41 [INFO] Generating changed sets xml to:
> D:\jenkins\workspace\MAVEN-Company-Project\target\changelog.xml
> 22:05:41 [INFO] Executing: cmd.exe /X /C "svn --username CIUSER --password
> * --no-auth-cache --non-interactive log -v -r "{2018-01-29 21:05:41
> +}:{2018-03-01 21:05:41 +}"
> http://svn.mycompany.intra:80/svn/parentpom/trunk/;
> 22:05:41 [INFO] Working directory: D:\jenkins\workspace\MAVEN-Company-Project
> 22:05:41 [ERROR] Provider message:
> 22:05:41 [ERROR] The svn command failed.
> 22:05:41 [ERROR] Command output:
> 22:05:41 [ERROR] The filename, directory name, or volume label syntax is
> incorrect.
> 22:05:41
> 22:05:41 [INFO]
>
> 22:05:41 [INFO] BUILD FAILURE
> 22:05:41 [INFO]
>
> 22:05:41 [INFO] Total time: 13.994 s
> 22:05:41 [INFO] Finished at: 2018-02-28T22:05:41+01:00
> 22:05:41 [INFO] Final Memory: 43M/451M
> 22:05:41 [INFO]
>
> 22:05:41 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project
> mycompany: Error generating maven-changelog-plugin:2.3:changelog: An error
> has occurred during changelog command : : Command failed. -> [Help 1]
> 22:05:41 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-site-plugin:3.6:site
> (default-cli) on project mycompany: Error generating
> maven-changelog-plugin:2.3:changelog: An error has occurred during changelog
> command :
> 22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> 22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> 22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> 22:05:41 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> 22:05:41 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> 22:05:41 at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> 22:05:41 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> ...{code}
> Running the command manually in the workspace directory
> D:\jenkins\workspace\MAVEN-Company-Project\ works without problems.
> The problems occurs in conjunction with maven 3.5.2. When switching back to
> maven 3.1.1 the error does not appear.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MCHANGELOG-128) Remove the unused commentFormat parameter from changelog mojo
[ https://issues.apache.org/jira/browse/MCHANGELOG-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MCHANGELOG-128. --- Resolution: Fixed > Remove the unused commentFormat parameter from changelog mojo > - > > Key: MCHANGELOG-128 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-128 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2, 2.3 >Reporter: Martin D'Aloia >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.0.0 > > Attachments: remove-commentFormat-parameter.patch > > > The parameter commentFormat on the changelog mojo is unused and the javadoc > says that it is used by ClearcaseChangeLogGenerator which not exists on the > project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHANGELOG-128) Remove the unused commentFormat parameter from changelog mojo
[ https://issues.apache.org/jira/browse/MCHANGELOG-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MCHANGELOG-128: --- Assignee: Sylwester Lachiewicz > Remove the unused commentFormat parameter from changelog mojo > - > > Key: MCHANGELOG-128 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-128 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2, 2.3 >Reporter: Martin D'Aloia >Assignee: Sylwester Lachiewicz >Priority: Trivial > Attachments: remove-commentFormat-parameter.patch > > > The parameter commentFormat on the changelog mojo is unused and the javadoc > says that it is used by ClearcaseChangeLogGenerator which not exists on the > project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MCHANGELOG-128) Remove the unused commentFormat parameter from changelog mojo
[ https://issues.apache.org/jira/browse/MCHANGELOG-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MCHANGELOG-128: Fix Version/s: 3.0.0 > Remove the unused commentFormat parameter from changelog mojo > - > > Key: MCHANGELOG-128 > URL: https://issues.apache.org/jira/browse/MCHANGELOG-128 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.2, 2.3 >Reporter: Martin D'Aloia >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.0.0 > > Attachments: remove-commentFormat-parameter.patch > > > The parameter commentFormat on the changelog mojo is unused and the javadoc > says that it is used by ClearcaseChangeLogGenerator which not exists on the > project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MCHANGELOG-151) Migrate plugin to Maven 3.6.3
[ https://issues.apache.org/jira/browse/MCHANGELOG-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MCHANGELOG-151: --- Assignee: Sylwester Lachiewicz > 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)
