[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar
[
https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691490#comment-17691490
]
Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:09 AM:
-
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
{code}mvn clean site
{code}
fails, while running
{code}mvn clean javadoc:javadoc
{code}
runs fine.
was (Author: matinh):
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
bq. {{mvn clean site}}
fails, while running
{quote}{{mvn clean javadoc:javadoc}}{quote}
runs fine.
> Dependencies not resolved for aggregate-jar
> ---
>
> Key: MJAVADOC-728
> URL: https://issues.apache.org/jira/browse/MJAVADOC-728
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.2.0, 3.4.1
>Reporter: Youenn LE JEUNE
>Priority: Major
>
> When building a multi-modules project using {{maven clean install
> javadoc:aggregate-jar}} I'm getting this:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:aggregate-jar
> (default-cli) on project beautyquests-parent: MavenReportException: Error
> while generating Javadoc:
> [ERROR] Exit code: 1 - Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\AbstractHolograms.java...
> [ERROR] Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\bossbar\BQBossBarImplementation.java...
> ...much more similar lines...
> [ERROR] Loading source files for package fr.skytasul.quests.api...
> ...again similar lines...
> [ERROR] Constructing Javadoc information...
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\commands\CommandsManager.java:9:
> error: cannot find symbol
> [ERROR] import org.jetbrains.annotations.Unmodifiable;
> [ERROR] ^
> [ERROR] symbol: class Unmodifiable
> [ERROR] location: package org.jetbrains.annotations
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\gui\ImmutableItemStack.java:9:
> error: cannot access HoverEventSource
> [ERROR] public class ImmutableItemStack extends ItemStack {
> [ERROR] ^
> [ERROR] class file for net.kyori.adventure.text.event.HoverEventSource not
> found
> ... 71 other errors ...{code}
> The javadoc generation fails on every dependency class/annotation/etc. access.
> Simply using the {{javadoc:jar}} plugin works, but it is not what I want.
> My parent project has those properties:
> {code:java}
> 1.8
> 1.8 {code}
> which are not overriden in the _core_ module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar
[
https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691490#comment-17691490
]
Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:08 AM:
-
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
bq. {{mvn clean site}}
fails, while running
{quote}{{mvn clean javadoc:javadoc}}{quote}
runs fine.
was (Author: matinh):
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
bq. {{mvn clean site}}
fails, while running
{{mvn clean javadoc:javadoc}}
runs fine.
> Dependencies not resolved for aggregate-jar
> ---
>
> Key: MJAVADOC-728
> URL: https://issues.apache.org/jira/browse/MJAVADOC-728
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.2.0, 3.4.1
>Reporter: Youenn LE JEUNE
>Priority: Major
>
> When building a multi-modules project using {{maven clean install
> javadoc:aggregate-jar}} I'm getting this:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:aggregate-jar
> (default-cli) on project beautyquests-parent: MavenReportException: Error
> while generating Javadoc:
> [ERROR] Exit code: 1 - Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\AbstractHolograms.java...
> [ERROR] Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\bossbar\BQBossBarImplementation.java...
> ...much more similar lines...
> [ERROR] Loading source files for package fr.skytasul.quests.api...
> ...again similar lines...
> [ERROR] Constructing Javadoc information...
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\commands\CommandsManager.java:9:
> error: cannot find symbol
> [ERROR] import org.jetbrains.annotations.Unmodifiable;
> [ERROR] ^
> [ERROR] symbol: class Unmodifiable
> [ERROR] location: package org.jetbrains.annotations
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\gui\ImmutableItemStack.java:9:
> error: cannot access HoverEventSource
> [ERROR] public class ImmutableItemStack extends ItemStack {
> [ERROR] ^
> [ERROR] class file for net.kyori.adventure.text.event.HoverEventSource not
> found
> ... 71 other errors ...{code}
> The javadoc generation fails on every dependency class/annotation/etc. access.
> Simply using the {{javadoc:jar}} plugin works, but it is not what I want.
> My parent project has those properties:
> {code:java}
> 1.8
> 1.8 {code}
> which are not overriden in the _core_ module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar
[
https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691490#comment-17691490
]
Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:07 AM:
-
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
{{mvn clean site}}
fails, while running
{{mvn clean javadoc:javadoc}}
runs fine.
was (Author: matinh):
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
{{ mvn clean site}}
fails, while running
{{ mvn clean javadoc:javadoc}}
runs fine.
> Dependencies not resolved for aggregate-jar
> ---
>
> Key: MJAVADOC-728
> URL: https://issues.apache.org/jira/browse/MJAVADOC-728
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.2.0, 3.4.1
>Reporter: Youenn LE JEUNE
>Priority: Major
>
> When building a multi-modules project using {{maven clean install
> javadoc:aggregate-jar}} I'm getting this:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:aggregate-jar
> (default-cli) on project beautyquests-parent: MavenReportException: Error
> while generating Javadoc:
> [ERROR] Exit code: 1 - Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\AbstractHolograms.java...
> [ERROR] Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\bossbar\BQBossBarImplementation.java...
> ...much more similar lines...
> [ERROR] Loading source files for package fr.skytasul.quests.api...
> ...again similar lines...
> [ERROR] Constructing Javadoc information...
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\commands\CommandsManager.java:9:
> error: cannot find symbol
> [ERROR] import org.jetbrains.annotations.Unmodifiable;
> [ERROR] ^
> [ERROR] symbol: class Unmodifiable
> [ERROR] location: package org.jetbrains.annotations
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\gui\ImmutableItemStack.java:9:
> error: cannot access HoverEventSource
> [ERROR] public class ImmutableItemStack extends ItemStack {
> [ERROR] ^
> [ERROR] class file for net.kyori.adventure.text.event.HoverEventSource not
> found
> ... 71 other errors ...{code}
> The javadoc generation fails on every dependency class/annotation/etc. access.
> Simply using the {{javadoc:jar}} plugin works, but it is not what I want.
> My parent project has those properties:
> {code:java}
> 1.8
> 1.8 {code}
> which are not overriden in the _core_ module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar
[
https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691490#comment-17691490
]
Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:07 AM:
-
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
bq. {{mvn clean site}}
fails, while running
{{mvn clean javadoc:javadoc}}
runs fine.
was (Author: matinh):
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
{{mvn clean site}}
fails, while running
{{mvn clean javadoc:javadoc}}
runs fine.
> Dependencies not resolved for aggregate-jar
> ---
>
> Key: MJAVADOC-728
> URL: https://issues.apache.org/jira/browse/MJAVADOC-728
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.2.0, 3.4.1
>Reporter: Youenn LE JEUNE
>Priority: Major
>
> When building a multi-modules project using {{maven clean install
> javadoc:aggregate-jar}} I'm getting this:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:aggregate-jar
> (default-cli) on project beautyquests-parent: MavenReportException: Error
> while generating Javadoc:
> [ERROR] Exit code: 1 - Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\AbstractHolograms.java...
> [ERROR] Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\bossbar\BQBossBarImplementation.java...
> ...much more similar lines...
> [ERROR] Loading source files for package fr.skytasul.quests.api...
> ...again similar lines...
> [ERROR] Constructing Javadoc information...
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\commands\CommandsManager.java:9:
> error: cannot find symbol
> [ERROR] import org.jetbrains.annotations.Unmodifiable;
> [ERROR] ^
> [ERROR] symbol: class Unmodifiable
> [ERROR] location: package org.jetbrains.annotations
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\gui\ImmutableItemStack.java:9:
> error: cannot access HoverEventSource
> [ERROR] public class ImmutableItemStack extends ItemStack {
> [ERROR] ^
> [ERROR] class file for net.kyori.adventure.text.event.HoverEventSource not
> found
> ... 71 other errors ...{code}
> The javadoc generation fails on every dependency class/annotation/etc. access.
> Simply using the {{javadoc:jar}} plugin works, but it is not what I want.
> My parent project has those properties:
> {code:java}
> 1.8
> 1.8 {code}
> which are not overriden in the _core_ module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MJAVADOC-728) Dependencies not resolved for aggregate-jar
[
https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691490#comment-17691490
]
Martin Höller edited comment on MJAVADOC-728 at 11/7/23 7:07 AM:
-
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
{{ mvn clean site}}
fails, while running
{{ mvn clean javadoc:javadoc}}
runs fine.
was (Author: matinh):
Problem still exists with m-javadoc-p 3.5.0. Tested with maven-site-plugin
3.12.1 and 4.0.0-M5.
For me, the problem only exists if I generate JavaDoc via the
maven-site-plugin. Running
mvn clean site
fails, while running
mvn clean javadoc:javadoc
runs fine.
> Dependencies not resolved for aggregate-jar
> ---
>
> Key: MJAVADOC-728
> URL: https://issues.apache.org/jira/browse/MJAVADOC-728
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.2.0, 3.4.1
>Reporter: Youenn LE JEUNE
>Priority: Major
>
> When building a multi-modules project using {{maven clean install
> javadoc:aggregate-jar}} I'm getting this:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:aggregate-jar
> (default-cli) on project beautyquests-parent: MavenReportException: Error
> while generating Javadoc:
> [ERROR] Exit code: 1 - Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\AbstractHolograms.java...
> [ERROR] Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\bossbar\BQBossBarImplementation.java...
> ...much more similar lines...
> [ERROR] Loading source files for package fr.skytasul.quests.api...
> ...again similar lines...
> [ERROR] Constructing Javadoc information...
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\commands\CommandsManager.java:9:
> error: cannot find symbol
> [ERROR] import org.jetbrains.annotations.Unmodifiable;
> [ERROR] ^
> [ERROR] symbol: class Unmodifiable
> [ERROR] location: package org.jetbrains.annotations
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\gui\ImmutableItemStack.java:9:
> error: cannot access HoverEventSource
> [ERROR] public class ImmutableItemStack extends ItemStack {
> [ERROR] ^
> [ERROR] class file for net.kyori.adventure.text.event.HoverEventSource not
> found
> ... 71 other errors ...{code}
> The javadoc generation fails on every dependency class/annotation/etc. access.
> Simply using the {{javadoc:jar}} plugin works, but it is not what I want.
> My parent project has those properties:
> {code:java}
> 1.8
> 1.8 {code}
> which are not overriden in the _core_ module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAVADOC-728) Dependencies not resolved for aggregate-jar
[
https://issues.apache.org/jira/browse/MJAVADOC-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783511#comment-17783511
]
Martin Höller commented on MJAVADOC-728:
Still same (buggy) behavior with {{maven-javadoc-plugin}} 3.6.2.
> Dependencies not resolved for aggregate-jar
> ---
>
> Key: MJAVADOC-728
> URL: https://issues.apache.org/jira/browse/MJAVADOC-728
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar, javadoc
>Affects Versions: 3.2.0, 3.4.1
>Reporter: Youenn LE JEUNE
>Priority: Major
>
> When building a multi-modules project using {{maven clean install
> javadoc:aggregate-jar}} I'm getting this:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:aggregate-jar
> (default-cli) on project beautyquests-parent: MavenReportException: Error
> while generating Javadoc:
> [ERROR] Exit code: 1 - Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\AbstractHolograms.java...
> [ERROR] Loading source file
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\api\bossbar\BQBossBarImplementation.java...
> ...much more similar lines...
> [ERROR] Loading source files for package fr.skytasul.quests.api...
> ...again similar lines...
> [ERROR] Constructing Javadoc information...
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\commands\CommandsManager.java:9:
> error: cannot find symbol
> [ERROR] import org.jetbrains.annotations.Unmodifiable;
> [ERROR] ^
> [ERROR] symbol: class Unmodifiable
> [ERROR] location: package org.jetbrains.annotations
> [ERROR]
> C:\Users\skyta\Documents\eclipse-workspace\BeautyQuests\core\src\main\java\fr\skytasul\quests\gui\ImmutableItemStack.java:9:
> error: cannot access HoverEventSource
> [ERROR] public class ImmutableItemStack extends ItemStack {
> [ERROR] ^
> [ERROR] class file for net.kyori.adventure.text.event.HoverEventSource not
> found
> ... 71 other errors ...{code}
> The javadoc generation fails on every dependency class/annotation/etc. access.
> Simply using the {{javadoc:jar}} plugin works, but it is not what I want.
> My parent project has those properties:
> {code:java}
> 1.8
> 1.8 {code}
> which are not overriden in the _core_ module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Change bootstrap syntax to align with the usual one [maven-integration-testing]
gnodet opened a new pull request, #316: URL: https://github.com/apache/maven-integration-testing/pull/316 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MSHARED-1327) Change output directory default in AbstractMavenReport
[
https://issues.apache.org/jira/browse/MSHARED-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783407#comment-17783407
]
ASF GitHub Bot commented on MSHARED-1327:
-
kriegaex commented on PR #26:
URL:
https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1797056331
> would you keep it in the build output dir directory? What is your opinion
on the clutter?
My use case with AspectJ reporting is a multi-page report, for which always
a subdirectory is created anyway. Honestly, when fixing the ITs here, I did not
check whether there was additional clutter written into the build directory,
because I think that each mojo writing more than a single file - say PDF, HTML
or whatever - ought to take care of creating a subdir for itself anyway,
because the same clutter would also end up in the reporting directory with the
old default, dangerously mixing with the output of other plugins. So arguably,
the demo plugin in the IT does not behave well.
> Change output directory default in AbstractMavenReport
> --
>
> Key: MSHARED-1327
> URL: https://issues.apache.org/jira/browse/MSHARED-1327
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-reporting-impl
>Affects Versions: maven-reporting-impl-4.0.0-M11
>Reporter: Alexander Kriegisch
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-impl-4.0.0-M12
>
>
> The output directory should default to {{${project.build.directory}}} instead
> of {{${project.reporting.outputDirectory}}}. Quoting my reasoning from
> https://github.com/apache/maven-jxr/commit/ae81a34ac616bf7e4ea4fa9d4eb09f0979eaccb1#commitcomment-130639906:
> {quote}
> (...) because the latter is simply wrong IMO. For stand-alone mojo execution,
> a plugin should not mess with Maven Site's default directory. Imagine a
> situation in which each module should get its own, self-consistent report
> when called stand-alone, but the site should contain an aggregate with a
> different structure or maybe no report from that plugin at all. The default
> would then pollute the site directory. This is why on the ML I asked you
> ([~michaelo]), if overriding a {{@Parameter}} annotation on a base class
> field by another {{@Parameter}} annotation on a setter in a subclass it is
> the right or canonical way to implement such a default override.
> BTW, like I also said before, Maven Javadoc Plugin, even though it does not
> use the abstract base class, implements the default correctly: build dir for
> stand-alone, report dir in site generation context.
> {quote}
> The javadoc is, BTW, still correct and does not need to be changed: In a site
> generation context, the reporting base directory will be set here
> automatically without any further changes due to:
> {code:java}
> @Override
> public void setReportOutputDirectory(File reportOutputDirectory) {
> this.reportOutputDirectory = reportOutputDirectory;
> this.outputDirectory = reportOutputDirectory;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1327] Change output directory default [maven-reporting-impl]
kriegaex commented on PR #26: URL: https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1797056331 > would you keep it in the build output dir directory? What is your opinion on the clutter? My use case with AspectJ reporting is a multi-page report, for which always a subdirectory is created anyway. Honestly, when fixing the ITs here, I did not check whether there was additional clutter written into the build directory, because I think that each mojo writing more than a single file - say PDF, HTML or whatever - ought to take care of creating a subdir for itself anyway, because the same clutter would also end up in the reporting directory with the old default, dangerously mixing with the output of other plugins. So arguably, the demo plugin in the IT does not behave well. -- 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 junitVersion from 5.10.0 to 5.10.1 [maven-doxia-sitetools]
dependabot[bot] opened a new pull request, #117: URL: https://github.com/apache/maven-doxia-sitetools/pull/117 Bumps `junitVersion` from 5.10.0 to 5.10.1. Updates `org.junit.jupiter:junit-jupiter-api` from 5.10.0 to 5.10.1 Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit.jupiter:junit-jupiter-api's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>compare view Updates `org.junit.jupiter:junit-jupiter-engine` from 5.10.0 to 5.10.1 Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit.jupiter:junit-jupiter-engine's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI pas
[PR] Bump org.junit.jupiter:junit-jupiter-api from 5.10.0 to 5.10.1 [maven-dependency-tree]
dependabot[bot] opened a new pull request, #41: URL: https://github.com/apache/maven-dependency-tree/pull/41 Bumps [org.junit.jupiter:junit-jupiter-api](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit.jupiter:junit-jupiter-api's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.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) -- 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-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783397#comment-17783397 ] ASF GitHub Bot commented on MNG-7909: - cstamas commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796964259 > Wasn't this one solved by #893 ? WILL be solved when merged, yes :smile: > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-9 > > > Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, > like transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7909] Upgrade to Resolver 2.0.0-alpha-1 [maven]
cstamas commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796964259 > Wasn't this one solved by #893 ? WILL be solved when merged, yes :smile: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-527) broken link to settings-1.3.0.xsd
[
https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783396#comment-17783396
]
ASF GitHub Bot commented on MNGSITE-527:
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796960251
I'm slightly worried about publishing unstable XSDs. This may cause problem
is the next 4.0.0 alpha/beta/milestone release does actually change it. Users
may have the schema cached by their IDE already. A safe way would be to bump
the version of the schemas if they changed in a future release, irrespective of
its alpha status. Another one would be to publish those with `-alpha-8` or
maybe just `alpha` in their file name, so something like
`maven-4.1.0-alpha-8.xsd`... ?
> broken link to settings-1.3.0.xsd
> -
>
> Key: MNGSITE-527
> URL: https://issues.apache.org/jira/browse/MNGSITE-527
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Filipe Roque
>Priority: Major
>
> The url of the XSD mentioned in the settings.xml settings tag is broken in
> Maven 4
> {code:java}
> http://maven.apache.org/SETTINGS/1.3.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.3.0
> https://maven.apache.org/xsd/settings-1.3.0.xsd";> {code}
> Both the settings.xml found at apache-maven-4.0.0-alpha-8/conf/settings.xml
> and at https://maven.apache.org/ref/4-LATEST/maven-settings/settings.html
> reference a broken url.
> There are older Versions at [http://maven.apache.org/xsd/].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] MNGSITE-527 broken link to settings-1.3.0.xsd [maven-site]
gnodet commented on PR #464: URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796960251 I'm slightly worried about publishing unstable XSDs. This may cause problem is the next 4.0.0 alpha/beta/milestone release does actually change it. Users may have the schema cached by their IDE already. A safe way would be to bump the version of the schemas if they changed in a future release, irrespective of its alpha status. Another one would be to publish those with `-alpha-8` or maybe just `alpha` in their file name, so something like `maven-4.1.0-alpha-8.xsd`... ? -- 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-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783392#comment-17783392 ] ASF GitHub Bot commented on MNG-7909: - gnodet commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796850539 > * we know about MavenITmng5669ReadPomsOnce, there is issue in model builder when using MT collector (and resolver 2.0.0 makes BF default that is MT) Wasn't this one solved by #893 ? > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-9 > > > Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, > like transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MNG-7909] Upgrade to Resolver 2.0.0-alpha-1 [maven]
gnodet commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796850539 > * we know about MavenITmng5669ReadPomsOnce, there is issue in model builder when using MT collector (and resolver 2.0.0 makes BF default that is MT) Wasn't this one solved by #893 ? -- 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-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783391#comment-17783391 ] ASF GitHub Bot commented on MNG-7909: - cstamas commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796837365 On Java 11 IT failures are: ``` Error: Failures: Error: MavenITmng4368TimestampAwareArtifactInstallerTest.testitJarPackaging:153->AbstractMavenIntegrationTestCase.assertFalse:363->AbstractMavenIntegrationTestCase.assertFalse:367 expected: but was: Error: MavenITmng5669ReadPomsOnce.testWithBuildConsumer:114->AbstractMavenIntegrationTestCase.assertTrue:359 Duplicate items: org.apache.maven:maven:3.2.5 org.apache.commons:commons-parent:52 org.codehaus.plexus:plexus:10 ==> expected: but was: Error: MavenITmng5669ReadPomsOnce.testWithoutBuildConsumer:78->AbstractMavenIntegrationTestCase.assertTrue:359 Duplicate items: org.apache.commons:commons-parent:52 org.apache:apache:15 org.apache.maven:maven-parent:25 ==> expected: but was: Error: Errors: Error: MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings:124 » Verification Text not found in log: Read timed out MavenITmng7470ResolverTransportTest.testResolverTransportDefault:106->performTest:97 » Verification Text not found in log: [DEBUG] Using transporter HttpTransporter [INFO] Error: Tests run: 904, Failures: 3, Errors: 2, Skipped: 34 ``` Info: * we know about MavenITmng5669ReadPomsOnce, there is issue in model builder when using MT collector (and resolver 2.0.0 makes BF default that is MT) * MavenITmng5175WagonHttpTest is strange, is called "Wagon" but asserts that "apache" transport is used (is not, on Java11+ is jdk used) * the only questionable is MavenITmng4368TimestampAwareArtifactInstallerTest > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-9 > > > Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, > like transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] MNGSITE-527 broken link to settings-1.3.0.xsd [maven-site]
gnodet commented on PR #464: URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796832812 The `plugin-[version].xsd` schemas are currently not published, so don't bother with those. -- 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-7909] Upgrade to Resolver 2.0.0-alpha-1 [maven]
cstamas commented on PR #1282: URL: https://github.com/apache/maven/pull/1282#issuecomment-1796837365 On Java 11 IT failures are: ``` Error: Failures: Error: MavenITmng4368TimestampAwareArtifactInstallerTest.testitJarPackaging:153->AbstractMavenIntegrationTestCase.assertFalse:363->AbstractMavenIntegrationTestCase.assertFalse:367 expected: but was: Error: MavenITmng5669ReadPomsOnce.testWithBuildConsumer:114->AbstractMavenIntegrationTestCase.assertTrue:359 Duplicate items: org.apache.maven:maven:3.2.5 org.apache.commons:commons-parent:52 org.codehaus.plexus:plexus:10 ==> expected: but was: Error: MavenITmng5669ReadPomsOnce.testWithoutBuildConsumer:78->AbstractMavenIntegrationTestCase.assertTrue:359 Duplicate items: org.apache.commons:commons-parent:52 org.apache:apache:15 org.apache.maven:maven-parent:25 ==> expected: but was: Error: Errors: Error: MavenITmng5175WagonHttpTest.testmng5175_ReadTimeOutFromSettings:124 » Verification Text not found in log: Read timed out MavenITmng7470ResolverTransportTest.testResolverTransportDefault:106->performTest:97 » Verification Text not found in log: [DEBUG] Using transporter HttpTransporter [INFO] Error: Tests run: 904, Failures: 3, Errors: 2, Skipped: 34 ``` Info: * we know about MavenITmng5669ReadPomsOnce, there is issue in model builder when using MT collector (and resolver 2.0.0 makes BF default that is MT) * MavenITmng5175WagonHttpTest is strange, is called "Wagon" but asserts that "apache" transport is used (is not, on Java11+ is jdk used) * the only questionable is MavenITmng4368TimestampAwareArtifactInstallerTest -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNGSITE-527) broken link to settings-1.3.0.xsd
[
https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783390#comment-17783390
]
ASF GitHub Bot commented on MNGSITE-527:
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796832812
The `plugin-[version].xsd` schemas are currently not published, so don't
bother with those.
> broken link to settings-1.3.0.xsd
> -
>
> Key: MNGSITE-527
> URL: https://issues.apache.org/jira/browse/MNGSITE-527
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Filipe Roque
>Priority: Major
>
> The url of the XSD mentioned in the settings.xml settings tag is broken in
> Maven 4
> {code:java}
> http://maven.apache.org/SETTINGS/1.3.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.3.0
> https://maven.apache.org/xsd/settings-1.3.0.xsd";> {code}
> Both the settings.xml found at apache-maven-4.0.0-alpha-8/conf/settings.xml
> and at https://maven.apache.org/ref/4-LATEST/maven-settings/settings.html
> reference a broken url.
> There are older Versions at [http://maven.apache.org/xsd/].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-dependency-plugin]
dependabot[bot] opened a new pull request, #348: URL: https://github.com/apache/maven-dependency-plugin/pull/348 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>org.codehaus.plexus:plexus-archiver's releases. 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 Update info about release notes in README, ReleaseNotes (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/308";>#308) https://github.com/slawekjaranowski";>@slawekjaranowski Commits https://github.com/codehaus-plexus/plexus-archiver/commit/b31477fb321484a115fcfa44d0f6b6cb0a902d8c";>b31477f [maven-release-plugin] prepare release plexus-archiver-4.9.0 https://github.com/codehaus-plexus/plexus-archiver/commit/87f62d5ffed709dc0d429d643b2f064dc84ee2ad";>87f62d5 Update info about release notes in README, ReleaseNotes https://github.com/codehaus-plexus/plexus-archiver/commit/36ccab0f67aa9cce5440498c8d48c11646625bd0";>36ccab0 Bump com.github.luben:zstd-jni from 1.5.5-6 to 1.5.5-10 https://github.com/codehaus-plexus/plexus-archiver/commit/25ed6df1dd1cbfba7951be6be2b5175888fe94cb";>25ed6df Allow copy all files without timestamp checking by DirectoryArchiver https://github.com/codehaus-plexus/plexus-archiver/commit/991aa4c7f4037e7722deeae869b82d81d8c7c25d";>991aa4c Bump commons-io:commons-io from 2.14.0 to 2.15.0 https://github.com/codehaus-plexus/plexus-archiver/commit/d17943230b0d18debf101e15ad825bcc238090b9";>d179432 Cleanup after parent pom update https://github.com/codehaus-plexus/plexus-archiver/commit/1fe44623b248be56d63f5ee17195e7e131df16e2";>1fe4462 Bump org.codehaus.plexus:plexus from 14 to 15 https://github.com/codehaus-plexus/plexus-archiver/commit/145128f9601e7be9114fba2e9fabd96dec9ab620";>145128f Bump com.github.luben:zstd-jni from 1.5.5-5 to 1.5.5-6 https://github.com/codehaus-plexus/plexus-archiver/commit/26c0b0469757eaeaf5fe5b12e03d34230f0b4f45";>26c0b04 Bump commons-io:commons-io from 2.13.0 to 2.14.0 https://github.com/codehaus-plexus/plexus-archiver/commit/8ebec4327f8b19af449c0e8f48c3a9d4fbc93200";>8ebec43 Bump org.apache.commons:commons-compress from 1.23.0 to 1.24.0 Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.8.0...plexus-archiver-4.9.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
[jira] [Commented] (MNGSITE-527) broken link to settings-1.3.0.xsd
[
https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783386#comment-17783386
]
ASF GitHub Bot commented on MNGSITE-527:
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796639967
The two missing XSDs should now be available by building maven master branch.
> broken link to settings-1.3.0.xsd
> -
>
> Key: MNGSITE-527
> URL: https://issues.apache.org/jira/browse/MNGSITE-527
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Filipe Roque
>Priority: Major
>
> The url of the XSD mentioned in the settings.xml settings tag is broken in
> Maven 4
> {code:java}
> http://maven.apache.org/SETTINGS/1.3.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.3.0
> https://maven.apache.org/xsd/settings-1.3.0.xsd";> {code}
> Both the settings.xml found at apache-maven-4.0.0-alpha-8/conf/settings.xml
> and at https://maven.apache.org/ref/4-LATEST/maven-settings/settings.html
> reference a broken url.
> There are older Versions at [http://maven.apache.org/xsd/].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] MNGSITE-527 broken link to settings-1.3.0.xsd [maven-site]
gnodet commented on PR #464: URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796639967 The two missing XSDs should now be available by building maven master branch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Fix Version/s: 4.0.0-alpha-9 (was: 4.0.x-candidate) > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.0-alpha-9 > > > Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, > like transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-7909: Assignee: Tamas Cservenak > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate > > > Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, > like transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Description: Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, like transport) becomes possible, so upgrade as well. (was: Post alpha-8 a release of Resolver 2.0.0 (depending on other work, like transport) becomes possible, so upgrade as well.) > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate > > > Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, > like transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1
[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Summary: Upgrade to Resolver 2.0.0-alpha-1 (was: Upgrade to Resolver 2.0.0) > Upgrade to Resolver 2.0.0-alpha-1 > - > > Key: MNG-7909 > URL: https://issues.apache.org/jira/browse/MNG-7909 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories >Reporter: Tamas Cservenak >Priority: Major > Fix For: 4.0.x-candidate > > > Post alpha-8 a release of Resolver 2.0.0 (depending on other work, like > transport) becomes possible, so upgrade as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-1327) Change output directory default in AbstractMavenReport
[
https://issues.apache.org/jira/browse/MSHARED-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783382#comment-17783382
]
ASF GitHub Bot commented on MSHARED-1327:
-
michael-o commented on PR #26:
URL:
https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1796462318
@kriegaex I have rebased this PR.
Here is the output when there is no subdir:
```
D:\Entwicklung\Projekte\maven-reporting-impl [patch-1 ≡ +2 ~0 -0 !]> ls
D:\Entwicklung\Projekte\maven-reporting-impl\target\it\use-as-direct-mojo\target
Directory:
D:\Entwicklung\Projekte\maven-reporting-impl\target\it\use-as-direct-mojo\target
Mode LastWriteTime Length Name
--
> Change output directory default in AbstractMavenReport
> --
>
> Key: MSHARED-1327
> URL: https://issues.apache.org/jira/browse/MSHARED-1327
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-reporting-impl
>Affects Versions: maven-reporting-impl-4.0.0-M11
>Reporter: Alexander Kriegisch
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-impl-4.0.0-M12
>
>
> The output directory should default to {{${project.build.directory}}} instead
> of {{${project.reporting.outputDirectory}}}. Quoting my reasoning from
> https://github.com/apache/maven-jxr/commit/ae81a34ac616bf7e4ea4fa9d4eb09f0979eaccb1#commitcomment-130639906:
> {quote}
> (...) because the latter is simply wrong IMO. For stand-alone mojo execution,
> a plugin should not mess with Maven Site's default directory. Imagine a
> situation in which each module should get its own, self-consistent report
> when called stand-alone, but the site should contain an aggregate with a
> different structure or maybe no report from that plugin at all. The default
> would then pollute the site directory. This is why on the ML I asked you
> ([~michaelo]), if overriding a {{@Parameter}} annotation on a base class
> field by another {{@Parameter}} annotation on a setter in a subclass it is
> the right or canonical way to implement such a default override.
> BTW, like I also said before, Maven Javadoc Plugin, even though it does not
> use the abstract base class, implements the default correctly: build dir for
> stand-alone, report dir in site generation context.
> {quote}
> The javadoc is, BTW, still correct and does not need to be changed: In a site
> generation context, the reporting base directory will be set here
> automatically without any further changes due to:
> {code:java}
> @Override
> public void setReportOutputDirectory(File reportOutputDirectory) {
> this.reportOutputDirectory = reportOutputDirectory;
> this.outputDirectory = reportOutputDirectory;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1327] Change output directory default [maven-reporting-impl]
michael-o commented on PR #26:
URL:
https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1796462318
@kriegaex I have rebased this PR.
Here is the output when there is no subdir:
```
D:\Entwicklung\Projekte\maven-reporting-impl [patch-1 ≡ +2 ~0 -0 !]> ls
D:\Entwicklung\Projekte\maven-reporting-impl\target\it\use-as-direct-mojo\target
Directory:
D:\Entwicklung\Projekte\maven-reporting-impl\target\it\use-as-direct-mojo\target
Mode LastWriteTime Length Name
- --
d 2023-11-0622:04css
d 2023-11-0622:05external
d 2023-11-0622:04fonts
d 2023-11-0622:04images
d 2023-11-0622:04img
d 2023-11-0622:04js
-a--- 2023-11-0622:04 2301
custom-report-with-renderer.html
-a--- 2023-11-0622:04 2094 custom-report.html
```
all in target. Not ideal.
@hboutemy What is your opinion? I still would prefer a subdir. @kriegaex,
would you keep it in the build output dir directory? What is your opinion on
the clutter?
--
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-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class
[
https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHARED-1326.
---
Resolution: Fixed
Fixed with
[65e9ed4606bfe902d2f340a78a1e376a34c11ad3|https://gitbox.apache.org/repos/asf?p=maven-reporting-api.git;a=commit;h=65e9ed4606bfe902d2f340a78a1e376a34c11ad3]
for maven-reporting-api and with
[cdf9631120a223b3b3cc740689c42729a50c63c5|https://gitbox.apache.org/repos/asf?p=maven-reporting-impl.git;a=commit;h=cdf9631120a223b3b3cc740689c42729a50c63c5]
for maven-reporting-impl.
> Improve (documentation on) MavenReport interface/AbstractMavenReport class
> --
>
> Key: MSHARED-1326
> URL: https://issues.apache.org/jira/browse/MSHARED-1326
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-reporting-api
>Affects Versions: maven-reporting-impl-4.0.0-M11,
> maven-reporting-api-4.0.0-M8
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-api-4.0.0-M9,
> maven-reporting-impl-4.0.0-M12
>
>
> Based on a
> [discussion|https://lists.apache.org/thread/6yxlvbhb7odfylfgjgzbvmvxg0vry20b]
> with [~kriegaex], there are few conceptional or documentational issues with
> the {{MavenReport}} interface:
> * {{#getOutputName()}} does not clearly say that is actually an optional base
> *path* and base name (base location) of the report item from a reporting
> output directory. It needs at least a doc update and maybe even a rename to
> {{#getOutputPath()}}/{{#getOutputPathLocation()}}?
> * Both {{#setReportOutputDirectory(File outputDirectory)}} and
> {{#getReportOutputDirectory()}} documentation imply that this directory
> solely refers to this single report, but that is not correct. It refers to
> root directory which contains all possibly generated reports. A shared
> directory, not exclusive one. Consider your report generates in a subdir,
> then these do *not* refer to it, but to its parent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MSHARED-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class
[
https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783373#comment-17783373
]
ASF GitHub Bot commented on MSHARED-1326:
-
asfgit closed pull request #25: [MSHARED-1326] Improve (documentation on)
AbstractMavenReport class
URL: https://github.com/apache/maven-reporting-impl/pull/25
> Improve (documentation on) MavenReport interface/AbstractMavenReport class
> --
>
> Key: MSHARED-1326
> URL: https://issues.apache.org/jira/browse/MSHARED-1326
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-reporting-api
>Affects Versions: maven-reporting-impl-4.0.0-M11,
> maven-reporting-api-4.0.0-M8
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-api-4.0.0-M9,
> maven-reporting-impl-4.0.0-M12
>
>
> Based on a
> [discussion|https://lists.apache.org/thread/6yxlvbhb7odfylfgjgzbvmvxg0vry20b]
> with [~kriegaex], there are few conceptional or documentational issues with
> the {{MavenReport}} interface:
> * {{#getOutputName()}} does not clearly say that is actually an optional base
> *path* and base name (base location) of the report item from a reporting
> output directory. It needs at least a doc update and maybe even a rename to
> {{#getOutputPath()}}/{{#getOutputPathLocation()}}?
> * Both {{#setReportOutputDirectory(File outputDirectory)}} and
> {{#getReportOutputDirectory()}} documentation imply that this directory
> solely refers to this single report, but that is not correct. It refers to
> root directory which contains all possibly generated reports. A shared
> directory, not exclusive one. Consider your report generates in a subdir,
> then these do *not* refer to it, but to its parent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1326] Improve (documentation on) AbstractMavenReport class [maven-reporting-impl]
asfgit closed pull request #25: [MSHARED-1326] Improve (documentation on) AbstractMavenReport class URL: https://github.com/apache/maven-reporting-impl/pull/25 -- 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-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class
[
https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783371#comment-17783371
]
ASF GitHub Bot commented on MSHARED-1326:
-
asfgit closed pull request #19: [MSHARED-1326] Improve (documentation on)
MavenReport interface
URL: https://github.com/apache/maven-reporting-api/pull/19
> Improve (documentation on) MavenReport interface/AbstractMavenReport class
> --
>
> Key: MSHARED-1326
> URL: https://issues.apache.org/jira/browse/MSHARED-1326
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-reporting-api
>Affects Versions: maven-reporting-impl-4.0.0-M11,
> maven-reporting-api-4.0.0-M8
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-api-4.0.0-M9,
> maven-reporting-impl-4.0.0-M12
>
>
> Based on a
> [discussion|https://lists.apache.org/thread/6yxlvbhb7odfylfgjgzbvmvxg0vry20b]
> with [~kriegaex], there are few conceptional or documentational issues with
> the {{MavenReport}} interface:
> * {{#getOutputName()}} does not clearly say that is actually an optional base
> *path* and base name (base location) of the report item from a reporting
> output directory. It needs at least a doc update and maybe even a rename to
> {{#getOutputPath()}}/{{#getOutputPathLocation()}}?
> * Both {{#setReportOutputDirectory(File outputDirectory)}} and
> {{#getReportOutputDirectory()}} documentation imply that this directory
> solely refers to this single report, but that is not correct. It refers to
> root directory which contains all possibly generated reports. A shared
> directory, not exclusive one. Consider your report generates in a subdir,
> then these do *not* refer to it, but to its parent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MSHARED-1326] Improve (documentation on) MavenReport interface [maven-reporting-api]
asfgit closed pull request #19: [MSHARED-1326] Improve (documentation on) MavenReport interface URL: https://github.com/apache/maven-reporting-api/pull/19 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-426) Move some HTTP configuration properties from transport-http
[ https://issues.apache.org/jira/browse/MRESOLVER-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783364#comment-17783364 ] Slawomir Jaranowski commented on MRESOLVER-426: --- We should consider to easy use common configurations in Maven settings - MNG-7849 > Move some HTTP configuration properties from transport-http > --- > > Key: MRESOLVER-426 > URL: https://issues.apache.org/jira/browse/MRESOLVER-426 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > As they are not ASF HttpClient specific, but could be reused by other > implementations as well, like bind address, support WebDAV, > preemprtivePutAuth... -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]
cstamas commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383907491 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: Sadly, modello "version range" predates (AFAIK, someone may correct me) Maven ranges, and has totally different syntax... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]
kwin commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383904826 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: Ah, sorry. I get it now. I thought this element was for documentation purposes -- 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.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-archiver]
dependabot[bot] opened a new pull request, #44: URL: https://github.com/apache/maven-archiver/pull/44 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>org.codehaus.plexus:plexus-archiver's releases. 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 Update info about release notes in README, ReleaseNotes (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/308";>#308) https://github.com/slawekjaranowski";>@slawekjaranowski Commits https://github.com/codehaus-plexus/plexus-archiver/commit/b31477fb321484a115fcfa44d0f6b6cb0a902d8c";>b31477f [maven-release-plugin] prepare release plexus-archiver-4.9.0 https://github.com/codehaus-plexus/plexus-archiver/commit/87f62d5ffed709dc0d429d643b2f064dc84ee2ad";>87f62d5 Update info about release notes in README, ReleaseNotes https://github.com/codehaus-plexus/plexus-archiver/commit/36ccab0f67aa9cce5440498c8d48c11646625bd0";>36ccab0 Bump com.github.luben:zstd-jni from 1.5.5-6 to 1.5.5-10 https://github.com/codehaus-plexus/plexus-archiver/commit/25ed6df1dd1cbfba7951be6be2b5175888fe94cb";>25ed6df Allow copy all files without timestamp checking by DirectoryArchiver https://github.com/codehaus-plexus/plexus-archiver/commit/991aa4c7f4037e7722deeae869b82d81d8c7c25d";>991aa4c Bump commons-io:commons-io from 2.14.0 to 2.15.0 https://github.com/codehaus-plexus/plexus-archiver/commit/d17943230b0d18debf101e15ad825bcc238090b9";>d179432 Cleanup after parent pom update https://github.com/codehaus-plexus/plexus-archiver/commit/1fe44623b248be56d63f5ee17195e7e131df16e2";>1fe4462 Bump org.codehaus.plexus:plexus from 14 to 15 https://github.com/codehaus-plexus/plexus-archiver/commit/145128f9601e7be9114fba2e9fabd96dec9ab620";>145128f Bump com.github.luben:zstd-jni from 1.5.5-5 to 1.5.5-6 https://github.com/codehaus-plexus/plexus-archiver/commit/26c0b0469757eaeaf5fe5b12e03d34230f0b4f45";>26c0b04 Bump commons-io:commons-io from 2.13.0 to 2.14.0 https://github.com/codehaus-plexus/plexus-archiver/commit/8ebec4327f8b19af449c0e8f48c3a9d4fbc93200";>8ebec43 Bump org.apache.commons:commons-compress from 1.23.0 to 1.24.0 Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.8.0...plexus-archiver-4.9.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@depend
[PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [maven-archiver]
dependabot[bot] opened a new pull request, #43: URL: https://github.com/apache/maven-archiver/pull/43 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit:junit-bom's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.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) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]
gnodet commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383873531 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: This is closed ranged version notation. That's defined by modello... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]
kwin commented on code in PR #1297: URL: https://github.com/apache/maven/pull/1297#discussion_r1383859037 ## api/maven-api-model/src/main/mdo/maven.mdo: ## @@ -387,7 +388,7 @@ - 4.0.0/4.1.0 + 4.0.0/4.0.99 Review Comment: @gnodet What is this supposed to mean? -- 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.junit:junit-bom from 5.9.3 to 5.10.0 [maven-surefire]
dependabot[bot] closed pull request #679: Bump org.junit:junit-bom from 5.9.3 to 5.10.0 URL: https://github.com/apache/maven-surefire/pull/679 -- 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.junit:junit-bom from 5.9.3 to 5.10.0 [maven-surefire]
dependabot[bot] commented on PR #679: URL: https://github.com/apache/maven-surefire/pull/679#issuecomment-1796041223 Superseded by #685. -- 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.junit:junit-bom from 5.9.3 to 5.10.1 [maven-surefire]
dependabot[bot] opened a new pull request, #685: URL: https://github.com/apache/maven-surefire/pull/685 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.9.3 to 5.10.1. Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit:junit-bom's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 JUnit 5.10.0 = Platform 1.10.0 + Jupiter 5.10.0 + Vintage 5.10.0 See http://junit.org/junit5/docs/5.10.0/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0-RC2...r5.10.0";>https://github.com/junit-team/junit5/compare/r5.10.0-RC2...r5.10.0 JUnit 5.10.0-RC2 = Platform 1.10.0-RC2+ Jupiter 5.10.0-RC2 + Vintage 5.10.0-RC2 See http://junit.org/junit5/docs/5.10.0-RC2/release-notes/";>Release Notes. JUnit 5.10.0-RC1 = Platform 1.10.0-RC1 + Jupiter 5.10.0-RC1 + Vintage 5.10.0-RC1 See http://junit.org/junit5/docs/5.10.0-RC1/release-notes/";>Release Notes. JUnit 5.10.0-M1 = Platform 1.10.0-M1 + Jupiter 5.10.0-M1 + Vintage 5.10.0-M1 See http://junit.org/junit5/docs/5.10.0-M1/release-notes/";>Release Notes. Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.9.3...r5.10.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) -- This is an automated message from
Re: [PR] Use 4.0.99 as as intermediate model to keep 4.1.0 for the Maven 4.x model [maven]
gnodet merged PR #1297: URL: https://github.com/apache/maven/pull/1297 -- 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] (MANTRUN-239) Update parent pom to 40
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MANTRUN-239: - Summary: Update parent pom to 40 (was: Update parent pom to 39) > Update parent pom to 40 > --- > > Key: MANTRUN-239 > URL: https://issues.apache.org/jira/browse/MANTRUN-239 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MANTRUN-239) Update parent pom to 39
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783339#comment-17783339 ] ASF GitHub Bot commented on MANTRUN-239: slachiewicz merged PR #88: URL: https://github.com/apache/maven-antrun-plugin/pull/88 > Update parent pom to 39 > --- > > Key: MANTRUN-239 > URL: https://issues.apache.org/jira/browse/MANTRUN-239 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MANTRUN-239] Upgrade parent pom to 40 [maven-antrun-plugin]
slachiewicz merged PR #88: URL: https://github.com/apache/maven-antrun-plugin/pull/88 -- 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] (MANTRUN-241) Update junit to 5.10.1
[ https://issues.apache.org/jira/browse/MANTRUN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783335#comment-17783335 ] ASF GitHub Bot commented on MANTRUN-241: slachiewicz merged PR #89: URL: https://github.com/apache/maven-antrun-plugin/pull/89 > Update junit to 5.10.1 > -- > > Key: MANTRUN-241 > URL: https://issues.apache.org/jira/browse/MANTRUN-241 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MANTRUN-241) Update junit to 5.10.1
[ https://issues.apache.org/jira/browse/MANTRUN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MANTRUN-241. Assignee: Sylwester Lachiewicz Resolution: Fixed > Update junit to 5.10.1 > -- > > Key: MANTRUN-241 > URL: https://issues.apache.org/jira/browse/MANTRUN-241 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [MANTRUN-241] Bump org.junit.jupiter:junit-jupiter-engine to 5.10.1 [maven-antrun-plugin]
slachiewicz merged PR #89: URL: https://github.com/apache/maven-antrun-plugin/pull/89 -- 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 xmlunit-matchers from 2.9.0 to 2.9.1 [maven-antrun-plugin]
elharo merged PR #83: URL: https://github.com/apache/maven-antrun-plugin/pull/83 -- 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 xmlunit-core from 2.9.0 to 2.9.1 [maven-antrun-plugin]
elharo merged PR #84: URL: https://github.com/apache/maven-antrun-plugin/pull/84 -- 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 xmlunit-matchers from 2.9.0 to 2.9.1 [maven-antrun-plugin]
slachiewicz commented on PR #83: URL: https://github.com/apache/maven-antrun-plugin/pull/83#issuecomment-1795800107 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MANTRUN-241) Update junit to 5.10.1
[ https://issues.apache.org/jira/browse/MANTRUN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783321#comment-17783321 ] ASF GitHub Bot commented on MANTRUN-241: slachiewicz opened a new pull request, #89: URL: https://github.com/apache/maven-antrun-plugin/pull/89 (no comment) > Update junit to 5.10.1 > -- > > Key: MANTRUN-241 > URL: https://issues.apache.org/jira/browse/MANTRUN-241 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump xmlunit-core from 2.9.0 to 2.9.1 [maven-antrun-plugin]
slachiewicz commented on PR #84: URL: https://github.com/apache/maven-antrun-plugin/pull/84#issuecomment-1795798951 @dependabot rebase -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MANTRUN-239) Update parent pom to 39
[ https://issues.apache.org/jira/browse/MANTRUN-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783320#comment-17783320 ] ASF GitHub Bot commented on MANTRUN-239: slachiewicz opened a new pull request, #88: URL: https://github.com/apache/maven-antrun-plugin/pull/88 (no comment) > Update parent pom to 39 > --- > > Key: MANTRUN-239 > URL: https://issues.apache.org/jira/browse/MANTRUN-239 > Project: Maven Antrun Plugin > Issue Type: Dependency upgrade >Reporter: Elliotte Rusty Harold >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MANTRUN-241) Update junit to 5.10.1
Sylwester Lachiewicz created MANTRUN-241: Summary: Update junit to 5.10.1 Key: MANTRUN-241 URL: https://issues.apache.org/jira/browse/MANTRUN-241 Project: Maven Antrun Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses
[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783301#comment-17783301 ] Christoph Läubrich commented on MRESOLVER-428: -- I just wanted to add a real use case where it is not the users-fault, of cause the same can happen when I use an unreleased version once and try to use it *after* it is really released... bottom line is that usually when I run the build I do it because I think I have done things right or fixed something, running a failed build faster (=with cached error) is almost never what I want... > Handle differently the "memoized HTTP 404" cached responses > --- > > Key: MRESOLVER-428 > URL: https://issues.apache.org/jira/browse/MRESOLVER-428 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > Currently, mvn local repo will "remember" that a repo reported 404 for > artifact not present, and this fact is cached using ordinary update policy. > To make mvn retry, -U is needed, that again, is too heavy handed, as it will > force update always policy for everything... -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 [maven-antrun-plugin]
dependabot[bot] commented on PR #86: URL: https://github.com/apache/maven-antrun-plugin/pull/86#issuecomment-1795613407 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.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 [maven-antrun-plugin]
slachiewicz closed pull request #86: Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 URL: https://github.com/apache/maven-antrun-plugin/pull/86 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses
[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783298#comment-17783298 ] Tamas Cservenak commented on MRESOLVER-428: --- I would leave out the "not yet synced to central" story from this, as it has many other issues as well (sadly, CENTRAL JIRA is not public, but I reported this several times): in Central _first_ the metadata is synced, and only then the content. This means that use cases like "versions display updates" would discover the not-yet-synced artifact version (as metadata is synced) while artifact content is not present. This is why maven itself is very strict with the order of deployment (metadata must be latest), but Central clearly violates this... > Handle differently the "memoized HTTP 404" cached responses > --- > > Key: MRESOLVER-428 > URL: https://issues.apache.org/jira/browse/MRESOLVER-428 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > Currently, mvn local repo will "remember" that a repo reported 404 for > artifact not present, and this fact is cached using ordinary update policy. > To make mvn retry, -U is needed, that again, is too heavy handed, as it will > force update always policy for everything... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses
[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783293#comment-17783293 ] Christoph Läubrich commented on MRESOLVER-428: -- Would be great if such a 404 is simply retried on next maven invocation, as user will see error and act on it (e.g. fix network settings, add repository, fix typo) and then retry to see everything works. Currently then user get *another error* and is confused how to fix that. Also very common case is when there is a new release and one is to eager to try it out, get 404 because it is not (yet) synced, leaving all kind of strange errors after the next run when it is there forcing to use -U to fix that up... > Handle differently the "memoized HTTP 404" cached responses > --- > > Key: MRESOLVER-428 > URL: https://issues.apache.org/jira/browse/MRESOLVER-428 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > Currently, mvn local repo will "remember" that a repo reported 404 for > artifact not present, and this fact is cached using ordinary update policy. > To make mvn retry, -U is needed, that again, is too heavy handed, as it will > force update always policy for everything... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses
Tamas Cservenak created MRESOLVER-428: - Summary: Handle differently the "memoized HTTP 404" cached responses Key: MRESOLVER-428 URL: https://issues.apache.org/jira/browse/MRESOLVER-428 Project: Maven Resolver Issue Type: Task Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0 Currently, mvn local repo will "remember" that a repo reported 404 for artifact not present, and this fact is cached using ordinary update policy. To make mvn retry, -U is needed, that again, is too heavy handed, as it will force update always policy for everything... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-427) Expose configuration for inhibiting Expect-Continue handshake
Tamas Cservenak created MRESOLVER-427: - Summary: Expose configuration for inhibiting Expect-Continue handshake Key: MRESOLVER-427 URL: https://issues.apache.org/jira/browse/MRESOLVER-427 Project: Maven Resolver Issue Type: Task Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0, 1.9.17 I consider servers claiming supporting HTTP/1.1 but "choking" on Expect-Continue a broken server, but meh... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MRESOLVER-426) Move some HTTP configuration properties from transport-http
Tamas Cservenak created MRESOLVER-426: - Summary: Move some HTTP configuration properties from transport-http Key: MRESOLVER-426 URL: https://issues.apache.org/jira/browse/MRESOLVER-426 Project: Maven Resolver Issue Type: Task Components: Resolver Reporter: Tamas Cservenak Fix For: 2.0.0 As they are not ASF HttpClient specific, but could be reused by other implementations as well, like bind address, support WebDAV, preemprtivePutAuth... -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]
gnodet commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1795431208 > > > This does not look wrong. What is the motivation behind this? > > > > > > The problem seems to be that sonatype oss release validation fail staging repositories deployed with Maven 4. The issue is there is now more than one .pom file in the repo. > > That really feels like fixing the symptom... It is. Maybe we should just do nothing and let Sonatype fix on their side ? > > > How will the attached artifact looked like if then main POM is still `foo.pom`? > > > > > > `foo-build-pom.xml` ? > > This names is reasonable since it is the original one with a classifier. Does `foo.build-pom` makes sense, too? Yes, I don't have a clear opinion. I wonder if the `-` in `build-pom` used as a classifier could cause parsing problems, as `-` is used to separate the artifactId from the classifier in `foo-build-pom.xml`... Is that why you suggested `foo.build-pom` ? I think the best would still be the current state, i.e. `foo-build.pom` ... -- 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.junit:junit-bom from 5.10.0 to 5.10.1 [maven-enforcer]
dependabot[bot] opened a new pull request, #296: URL: https://github.com/apache/maven-enforcer/pull/296 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit:junit-bom's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.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) -- 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] (SCM-1014) Enable scm changelog on files for svnexe provider
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Description: When using the maven scm changelog command in our custom maven release manager phases (used solely for svnexe provider) to check the most recent commit comment of a specific file we face the issue that we first have to do an scm info on the file and then do a scm changelog on the file's directory using the revision retrieved. This is necessary because the implementation of changelog for svnexe does ignore any file or list of files provided in the scm file set for the change log command. I would like to provide the functionality at least for a single file. Cause i do not really see the necessity to have this also for multiple files. But the svn log command supports this so if you would like me to go the whole extra mile i would try to do that, too. Since there is this info/log workaround i took the priority down a notch. was: When using the maven scm changelog command in our custom maven release manager phases (used solely for svnexe provider) to check the most recent commit comment of a specific file we face the issue that we first have to do an scm info on the file and then do a scm changelog on the file's directory using the revision retrieved. This is necessary because the implementation of changelog for svnexe does ignore any file or list of files provided in the scm file set for the change log command. I would like to provide the functionality at least for a single file. Cause i do not really see the necessity to have this also for multiple files. But the svn log command supports this so if you would like me to go the whole extra mile i would try to do that, too. > Enable scm changelog on files for svnexe provider > - > > Key: SCM-1014 > URL: https://issues.apache.org/jira/browse/SCM-1014 > Project: Maven SCM > Issue Type: Improvement >Reporter: Clemens Quoß >Priority: Minor > > When using the maven scm changelog command in our custom maven release > manager phases (used solely for svnexe provider) to check the most recent > commit comment of a specific file we face the issue that we first have to do > an scm info on the file and then do a scm changelog on the file's directory > using the revision retrieved. > This is necessary because the implementation of changelog for svnexe does > ignore any file or list of files provided in the scm file set for the change > log command. > I would like to provide the functionality at least for a single file. Cause i > do not really see the necessity to have this also for multiple files. > But the svn log command supports this so if you would like me to go the whole > extra mile i would try to do that, too. > Since there is this info/log workaround i took the priority down a notch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Affects Version/s: 2.0.1 > Enable scm changelog on files for svnexe provider > - > > Key: SCM-1014 > URL: https://issues.apache.org/jira/browse/SCM-1014 > Project: Maven SCM > Issue Type: Improvement >Affects Versions: 2.0.1 >Reporter: Clemens Quoß >Priority: Minor > > When using the maven scm changelog command in our custom maven release > manager phases (used solely for svnexe provider) to check the most recent > commit comment of a specific file we face the issue that we first have to do > an scm info on the file and then do a scm changelog on the file's directory > using the revision retrieved. > This is necessary because the implementation of changelog for svnexe does > ignore any file or list of files provided in the scm file set for the change > log command. > I would like to provide the functionality at least for a single file. Cause i > do not really see the necessity to have this also for multiple files. > But the svn log command supports this so if you would like me to go the whole > extra mile i would try to do that, too. > Since there is this info/log workaround i took the priority down a notch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Component/s: maven-scm-provider-svn > Enable scm changelog on files for svnexe provider > - > > Key: SCM-1014 > URL: https://issues.apache.org/jira/browse/SCM-1014 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-svn >Affects Versions: 2.0.1 >Reporter: Clemens Quoß >Priority: Minor > > When using the maven scm changelog command in our custom maven release > manager phases (used solely for svnexe provider) to check the most recent > commit comment of a specific file we face the issue that we first have to do > an scm info on the file and then do a scm changelog on the file's directory > using the revision retrieved. > This is necessary because the implementation of changelog for svnexe does > ignore any file or list of files provided in the scm file set for the change > log command. > I would like to provide the functionality at least for a single file. Cause i > do not really see the necessity to have this also for multiple files. > But the svn log command supports this so if you would like me to go the whole > extra mile i would try to do that, too. > Since there is this info/log workaround i took the priority down a notch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Priority: Minor (was: Major) > Enable scm changelog on files for svnexe provider > - > > Key: SCM-1014 > URL: https://issues.apache.org/jira/browse/SCM-1014 > Project: Maven SCM > Issue Type: Improvement >Reporter: Clemens Quoß >Priority: Minor > > When using the maven scm changelog command in our custom maven release > manager phases (used solely for svnexe provider) to check the most recent > commit comment of a specific file we face the issue that we first have to do > an scm info on the file and then do a scm changelog on the file's directory > using the revision retrieved. > This is necessary because the implementation of changelog for svnexe does > ignore any file or list of files provided in the scm file set for the change > log command. > I would like to provide the functionality at least for a single file. Cause i > do not really see the necessity to have this also for multiple files. > But the svn log command supports this so if you would like me to go the whole > extra mile i would try to do that, too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Description: When using the maven scm changelog command in our custom maven release manager phases (used solely for svnexe provider) to check the most recent commit comment of a specific file we face the issue that we first have to do an scm info on the file and then do a scm changelog on the file's directory using the revision retrieved. This is necessary because the implementation of changelog for svnexe does ignore any file or list of files provided in the scm file set for the change log command. I would like to provide the functionality at least for a single file. Cause i do not really see the necessity to have this also for multiple files. But the svn log command supports this so if you would like me to go the whole extra mile i would try to do that, too. was: When using the maven scm changelog command in our custom maven release manager phases (used solely for svnexe provider) to check the most recent commit comment of a specific file we face the issue that we first have to do an scm info on the file and then do a scm changelog on the file's directory using the revision retrieved. This is necessary because the implementation of changelog for svnexe does ignore any file or list of files provided in the scm file set for the change log command. I would like to provide the functionality at least for a single file. Cause i do not really the the necessity to have this also for multiple files. But the svn log command supports this so if you would like me to go the whole extra mile i would try to do that, too. > Enable scm changelog on files for svnexe provider > - > > Key: SCM-1014 > URL: https://issues.apache.org/jira/browse/SCM-1014 > Project: Maven SCM > Issue Type: Improvement >Reporter: Clemens Quoß >Priority: Major > > When using the maven scm changelog command in our custom maven release > manager phases (used solely for svnexe provider) to check the most recent > commit comment of a specific file we face the issue that we first have to do > an scm info on the file and then do a scm changelog on the file's directory > using the revision retrieved. > This is necessary because the implementation of changelog for svnexe does > ignore any file or list of files provided in the scm file set for the change > log command. > I would like to provide the functionality at least for a single file. Cause i > do not really see the necessity to have this also for multiple files. > But the svn log command supports this so if you would like me to go the whole > extra mile i would try to do that, too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SCM-1014) Enable scm changelog on files for svnexe provider
[ https://issues.apache.org/jira/browse/SCM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Quoß updated SCM-1014: -- Description: When using the maven scm changelog command in our custom maven release manager phases (used solely for svnexe provider) to check the most recent commit comment of a specific file we face the issue that we first have to do an scm info on the file and then do a scm changelog on the file's directory using the revision retrieved. This is necessary because the implementation of changelog for svnexe does ignore any file or list of files provided in the scm file set for the change log command. I would like to provide the functionality at least for a single file. Cause i do not really the the necessity to have this also for multiple files. But the svn log command supports this so if you would like me to go the whole extra mile i would try to do that, too. > Enable scm changelog on files for svnexe provider > - > > Key: SCM-1014 > URL: https://issues.apache.org/jira/browse/SCM-1014 > Project: Maven SCM > Issue Type: Improvement >Reporter: Clemens Quoß >Priority: Major > > When using the maven scm changelog command in our custom maven release > manager phases (used solely for svnexe provider) to check the most recent > commit comment of a specific file we face the issue that we first have to do > an scm info on the file and then do a scm changelog on the file's directory > using the revision retrieved. > This is necessary because the implementation of changelog for svnexe does > ignore any file or list of files provided in the scm file set for the change > log command. > I would like to provide the functionality at least for a single file. Cause i > do not really the the necessity to have this also for multiple files. > But the svn log command supports this so if you would like me to go the whole > extra mile i would try to do that, too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SCM-1014) Enable scm changelog on files for svnexe provider
Clemens Quoß created SCM-1014: - Summary: Enable scm changelog on files for svnexe provider Key: SCM-1014 URL: https://issues.apache.org/jira/browse/SCM-1014 Project: Maven SCM Issue Type: Improvement Reporter: Clemens Quoß -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MSITE-988) Documentation
[ https://issues.apache.org/jira/browse/MSITE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSITE-988: - Fix Version/s: 4.0.0-M12 > Documentation > - > > Key: MSITE-988 > URL: https://issues.apache.org/jira/browse/MSITE-988 > Project: Maven Site Plugin > Issue Type: Bug > Components: documentation >Affects Versions: 4.0.0-M9 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > Fix For: 4.0.0-M12 > > > Create old pre-version 2.0.0 model. > If using newer versions, 4.0.0-M9 to the current M11, > then an error occurs: > ``` > Site model of > 'eu.simuline.m2latex:latex-maven-plugin:maven-plugin:2.0-SNAPSHOT' > for locale 'en' is still using the old pre-version 2.0.0 model. > You MUST migrate to the new model as soon as possible > otherwise your build will break in the future! > ``` > This is due to an old form of `site.xml` > The first problem is the documentation, > `https://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html` > > which describes the old form and refers to the new one only in a link. > What would be needed is a clear statement on the mapping of the version to > the form. > Also the new form is not completely supported: > ``` >xmlns="http://maven.apache.org/SITE/2.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/SITE/2.0.0 > https://maven.apache.org/xsd/site-2.0.0.xsd";> > ... > > ``` > well, the link `https://maven.apache.org/xsd/site-2.0.0.xsd` does not exist, > resulting in a warning in my IDE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MSITE-988) Documentation
[ https://issues.apache.org/jira/browse/MSITE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSITE-988: Assignee: Michael Osipov > Documentation > - > > Key: MSITE-988 > URL: https://issues.apache.org/jira/browse/MSITE-988 > Project: Maven Site Plugin > Issue Type: Bug > Components: documentation >Affects Versions: 4.0.0-M9 >Reporter: Ernst Reissner >Assignee: Michael Osipov >Priority: Major > > Create old pre-version 2.0.0 model. > If using newer versions, 4.0.0-M9 to the current M11, > then an error occurs: > ``` > Site model of > 'eu.simuline.m2latex:latex-maven-plugin:maven-plugin:2.0-SNAPSHOT' > for locale 'en' is still using the old pre-version 2.0.0 model. > You MUST migrate to the new model as soon as possible > otherwise your build will break in the future! > ``` > This is due to an old form of `site.xml` > The first problem is the documentation, > `https://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html` > > which describes the old form and refers to the new one only in a link. > What would be needed is a clear statement on the mapping of the version to > the form. > Also the new form is not completely supported: > ``` >xmlns="http://maven.apache.org/SITE/2.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/SITE/2.0.0 > https://maven.apache.org/xsd/site-2.0.0.xsd";> > ... > > ``` > well, the link `https://maven.apache.org/xsd/site-2.0.0.xsd` does not exist, > resulting in a warning in my IDE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump org.junit.jupiter:junit-jupiter-engine from 5.9.1 to 5.10.0 [maven-antrun-plugin]
dependabot[bot] commented on PR #86: URL: https://github.com/apache/maven-antrun-plugin/pull/86#issuecomment-1794860869 A newer version of org.junit.jupiter:junit-jupiter-engine exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [maven-plugin-tools]
dependabot[bot] opened a new pull request, #238: URL: https://github.com/apache/maven-plugin-tools/pull/238 Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.0 to 5.10.1. Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit:junit-bom's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.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) -- 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.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-plugin-tools]
dependabot[bot] opened a new pull request, #237: URL: https://github.com/apache/maven-plugin-tools/pull/237 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>org.codehaus.plexus:plexus-archiver's releases. 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 Update info about release notes in README, ReleaseNotes (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/308";>#308) https://github.com/slawekjaranowski";>@slawekjaranowski Commits https://github.com/codehaus-plexus/plexus-archiver/commit/b31477fb321484a115fcfa44d0f6b6cb0a902d8c";>b31477f [maven-release-plugin] prepare release plexus-archiver-4.9.0 https://github.com/codehaus-plexus/plexus-archiver/commit/87f62d5ffed709dc0d429d643b2f064dc84ee2ad";>87f62d5 Update info about release notes in README, ReleaseNotes https://github.com/codehaus-plexus/plexus-archiver/commit/36ccab0f67aa9cce5440498c8d48c11646625bd0";>36ccab0 Bump com.github.luben:zstd-jni from 1.5.5-6 to 1.5.5-10 https://github.com/codehaus-plexus/plexus-archiver/commit/25ed6df1dd1cbfba7951be6be2b5175888fe94cb";>25ed6df Allow copy all files without timestamp checking by DirectoryArchiver https://github.com/codehaus-plexus/plexus-archiver/commit/991aa4c7f4037e7722deeae869b82d81d8c7c25d";>991aa4c Bump commons-io:commons-io from 2.14.0 to 2.15.0 https://github.com/codehaus-plexus/plexus-archiver/commit/d17943230b0d18debf101e15ad825bcc238090b9";>d179432 Cleanup after parent pom update https://github.com/codehaus-plexus/plexus-archiver/commit/1fe44623b248be56d63f5ee17195e7e131df16e2";>1fe4462 Bump org.codehaus.plexus:plexus from 14 to 15 https://github.com/codehaus-plexus/plexus-archiver/commit/145128f9601e7be9114fba2e9fabd96dec9ab620";>145128f Bump com.github.luben:zstd-jni from 1.5.5-5 to 1.5.5-6 https://github.com/codehaus-plexus/plexus-archiver/commit/26c0b0469757eaeaf5fe5b12e03d34230f0b4f45";>26c0b04 Bump commons-io:commons-io from 2.13.0 to 2.14.0 https://github.com/codehaus-plexus/plexus-archiver/commit/8ebec4327f8b19af449c0e8f48c3a9d4fbc93200";>8ebec43 Bump org.apache.commons:commons-compress from 1.23.0 to 1.24.0 Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.8.0...plexus-archiver-4.9.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@
Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]
gnodet merged PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]
gnodet commented on code in PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#discussion_r1383274777 ## core-it-suite/src/test/resources-filtered/bootstrap.txt: ## @@ -18,6 +18,8 @@ org.apache.commons:commons-text:1.10.0 org.apache.geronimo.specs:geronimo-jcdi_2.0_spec:1.3 org.apache.groovy:groovy-ant:4.0.15 org.apache.groovy:groovy:4.0.15 +org.apache.maven:maven-api-spi:4.0.0-alpha-8 +org.apache.maven:maven-api-model:4.0.0-alpha-8:mdo Review Comment: The `maven-api-core` artifact is a dependency of `maven-api-spi` (basically all other maven-api-xxx should be downloaded this way). I can be more explicit if you think it's better and list them all, but I don't really see the point in being verbose. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]
gnodet commented on code in PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#discussion_r1383274777 ## core-it-suite/src/test/resources-filtered/bootstrap.txt: ## @@ -18,6 +18,8 @@ org.apache.commons:commons-text:1.10.0 org.apache.geronimo.specs:geronimo-jcdi_2.0_spec:1.3 org.apache.groovy:groovy-ant:4.0.15 org.apache.groovy:groovy:4.0.15 +org.apache.maven:maven-api-spi:4.0.0-alpha-8 +org.apache.maven:maven-api-model:4.0.0-alpha-8:mdo Review Comment: The `maven-api-core` artifact is a dependency of `maven-api-spi` (basically all other maven-api-xxx are downloaded as transitive dependencies). I can be more explicit if you think it's better and list them all, but I don't really see the point in being verbose. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]
slawekjaranowski commented on code in PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#discussion_r1383269705 ## core-it-suite/src/test/resources-filtered/bootstrap.txt: ## @@ -18,6 +18,8 @@ org.apache.commons:commons-text:1.10.0 org.apache.geronimo.specs:geronimo-jcdi_2.0_spec:1.3 org.apache.groovy:groovy-ant:4.0.15 org.apache.groovy:groovy:4.0.15 +org.apache.maven:maven-api-spi:4.0.0-alpha-8 +org.apache.maven:maven-api-model:4.0.0-alpha-8:mdo Review Comment: maven-api-core? -- 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] (MSITE-988) Documentation
Ernst Reissner created MSITE-988: Summary: Documentation Key: MSITE-988 URL: https://issues.apache.org/jira/browse/MSITE-988 Project: Maven Site Plugin Issue Type: Bug Components: documentation Affects Versions: 4.0.0-M9 Reporter: Ernst Reissner Create old pre-version 2.0.0 model. If using newer versions, 4.0.0-M9 to the current M11, then an error occurs: ``` Site model of 'eu.simuline.m2latex:latex-maven-plugin:maven-plugin:2.0-SNAPSHOT' for locale 'en' is still using the old pre-version 2.0.0 model. You MUST migrate to the new model as soon as possible otherwise your build will break in the future! ``` This is due to an old form of `site.xml` The first problem is the documentation, `https://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html` which describes the old form and refers to the new one only in a link. What would be needed is a clear statement on the mapping of the version to the form. Also the new form is not completely supported: ``` http://maven.apache.org/SITE/2.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/SITE/2.0.0 https://maven.apache.org/xsd/site-2.0.0.xsd";> ... ``` well, the link `https://maven.apache.org/xsd/site-2.0.0.xsd` does not exist, resulting in a warning in my IDE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-5695) inconsistent custom Guice scope bindings
[
https://issues.apache.org/jira/browse/MNG-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783204#comment-17783204
]
ASF GitHub Bot commented on MNG-5695:
-
cstamas commented on code in PR #236:
URL:
https://github.com/apache/maven-plugin-tools/pull/236#discussion_r1383237666
##
maven-plugin-tools-annotations/src/site/apt/index.apt:
##
@@ -94,27 +94,42 @@ public class MyMojo
hint = "..." )
private MyComponent component;
+// pseudo-parameters (marked read-only) permitting injection of Maven
build context objects
// sample objects taken from Maven API through
PluginParameterExpressionEvaluator
+//
https://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html
+// plugins targetting Maven 3.2.5+ (after MNG-5695) should not use these
pseudo-parameters any more,
+// but @Component and Maven APIs to get better compiler-time checks
-@Parameter( defaultValue = "${session}", readonly = true )
+// @Parameter( defaultValue = "${session}", readonly = true )
+@Component // since Maven 3.2.5, thanks to MNG-5695
Review Comment:
IMHO there is no problem when JSR330 being used. Problem happens when Mojo
APIs (java5 anno or javadoc annos are being used).
> inconsistent custom Guice scope bindings
>
>
> Key: MNG-5695
> URL: https://issues.apache.org/jira/browse/MNG-5695
> Project: Maven
> Issue Type: Bug
>Reporter: Igor Fedorenko
>Assignee: igorfie
>Priority: Major
> Fix For: 3.2.5
>
>
> - Session scope ({{MavenSession}}) is only available for maven core and core
> extensions components (i.e. -Dmaven.ext.class.path stuff), but does not work
> for components from maven plugins.
> - Mojo execution scope ({{MavenProject}} and {{MojoExecution}}) works for
> components from maven plugins but not for maven core and core extensions.
> Need to consistently bind custom Guice scopes in all realms.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [MNG-5695] document Maven 3.2.5+ scoped components usage [maven-plugin-tools]
cstamas commented on code in PR #236:
URL:
https://github.com/apache/maven-plugin-tools/pull/236#discussion_r1383237666
##
maven-plugin-tools-annotations/src/site/apt/index.apt:
##
@@ -94,27 +94,42 @@ public class MyMojo
hint = "..." )
private MyComponent component;
+// pseudo-parameters (marked read-only) permitting injection of Maven
build context objects
// sample objects taken from Maven API through
PluginParameterExpressionEvaluator
+//
https://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html
+// plugins targetting Maven 3.2.5+ (after MNG-5695) should not use these
pseudo-parameters any more,
+// but @Component and Maven APIs to get better compiler-time checks
-@Parameter( defaultValue = "${session}", readonly = true )
+// @Parameter( defaultValue = "${session}", readonly = true )
+@Component // since Maven 3.2.5, thanks to MNG-5695
Review Comment:
IMHO there is no problem when JSR330 being used. Problem happens when Mojo
APIs (java5 anno or javadoc annos are being used).
--
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 junitVersion from 5.10.0 to 5.10.1 [maven-doxia]
dependabot[bot] opened a new pull request, #178: URL: https://github.com/apache/maven-doxia/pull/178 Bumps `junitVersion` from 5.10.0 to 5.10.1. Updates `org.junit.jupiter:junit-jupiter-api` from 5.10.0 to 5.10.1 Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit.jupiter:junit-jupiter-api's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>compare view Updates `org.junit.jupiter:junit-jupiter-engine` from 5.10.0 to 5.10.1 Release notes Sourced from https://github.com/junit-team/junit5/releases";>org.junit.jupiter:junit-jupiter-engine's releases. JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1 See http://junit.org/junit5/docs/5.10.1/release-notes/";>Release Notes. Full Changelog: https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1 Commits https://github.com/junit-team/junit5/commit/e5f50d8720741623915979ac154b65bcbcd6a577";>e5f50d8 Release 5.10.1 https://github.com/junit-team/junit5/commit/ac86d18e9b15dbebe046e82743ac7f9534a17582";>ac86d18 Fix typo in AfterAll documentation https://github.com/junit-team/junit5/commit/388c5beaf42944961ab5b455c900d958a6e15588";>388c5be Harmonize application of method and field filters in search algorithms https://github.com/junit-team/junit5/commit/f82dd1e716f8717e012152b1d1d5cc0da10d33cd";>f82dd1e Apply field predicate before searching type hierarchy https://github.com/junit-team/junit5/commit/1d1eb8571552bbf28e578241965010de6c8ee779";>1d1eb85 Polishing https://github.com/junit-team/junit5/commit/5ce280eff69b43759a3cb0c176207abe0a41b579";>5ce280e Update picocli to 4.7.5 and enable help width computation https://github.com/junit-team/junit5/commit/fea05c3aa80de76686f326b5ce26ddf7f153ff5a";>fea05c3 Fix ConsoleLauncherTests and StandaloneTests https://github.com/junit-team/junit5/commit/c5567354c2556e772f8a0035ef7647161011d1c0";>c556735 Use same expected files for all JDK versions https://github.com/junit-team/junit5/commit/808493ab09b30970b506a48fda3d616ac1ba4fff";>808493a Run StandaloneTests for Java 8 under Java 8 https://github.com/junit-team/junit5/commit/9ec57661c78c3889db004ab6a89416e56a2fb2e0";>9ec5766 Unify messages about exit codes in StandaloneTests Additional commits viewable in https://github.com/junit-team/junit5/compare/r5.10.0...r5.10.1";>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
Re: [PR] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]
gnodet commented on PR #315: URL: https://github.com/apache/maven-integration-testing/pull/315#issuecomment-1794672092 > Should we also add to core-it-suite/src/test/resources-filtered/bootstrap.txt? Good point. It should actually fail. I think the reason it does not is because the CI workflow for these PR only build with Maven 3.9.5 atm. We should maybe add the latest 4.x build too... -- 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] (MASSEMBLY-1002) Assembly fails to include directories when they are symbolic links
Jimisola Laursen created MASSEMBLY-1002:
---
Summary: Assembly fails to include directories when they are
symbolic links
Key: MASSEMBLY-1002
URL: https://issues.apache.org/jira/browse/MASSEMBLY-1002
Project: Maven Assembly Plugin
Issue Type: Improvement
Affects Versions: 3.6.0
Reporter: Jimisola Laursen
Assembly fails to include directories when they are symbolic links.
E.g.
If the directory "${project.basedir}/target/surefire-reports" is a symbolic
link to another directory then the following fileset will not work.
{code:java}
${project.basedir}/target/surefire-reports
/test_results/surefire
*.*
{code}
However, if the directory "${project.basedir}/target/surefire-reports" is an
actual directory (and not a symlinj ) and the files in that directory are
symbolic links then it works as expected.
I'm guessing that this might not be a bug in this plugin but rather Maven
Resources.
There is a related [issue|https://issues.apache.org/jira/browse/MRESOURCES-237]
in terms of being about symlinks, but that ticket is about preserving symbolic
links or not which in not the case here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MSHARED-1326) Improve (documentation on) MavenReport interface/AbstractMavenReport class
[
https://issues.apache.org/jira/browse/MSHARED-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHARED-1326:
Description:
Based on a
[discussion|https://lists.apache.org/thread/6yxlvbhb7odfylfgjgzbvmvxg0vry20b]
with [~kriegaex], there are few conceptional or documentational issues with the
{{MavenReport}} interface:
* {{#getOutputName()}} does not clearly say that is actually an optional base
*path* and base name (base location) of the report item from a reporting output
directory. It needs at least a doc update and maybe even a rename to
{{#getOutputPath()}}/{{#getOutputPathLocation()}}?
* Both {{#setReportOutputDirectory(File outputDirectory)}} and
{{#getReportOutputDirectory()}} documentation imply that this directory solely
refers to this single report, but that is not correct. It refers to root
directory which contains all possibly generated reports. A shared directory,
not exclusive one. Consider your report generates in a subdir, then these do
*not* refer to it, but to its parent.
was:
Based on a
[discussion|https://lists.apache.org/thread/6yxlvbhb7odfylfgjgzbvmvxg0vry20b]
with [~kriegaex], there are few conceptional or documentational issues with the
{{MavenReport}} interface:
* {{#getOutputName()}} does not clearly say that is actually an optional base
*path* and base name (base location) of the report item from a reporting output
directory. It needs at least a doc update and maybe even a rename to
{{#getOutputPath()}}/{{#getOutputPathLocation()}}?
* Both {{#setReportOutputDirectory(File outputDirectory)}} and
{{#getReportOutputDirectory()}} documentation imply tha this directory solely
refers to this single report, but that is not correct. It refers to root
directory which contains all possibly generated reports. A shared directory,
not exclusive one. Consider your report generates in a subdir, then these do
*not* refer to it, but to its parent.
> Improve (documentation on) MavenReport interface/AbstractMavenReport class
> --
>
> Key: MSHARED-1326
> URL: https://issues.apache.org/jira/browse/MSHARED-1326
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-reporting-api
>Affects Versions: maven-reporting-impl-4.0.0-M11,
> maven-reporting-api-4.0.0-M8
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: maven-reporting-api-4.0.0-M9,
> maven-reporting-impl-4.0.0-M12
>
>
> Based on a
> [discussion|https://lists.apache.org/thread/6yxlvbhb7odfylfgjgzbvmvxg0vry20b]
> with [~kriegaex], there are few conceptional or documentational issues with
> the {{MavenReport}} interface:
> * {{#getOutputName()}} does not clearly say that is actually an optional base
> *path* and base name (base location) of the report item from a reporting
> output directory. It needs at least a doc update and maybe even a rename to
> {{#getOutputPath()}}/{{#getOutputPathLocation()}}?
> * Both {{#setReportOutputDirectory(File outputDirectory)}} and
> {{#getReportOutputDirectory()}} documentation imply that this directory
> solely refers to this single report, but that is not correct. It refers to
> root directory which contains all possibly generated reports. A shared
> directory, not exclusive one. Consider your report generates in a subdir,
> then these do *not* refer to it, but to its parent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]
michael-o commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1794431344 > > This does not look wrong. What is the motivation behind this? > > The problem seems to be that sonatype oss release validation fail staging repositories deployed with Maven 4. The issue is there is now more than one .pom file in the repo. That really feels like fixing the symptom... > > How will the attached artifact looked like if then main POM is still `foo.pom`? > > `foo-build-pom.xml` ? This names is reasonable since it is the original one with a classifier. Does `foo.build-pom` makes sense, too? -- 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] Use 4.0.0-alpha-8 instead of SNAPSHOT [maven-integration-testing]
gnodet opened a new pull request, #315: URL: https://github.com/apache/maven-integration-testing/pull/315 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]
gnodet commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1794423566 > This does not look wrong. What is the motivation behind this? The problem seems to be that sonatype oss release validation fail staging repositories deployed with Maven 4. The issue is there is now more than one .pom file in the repo. > How will the attached artifact looked like if then main POM is still `foo.pom`? `foo-build-pom.xml` ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MRESOLVER-423) Remove the 3.x banner from Resolver site
[ https://issues.apache.org/jira/browse/MRESOLVER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783154#comment-17783154 ] ASF GitHub Bot commented on MRESOLVER-423: -- olamy commented on PR #354: URL: https://github.com/apache/maven-resolver/pull/354#issuecomment-1794418256 Looking at this page https://maven.apache.org/docs/history.html, we are still supporting 3.8.x > Remove the 3.x banner from Resolver site > > > Key: MRESOLVER-423 > URL: https://issues.apache.org/jira/browse/MRESOLVER-423 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 2.0.0 > > > The resolver index page starts with "Since version 1.7.0 Maven Resolver > requires Java 8 to run. For a Maven 3.8.x compatible version read here.". > Remove this, it really does not belong to Resolver 2.0.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Bump org.codehaus.plexus:plexus-archiver from 4.8.0 to 4.9.0 [maven-ear-plugin]
dependabot[bot] opened a new pull request, #98: URL: https://github.com/apache/maven-ear-plugin/pull/98 Bumps [org.codehaus.plexus:plexus-archiver](https://github.com/codehaus-plexus/plexus-archiver) from 4.8.0 to 4.9.0. Release notes Sourced from https://github.com/codehaus-plexus/plexus-archiver/releases";>org.codehaus.plexus:plexus-archiver's releases. 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 Update info about release notes in README, ReleaseNotes (https://redirect.github.com/codehaus-plexus/plexus-archiver/pull/308";>#308) https://github.com/slawekjaranowski";>@slawekjaranowski Commits https://github.com/codehaus-plexus/plexus-archiver/commit/b31477fb321484a115fcfa44d0f6b6cb0a902d8c";>b31477f [maven-release-plugin] prepare release plexus-archiver-4.9.0 https://github.com/codehaus-plexus/plexus-archiver/commit/87f62d5ffed709dc0d429d643b2f064dc84ee2ad";>87f62d5 Update info about release notes in README, ReleaseNotes https://github.com/codehaus-plexus/plexus-archiver/commit/36ccab0f67aa9cce5440498c8d48c11646625bd0";>36ccab0 Bump com.github.luben:zstd-jni from 1.5.5-6 to 1.5.5-10 https://github.com/codehaus-plexus/plexus-archiver/commit/25ed6df1dd1cbfba7951be6be2b5175888fe94cb";>25ed6df Allow copy all files without timestamp checking by DirectoryArchiver https://github.com/codehaus-plexus/plexus-archiver/commit/991aa4c7f4037e7722deeae869b82d81d8c7c25d";>991aa4c Bump commons-io:commons-io from 2.14.0 to 2.15.0 https://github.com/codehaus-plexus/plexus-archiver/commit/d17943230b0d18debf101e15ad825bcc238090b9";>d179432 Cleanup after parent pom update https://github.com/codehaus-plexus/plexus-archiver/commit/1fe44623b248be56d63f5ee17195e7e131df16e2";>1fe4462 Bump org.codehaus.plexus:plexus from 14 to 15 https://github.com/codehaus-plexus/plexus-archiver/commit/145128f9601e7be9114fba2e9fabd96dec9ab620";>145128f Bump com.github.luben:zstd-jni from 1.5.5-5 to 1.5.5-6 https://github.com/codehaus-plexus/plexus-archiver/commit/26c0b0469757eaeaf5fe5b12e03d34230f0b4f45";>26c0b04 Bump commons-io:commons-io from 2.13.0 to 2.14.0 https://github.com/codehaus-plexus/plexus-archiver/commit/8ebec4327f8b19af449c0e8f48c3a9d4fbc93200";>8ebec43 Bump org.apache.commons:commons-compress from 1.23.0 to 1.24.0 Additional commits viewable in https://github.com/codehaus-plexus/plexus-archiver/compare/plexus-archiver-4.8.0...plexus-archiver-4.9.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@depe
Re: [PR] [MRESOLVER-423] Legacy promotion is no stay here [maven-resolver]
olamy commented on PR #354: URL: https://github.com/apache/maven-resolver/pull/354#issuecomment-1794418256 Looking at this page https://maven.apache.org/docs/history.html, we are still supporting 3.8.x -- 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] [test] Added Unit tests for AssemblyFileUtils, FileLocation, and Mess… [maven-assembly-plugin]
slawekjaranowski commented on PR #161: URL: https://github.com/apache/maven-assembly-plugin/pull/161#issuecomment-1794333899 @Kaushikdhola please check build output the same should be when you build project locally 😄 -- 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] Change build pom naming from xxx-build.pom to xxx-build-pom.xml [maven]
michael-o commented on PR #1298: URL: https://github.com/apache/maven/pull/1298#issuecomment-1794331534 This does not look wrong. What is the motivation behind this? How will the attached artifact looked like if then main POM is still `foo.pom`? -- 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
