[jira] [Commented] (MENFORCER-389) Exclusions are not considered when looking at parent for requireReleaseDeps
[
https://issues.apache.org/jira/browse/MENFORCER-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545297#comment-17545297
]
Hudson commented on MENFORCER-389:
--
Build failed in Jenkins: Maven » Maven TLP » maven-enforcer » master #33
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/33/
> Exclusions are not considered when looking at parent for requireReleaseDeps
> ---
>
> Key: MENFORCER-389
> URL: https://issues.apache.org/jira/browse/MENFORCER-389
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 3.0.0
>Reporter: Henri Tremblay
>Assignee: Slawomir Jaranowski
>Priority: Blocker
> Fix For: 3.0.1
>
>
> I would like to prevent parent poms to be a snapshots. But I have a
> multi-module project. The rule is this on the parent pom:
> {code:java}
>
>
> No Snapshots Allowed!
>
> ${project.groupId}:*
>
> true
>
>
> {code}
> I would expect this to fail only when the parent pom is not in my groupId.
> But it's not what it does. It just makes {{failWhenParentIsSnapshot}}
> unusable for multi-module projects.
> See [https://github.com/henri-tremblay/enforce-parent-bug] for a full project
> to reproduce. Just type {{mvn enforcer:enforce}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545300#comment-17545300
]
Herve Boutemy commented on MRELEASE-1072:
-
I want to do the release, this issue is the only one remaining, I will postpone
it
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MDEP-774) analyze-only failed: PermittedSubclasses requires ASM9
[
https://issues.apache.org/jira/browse/MDEP-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545323#comment-17545323
]
Jordan Zimmerman commented on MDEP-774:
---
Why is this marked as fixed? It's still failing for me with Java 17.0.1
> analyze-only failed: PermittedSubclasses requires ASM9
> --
>
> Key: MDEP-774
> URL: https://issues.apache.org/jira/browse/MDEP-774
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
> Environment: Maven 3.8.2, Adoptium 17, MacOS 11.6
>Reporter: Dan Ziemba
>Assignee: Sylwester Lachiewicz
>Priority: Critical
> Fix For: 3.3.0
>
>
> The analyze-only goal does not work with Java 17 bytecode:
> {noformat}
> Execution dep-analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only failed:
> PermittedSubclasses requires ASM9{noformat}
> Running the same build under the same version of Java 17, but with
> "maven.compiler.release" set to 16 works fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Comment Edited] (MDEP-774) analyze-only failed: PermittedSubclasses requires ASM9
[
https://issues.apache.org/jira/browse/MDEP-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545323#comment-17545323
]
Jordan Zimmerman edited comment on MDEP-774 at 6/2/22 7:55 AM:
---
Why is this marked as fixed? It's still failing for me with Java 17.0.1
{{Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.3.0:analyze-only failed:
PermittedSubclasses requires ASM9}}
was (Author: randgalt):
Why is this marked as fixed? It's still failing for me with Java 17.0.1
> analyze-only failed: PermittedSubclasses requires ASM9
> --
>
> Key: MDEP-774
> URL: https://issues.apache.org/jira/browse/MDEP-774
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
> Environment: Maven 3.8.2, Adoptium 17, MacOS 11.6
>Reporter: Dan Ziemba
>Assignee: Sylwester Lachiewicz
>Priority: Critical
> Fix For: 3.3.0
>
>
> The analyze-only goal does not work with Java 17 bytecode:
> {noformat}
> Execution dep-analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only failed:
> PermittedSubclasses requires ASM9{noformat}
> Running the same build under the same version of Java 17, but with
> "maven.compiler.release" set to 16 works fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MDEP-786) Sealed classes not supported
[
https://issues.apache.org/jira/browse/MDEP-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545327#comment-17545327
]
Jordan Zimmerman commented on MDEP-786:
---
It does not.
{{Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.3.0:analyze-only failed:
PermittedSubclasses requires ASM9}}
> Sealed classes not supported
>
>
> Key: MDEP-786
> URL: https://issues.apache.org/jira/browse/MDEP-786
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
>Reporter: Jordan Zimmerman
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.0
>
>
> Use of Java 17's sealed classes generates an error:
> {{PermittedSubclasses requires ASM9}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545336#comment-17545336
]
Samuel Le Berrigaud commented on MRELEASE-1072:
---
[~hboutemy] just to be clear, are you postponing the release or the issue?
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MDEP-774) analyze-only failed: PermittedSubclasses requires ASM9
[
https://issues.apache.org/jira/browse/MDEP-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545343#comment-17545343
]
Slawomir Jaranowski commented on MDEP-774:
--
[~randgalt] - Please provide minimal project which can reproduce it.
> analyze-only failed: PermittedSubclasses requires ASM9
> --
>
> Key: MDEP-774
> URL: https://issues.apache.org/jira/browse/MDEP-774
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
> Environment: Maven 3.8.2, Adoptium 17, MacOS 11.6
>Reporter: Dan Ziemba
>Assignee: Sylwester Lachiewicz
>Priority: Critical
> Fix For: 3.3.0
>
>
> The analyze-only goal does not work with Java 17 bytecode:
> {noformat}
> Execution dep-analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only failed:
> PermittedSubclasses requires ASM9{noformat}
> Running the same build under the same version of Java 17, but with
> "maven.compiler.release" set to 16 works fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MDEP-774) analyze-only failed: PermittedSubclasses requires ASM9
[
https://issues.apache.org/jira/browse/MDEP-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545363#comment-17545363
]
Jordan Zimmerman commented on MDEP-774:
---
Sorry - it was our error. Our parent pom forced the ASM version to work around
the earlier issue in the plugin. Sorry for the noise.
> analyze-only failed: PermittedSubclasses requires ASM9
> --
>
> Key: MDEP-774
> URL: https://issues.apache.org/jira/browse/MDEP-774
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
> Environment: Maven 3.8.2, Adoptium 17, MacOS 11.6
>Reporter: Dan Ziemba
>Assignee: Sylwester Lachiewicz
>Priority: Critical
> Fix For: 3.3.0
>
>
> The analyze-only goal does not work with Java 17 bytecode:
> {noformat}
> Execution dep-analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only failed:
> PermittedSubclasses requires ASM9{noformat}
> Running the same build under the same version of Java 17, but with
> "maven.compiler.release" set to 16 works fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MDEP-786) Sealed classes not supported
[
https://issues.apache.org/jira/browse/MDEP-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545364#comment-17545364
]
Jordan Zimmerman commented on MDEP-786:
---
Sorry for - it was our error. Our parent pom forced the ASM version to
work around the earlier issue in the plugin. Sorry for the noise.
> Sealed classes not supported
>
>
> Key: MDEP-786
> URL: https://issues.apache.org/jira/browse/MDEP-786
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.2.0
>Reporter: Jordan Zimmerman
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.0
>
>
> Use of Java 17's sealed classes generates an error:
> {{PermittedSubclasses requires ASM9}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (SUREFIRE-1373) Tests annotated with @NotThreadSafe are not executed in isolation
[ https://issues.apache.org/jira/browse/SUREFIRE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545389#comment-17545389 ] Plamen Tanov commented on SUREFIRE-1373: As a workaround you can use multiple executions with excluded groups, e.g. put @Test(groups="somegroup") together with @NotThreadSafe and then having two configurations like it is described here: [https://rmannibucau.metawerx.net/post/maven-surefire-debugging-execution#configure-multiple-executions] First one (or default one, outside ) with somegroup and the second one with somegroup keep in mind that @BeforeMethod of parent classes will not be called until they have alwaysRun = true (e.g. @BeforeMethod(alwaysRun=true) or @BeforeMethod(groups="somegroup") ) But yes - I expected that @NotThreadSafe will be executed at the end (after all other tests are completed) and NOT in parallel to rest of the tests. My case is the same - all tests share one DB instance (for speed optimization) and the tests that checks one statistical method (that aggregates all records in the DB) needs to be called completely separated from the rest of tests (that works on a explicitly separated data) so the data from all tests doesn't conflicts with the expected results from the first method. > Tests annotated with @NotThreadSafe are not executed in isolation > - > > Key: SUREFIRE-1373 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1373 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.20 >Reporter: Sebastian Kirsch >Assignee: Tibor Digana >Priority: Major > Fix For: Backlog > > Original Estimate: 48h > Remaining Estimate: 48h > > The [surefire > documentation|http://maven.apache.org/components/surefire/maven-failsafe-plugin/examples/fork-options-and-parallel-execution.html] > states that > bq. you can apply the JCIP annotation @net.jcip.annotations.NotThreadSafe on > the Java class of JUnit test (pure test class, Suite, Parameterized, etc.) in > order to execute it in single Thread instance. The Thread has name > maven-surefire-plugin@NotThreadSafe and it is executed at the end of the test > run. > However, the thread is run in parallel to the other tests being executed, > which contradicts the documentation and defeats the purpose of running tests > sequentially in a single thread. > See https://github.com/sebastiankirsch/surefire-nonthreadsafe for a test case. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven] cstamas merged pull request #747: [MNG-7491] Update parent POM 36
cstamas merged PR #747: URL: https://github.com/apache/maven/pull/747 -- 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-7491) Update parent POM to 36
[ https://issues.apache.org/jira/browse/MNG-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545416#comment-17545416 ] ASF GitHub Bot commented on MNG-7491: - cstamas merged PR #747: URL: https://github.com/apache/maven/pull/747 > Update parent POM to 36 > --- > > Key: MNG-7491 > URL: https://issues.apache.org/jira/browse/MNG-7491 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0 > > > Update parent POM from 35 to 36. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven] cstamas merged pull request #748: [MNG-7491] Update parent POM 36 (3.9.x)
cstamas merged PR #748: URL: https://github.com/apache/maven/pull/748 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (MNG-7491) Update parent POM to 36
[ https://issues.apache.org/jira/browse/MNG-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák resolved MNG-7491. -- Resolution: Fixed > Update parent POM to 36 > --- > > Key: MNG-7491 > URL: https://issues.apache.org/jira/browse/MNG-7491 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0 > > > Update parent POM from 35 to 36. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (MNG-7491) Update parent POM to 36
[ https://issues.apache.org/jira/browse/MNG-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamás Cservenák closed MNG-7491. > Update parent POM to 36 > --- > > Key: MNG-7491 > URL: https://issues.apache.org/jira/browse/MNG-7491 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0 > > > Update parent POM from 35 to 36. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MNG-7491) Update parent POM to 36
[ https://issues.apache.org/jira/browse/MNG-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545417#comment-17545417 ] ASF GitHub Bot commented on MNG-7491: - cstamas merged PR #748: URL: https://github.com/apache/maven/pull/748 > Update parent POM to 36 > --- > > Key: MNG-7491 > URL: https://issues.apache.org/jira/browse/MNG-7491 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0 > > > Update parent POM from 35 to 36. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-doxia] michael-o commented on a diff in pull request #104: implement hidden rows
michael-o commented on code in PR #104:
URL: https://github.com/apache/maven-doxia/pull/104#discussion_r887840744
##
doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java:
##
@@ -136,13 +139,13 @@ public Xhtml5BaseSink( Writer out )
{
this.writer = new PrintWriter( out );
-this.cellJustifStack = new LinkedList<>();
-this.isCellJustifStack = new LinkedList<>();
-this.cellCountStack = new LinkedList<>();
-this.tableContentWriterStack = new LinkedList<>();
-this.tableCaptionWriterStack = new LinkedList<>();
-this.tableCaptionXMLWriterStack = new LinkedList<>();
-this.tableCaptionStack = new LinkedList<>();
+this.cellJustifStack = new LinkedList();
+this.isCellJustifStack = new LinkedList();
+this.cellCountStack = new LinkedList();
+this.tableContentWriterStack = new LinkedList();
+this.tableCaptionWriterStack = new LinkedList();
+this.tableCaptionXMLWriterStack = new
LinkedList();
+this.tableCaptionStack = new LinkedList();
Review Comment:
Why?
##
doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java:
##
@@ -61,17 +61,20 @@
/** The PrintWriter to write the result. */
private final PrintWriter writer;
+/** Used to identify if a class string contains `hidden` */
+private static final Pattern HIDDEN_CLASS_PATTERN = Pattern.compile(
"(?:.*\\s|^)hidden(?:\\s.*|$)" );
+
/** Used to collect text events mainly for the head events. */
private StringBuffer textBuffer = new StringBuffer();
/** An indication on if we're inside a head. */
private boolean headFlag;
/** Keep track of the main and div tags for content events. */
-protected Stack contentStack = new Stack<>();
+protected Stack contentStack = new Stack();
Review Comment:
Why?
##
doxia-core/src/main/java/org/apache/maven/doxia/sink/impl/Xhtml5BaseSink.java:
##
@@ -61,17 +61,20 @@
/** The PrintWriter to write the result. */
private final PrintWriter writer;
+/** Used to identify if a class string contains `hidden` */
+private static final Pattern HIDDEN_CLASS_PATTERN = Pattern.compile(
"(?:.*\\s|^)hidden(?:\\s.*|$)" );
+
/** Used to collect text events mainly for the head events. */
private StringBuffer textBuffer = new StringBuffer();
/** An indication on if we're inside a head. */
private boolean headFlag;
/** Keep track of the main and div tags for content events. */
-protected Stack contentStack = new Stack<>();
+protected Stack contentStack = new Stack();
/** Keep track of the closing tags for inline events. */
-protected Stack> inlineStack = new Stack<>();
+protected Stack> inlineStack = new Stack>();
Review Comment:
Why?
--
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-7491) Update parent POM to 36
[ https://issues.apache.org/jira/browse/MNG-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545421#comment-17545421 ] Hudson commented on MNG-7491: - Build succeeded in Jenkins: Maven » Maven TLP » maven » maven-3.9.x #41 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/maven-3.9.x/41/ > Update parent POM to 36 > --- > > Key: MNG-7491 > URL: https://issues.apache.org/jira/browse/MNG-7491 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0 > > > Update parent POM from 35 to 36. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-fluido-skin] bmarwell commented on pull request #31: [MSKINS-189] Deprecate Piwik web analytics
bmarwell commented on PR #31: URL: https://github.com/apache/maven-fluido-skin/pull/31#issuecomment-1144750132 @kwin will you add Matomo support later? -- 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
[GitHub] [maven-fluido-skin] kwin commented on pull request #31: [MSKINS-189] Deprecate Piwik web analytics
kwin commented on PR #31: URL: https://github.com/apache/maven-fluido-skin/pull/31#issuecomment-1144750968 > @kwin will you add Matomo support later? Already there: https://issues.apache.org/jira/browse/MSKINS-177 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-war-plugin] slachiewicz merged pull request #23: [MWAR-453] Require Java 8
slachiewicz merged PR #23: URL: https://github.com/apache/maven-war-plugin/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MWAR-453) Require Java 8
[ https://issues.apache.org/jira/browse/MWAR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MWAR-453. - Resolution: Fixed > Require Java 8 > -- > > Key: MWAR-453 > URL: https://issues.apache.org/jira/browse/MWAR-453 > Project: Maven WAR Plugin > Issue Type: Task >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-war-plugin] slachiewicz commented on pull request #24: Bump commons-io from 2.6 to 2.7
slachiewicz commented on PR #24: URL: https://github.com/apache/maven-war-plugin/pull/24#issuecomment-1144755470 @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] (MNG-7491) Update parent POM to 36
[ https://issues.apache.org/jira/browse/MNG-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545427#comment-17545427 ] Hudson commented on MNG-7491: - Build succeeded in Jenkins: Maven » Maven TLP » maven » master #57 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/57/ > Update parent POM to 36 > --- > > Key: MNG-7491 > URL: https://issues.apache.org/jira/browse/MNG-7491 > Project: Maven > Issue Type: Dependency upgrade > Components: Bootstrap & Build >Reporter: Tamás Cservenák >Assignee: Tamás Cservenák >Priority: Major > Fix For: 3.9.0, 4.0.0 > > > Update parent POM from 35 to 36. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MWAR-453) Require Java 8
[ https://issues.apache.org/jira/browse/MWAR-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545428#comment-17545428 ] Hudson commented on MWAR-453: - Build succeeded in Jenkins: Maven » Maven TLP » maven-war-plugin » master #11 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-war-plugin/job/master/11/ > Require Java 8 > -- > > Key: MWAR-453 > URL: https://issues.apache.org/jira/browse/MWAR-453 > Project: Maven WAR Plugin > Issue Type: Task >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-project-info-reports-plugin] gnodet opened a new pull request, #38: [MPIR-407] Provide a way to map license names
gnodet opened a new pull request, #38: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/38 This PR allows defining a mapping to group licenses in a cleaner way. From https://maven.apache.org/plugins/maven-site-plugin/dependencies.html#licenses using: ``` Apache License 2.0 The Apache Software License, Version 2.0 Apache Public License 2.0 Apache Software License - Version 2.0 Apache License, Version 2.0 Eclipse Public License 1.0 Eclipse Public License - Version 1.0 Eclipse Public License, Version 1.0 ``` to something like: ### Licenses - **Eclipse Public License, Version 1.0**: Aether API, Aether Implementation, Aether SPI, Aether Utilities, JUnit, Jetty :: Asynchronous HTTP Client, Jetty :: Http Utility, Jetty :: IO Utility, Jetty :: Proxy, Jetty :: Security, Jetty :: Server Core, Jetty :: Servlet Handling, Jetty :: Utilities, Jetty :: Utilities :: Ajax(JSON), Jetty :: Webapp Application Support, Jetty :: XML utilities, org.eclipse.sisu.inject, org.eclipse.sisu.plexus - **Unknown**: Plexus I18N Component, commons-beanutils, commons-collections, dom4j, oro - **MIT License**: SLF4J API Module, SLF4J Simple Binding, autolink-java - **The MIT License**: jsoup Java HTML Parser - **Apache License, Version 2.0**: Apache Commons Codec, Apache Commons Compress, Apache Commons IO, Apache Commons Lang, Apache Commons Text, Apache HttpClient, Apache HttpCore, Apache Maven Archiver, Apache Maven Reporting API, Apache Maven Reporting Executor, Apache Maven Shared Utils, Apache Maven Site Plugin, Apache Maven Wagon :: API, Apache Maven Wagon :: Providers :: HTTP Shared Library, Apache Maven Wagon :: Providers :: WebDAV Provider, Apache Velocity, CDI APIs, Commons Lang, Doxia :: APT Module, Doxia :: Core, Doxia :: FML Module, Doxia :: Markdown Module, Doxia :: Sink API, Doxia :: XDoc Module, Doxia :: XHTML Module, Doxia :: XHTML5 Module, Doxia Sitetools :: Decoration Model, Doxia Sitetools :: Integration Tools, Doxia Sitetools :: Site Renderer, Doxia Sitetools :: Skin Model, Guava: Google Core Libraries for Java, JCL 1.2 implemented over SLF4J, Jackrabbit WebDAV Library, Jetty :: Asynchronous HTTP Client, Jetty :: Http Utility, Jetty :: IO Utility, Jetty :: Proxy, Jetty :: Security, Jetty :: Server Core, Jetty :: Servlet Handling, Jetty :: Utilities, Jetty :: Utilities :: Ajax(JSON), Jetty :: Webapp Application Support, Jetty :: XML utilities, Maven Aether Provider, Maven Artifact, Maven Compat, Maven Core, Maven Model, Maven Model Builder, Maven Plugin API, Maven Plugin Testing Mechanism, Maven Plugin Tools Java Annotations, Maven Repository Metadata Model, Maven Settings, Maven Settings Builder, Plexus :: Component Annotations, Plexus Archiver Component, Plexus Cipher: encryption/decryption Component, Plexus Classworlds, Plexus Common Utilities, Plexus IO Components, Plexus Interpolation API, Plexus Security Dispatcher Component, Plexus Velocity Component, Sisu - Guice, Sisu - Inject (JSR330 bean support), Sisu - Inject (Plexus bean support), Sisu Guice - Core Library, VelocityTools, javax.inject, snappy - **CDDL + GPLv2 with classpath exception**: Java Servlet API, javax.annotation API - **Public Domain**: AOP alliance, XZ for Java - **BSD 2-Clause License**: flexmark-all, flexmark-ext-youtube-embedded, flexmark-java HTML to Markdown, flexmark-java core, flexmark-java extension for GitHub issue syntax, flexmark-java extension for GitHub user syntax, flexmark-java extension for GitLab Flavoured Markdown, flexmark-java extension for HTML5 media tags, flexmark-java extension for YAML front matter, flexmark-java extension for YouTrack conversion, flexmark-java extension for abbreviations in text, flexmark-java extension for admonition syntax, flexmark-java extension for attributes, flexmark-java extension for autolinking, flexmark-java extension for converting | to aside tags, flexmark-java extension for definition, flexmark-java extension for emoji shortcuts, flexmark-java extension for enumerated reference, flexmark-java extension for escaped_character, flexmark-java extension for footnotes, flexmark-java extension for formatter, flexmark-java extension for generating GitHub style task list items, flexmark-jav a extension for ins, flexmark-java extension for jekyll tag parsing, flexmark-java extension for jekyll_front_matter, flexmark-java extension for jira_converter, flexmark-java extension for processing macros, flexmark-java extension for strikethrough, flexmark-java extension for superscript, flexmark-java extension for tables, flexmark-java e
[GitHub] [maven-project-info-reports-plugin] michael-o commented on pull request #38: [MPIR-407] Provide a way to map license names
michael-o commented on PR #38: URL: https://github.com/apache/maven-project-info-reports-plugin/pull/38#issuecomment-1144880013 Nice, I will take a look after 3.8.5 release. -- 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
[GitHub] [maven-doxia] michael-o commented on pull request #104: [DOXIA-590] implement hidden rows
michael-o commented on PR #104: URL: https://github.com/apache/maven-doxia/pull/104#issuecomment-1144880745 Will check in the next couple of dazs. -- 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] (DOXIA-590) Either provided element class or default class gets ignored
[ https://issues.apache.org/jira/browse/DOXIA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545476#comment-17545476 ] ASF GitHub Bot commented on DOXIA-590: -- michael-o commented on PR #104: URL: https://github.com/apache/maven-doxia/pull/104#issuecomment-1144880745 Will check in the next couple of dazs. > Either provided element class or default class gets ignored > --- > > Key: DOXIA-590 > URL: https://issues.apache.org/jira/browse/DOXIA-590 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.8 >Reporter: Fred Eckertson >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M3, 1.11.2 > > Attachments: image-2022-05-18-21-57-40-619.png > > > The following construct is somewhat common in doxia-core > att.addAttribute( Attribute.CLASS, "a" ); > The documentation says that basic attributes (including CLASS) are supported. > However in cases like this either that "a" or the CLASS that was provided in > the attributes parameter will be ignored. The correct way to do this is to > append the provided CLASS to "a " if a CLASS attribute was provided. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-doxia] feckertson commented on pull request #104: [DOXIA-590] implement hidden rows
feckertson commented on PR #104: URL: https://github.com/apache/maven-doxia/pull/104#issuecomment-1144929969 Apologies for not checking the diff before creating the PR. The apache format introduced unintended changes/noise. The standard format should be applied, but in a PR which only does that. I couldn't find standard eclipse settings (code cleanup) for this org/project to avoid the diamond changes? Are there any? -- 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] (DOXIA-590) Either provided element class or default class gets ignored
[ https://issues.apache.org/jira/browse/DOXIA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545496#comment-17545496 ] ASF GitHub Bot commented on DOXIA-590: -- feckertson commented on PR #104: URL: https://github.com/apache/maven-doxia/pull/104#issuecomment-1144929969 Apologies for not checking the diff before creating the PR. The apache format introduced unintended changes/noise. The standard format should be applied, but in a PR which only does that. I couldn't find standard eclipse settings (code cleanup) for this org/project to avoid the diamond changes? Are there any? > Either provided element class or default class gets ignored > --- > > Key: DOXIA-590 > URL: https://issues.apache.org/jira/browse/DOXIA-590 > Project: Maven Doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.8 >Reporter: Fred Eckertson >Assignee: Michael Osipov >Priority: Major > Fix For: 2.0.0-M3, 1.11.2 > > Attachments: image-2022-05-18-21-57-40-619.png > > > The following construct is somewhat common in doxia-core > att.addAttribute( Attribute.CLASS, "a" ); > The documentation says that basic attributes (including CLASS) are supported. > However in cases like this either that "a" or the CLASS that was provided in > the attributes parameter will be ignored. The correct way to do this is to > append the provided CLASS to "a " if a CLASS attribute was provided. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MENFORCER-401) DependencyConvergence ignores exclusions
[
https://issues.apache.org/jira/browse/MENFORCER-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545553#comment-17545553
]
Slawomir Jaranowski commented on MENFORCER-401:
---
Should be working with the latest master version - please retest or provide
minimal project to reproduce.
> DependencyConvergence ignores exclusions
>
>
> Key: MENFORCER-401
> URL: https://issues.apache.org/jira/browse/MENFORCER-401
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin, Standard Rules
>Affects Versions: 3.0.0
>Reporter: T. Mohme
>Priority: Critical
>
> In my project there is a transitive dependency on an artifact ("idlj-idl")
> with scope=provided that cannot be resolved (this probably is a different
> problem) - so far, so good (bad).
> {noformat}
> ...
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at com.acme:my-project:jar:1.0.0 ->
> io.quarkus:quarkus-flyway:jar:2.2.3.Final ->
> io.quarkus:quarkus-agroal:jar:2.2.3.Final ->
> io.quarkus:quarkus-narayana-jta:jar:2.2.3.Final ->
> org.jboss.narayana.jts:narayana-jts-integration:jar:5.12.0.Final ->
> org.jboss.narayana.jts:idlj-idl:jar:5.12.0.Final
> ...{noformat}
> Interestingly, `./mvnw dependency:tree` doesn't show this dependency.
> The tree descends only down to "narayana-jts-integration".
> When I exclude the unresolvable dependency ("idle-idl") from an artifact
> before it in the chain shown by the exception cause, this has no impact:
> {noformat}
>
> io.quarkus
> quarkus-agroal
>
>
> org.jboss.narayana.jts
> idlj-idl
>
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MENFORCER-401) DependencyConvergence ignores exclusions
[
https://issues.apache.org/jira/browse/MENFORCER-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MENFORCER-401:
--
Fix Version/s: waiting-for-feedback
> DependencyConvergence ignores exclusions
>
>
> Key: MENFORCER-401
> URL: https://issues.apache.org/jira/browse/MENFORCER-401
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin, Standard Rules
>Affects Versions: 3.0.0
>Reporter: T. Mohme
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> In my project there is a transitive dependency on an artifact ("idlj-idl")
> with scope=provided that cannot be resolved (this probably is a different
> problem) - so far, so good (bad).
> {noformat}
> ...
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at com.acme:my-project:jar:1.0.0 ->
> io.quarkus:quarkus-flyway:jar:2.2.3.Final ->
> io.quarkus:quarkus-agroal:jar:2.2.3.Final ->
> io.quarkus:quarkus-narayana-jta:jar:2.2.3.Final ->
> org.jboss.narayana.jts:narayana-jts-integration:jar:5.12.0.Final ->
> org.jboss.narayana.jts:idlj-idl:jar:5.12.0.Final
> ...{noformat}
> Interestingly, `./mvnw dependency:tree` doesn't show this dependency.
> The tree descends only down to "narayana-jts-integration".
> When I exclude the unresolvable dependency ("idle-idl") from an artifact
> before it in the chain shown by the exception cause, this has no impact:
> {noformat}
>
> io.quarkus
> quarkus-agroal
>
>
> org.jboss.narayana.jts
> idlj-idl
>
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MENFORCER-414) Architecture-specific versions of library wrongly flagged by dependency convergence rule
[
https://issues.apache.org/jira/browse/MENFORCER-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1754#comment-1754
]
Slawomir Jaranowski commented on MENFORCER-414:
---
please provide minimal project to reproduce.
> Architecture-specific versions of library wrongly flagged by dependency
> convergence rule
>
>
> Key: MENFORCER-414
> URL: https://issues.apache.org/jira/browse/MENFORCER-414
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: Vladimir B
>Priority: Major
>
> I get the following warning reported by the dependency convergence rule of
> the plugin:
> {code:java}
> Dependency convergence error for
> io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile paths to
> dependency are:
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-com.twitter:finagle-http2_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:linux-x86_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:linux-aarch_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:osx-x86_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:osx-aarch_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:windows-x86_64:2.0.48.Final:compile{code}
> It seems that the conflicting library is seen as being the same for all the
> paths, while in fact there are architecture-specific versions of the same
> library, which shouldn't be treated as the same library in my opinion.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (MENFORCER-414) Architecture-specific versions of library wrongly flagged by dependency convergence rule
[
https://issues.apache.org/jira/browse/MENFORCER-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MENFORCER-414:
--
Fix Version/s: waiting-for-feedback
> Architecture-specific versions of library wrongly flagged by dependency
> convergence rule
>
>
> Key: MENFORCER-414
> URL: https://issues.apache.org/jira/browse/MENFORCER-414
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: Vladimir B
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I get the following warning reported by the dependency convergence rule of
> the plugin:
> {code:java}
> Dependency convergence error for
> io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile paths to
> dependency are:
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-com.twitter:finagle-http2_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:linux-x86_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:linux-aarch_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:osx-x86_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:osx-aarch_64:2.0.48.Final:compile
> and
> +-com.ing.wbs.toolkit:wbs-toolkit-tpa-httpclient:jar:5.5.0
> +-com.ing.apisdk:toolkit-connectivity-transport-http_2.12:jar:20.1.0:compile
> +-com.twitter:finagle-http_2.12:jar:22.2.0:compile
> +-io.netty:netty-tcnative-boringssl-static:jar:2.0.50.Final:compile
>
> +-io.netty:netty-tcnative-boringssl-static:jar:windows-x86_64:2.0.48.Final:compile{code}
> It seems that the conflicting library is seen as being the same for all the
> paths, while in fact there are architecture-specific versions of the same
> library, which shouldn't be treated as the same library in my opinion.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MENFORCER-413) Upgrading from 3.0.0-M3 to 3.0.0 causes strange errors about Spring Roo
[
https://issues.apache.org/jira/browse/MENFORCER-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545559#comment-17545559
]
Slawomir Jaranowski commented on MENFORCER-413:
---
please retest with the latest master version
> Upgrading from 3.0.0-M3 to 3.0.0 causes strange errors about Spring Roo
> ---
>
> Key: MENFORCER-413
> URL: https://issues.apache.org/jira/browse/MENFORCER-413
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: Matt Raible
>Priority: Major
> Fix For: wontfix-candidate
>
>
> In a fresh JHipster project, I get a strange error from the Maven enforcer
> plugin about Spring Roo dependencies.
>
> [INFO] — maven-enforcer-plugin:3.0.0:enforce (enforce-dependencyConvergence)
> @ lapp-li —
> [WARNING] The POM for org.apache.logging.log4j:log4j-api-java9:zip:2.14.1 is
> missing, no dependency information available
> Downloading from spring-libs-snapshot:
> [https://repo.spring.io/libs-snapshot/org/springframework/roo/org.springframework.roo.annotations/1.2.3.RELEASE/org.springframework.roo.annotations-1.2.3.RELEASE.pom]
> Downloading from spring-libs-release:
> [https://repo.spring.io/libs-release/org/springframework/roo/org.springframework.roo.annotations/1.2.3.RELEASE/org.springframework.roo.annotations-1.2.3.RELEASE.pom]
>
> If I run {{{}mvn dependency:tree | grep roo{}}}, there are no results.
>
> According to the issue below, reverting to -M3 solves the problem.
>
> [https://github.com/jhipster/generator-jhipster/issues/16318]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (MNG-7492) Invalid POMS are blithefully ignored
Robert Krajewski created MNG-7492:
-
Summary: Invalid POMS are blithefully ignored
Key: MNG-7492
URL: https://issues.apache.org/jira/browse/MNG-7492
Project: Maven
Issue Type: Improvement
Components: Dependencies
Affects Versions: 3.6.3
Reporter: Robert Krajewski
Invalid poms prevent construction of the model's dependencies tree (and thus
the model itself) and yet are only warnings:
{{[WARNING] Invalid POM , transitive dependencies (if any) will not be
available, enable debug logging for more details}}
Once this happens, Java compiler errors often ensue and are completely
mysterious. Debug logging will tell you why the POM is missing, but it doesn't
stop a nonsensical model from being treated as valid. Which it's {*}not{*}.
See
https://stackoverflow.com/questions/59944898/fail-on-invalid-or-missing-poms
for a discussion. Workarounds don't fix the issue.
Please implement an option to make this situation fail the build in Maven 3.
Even better, make it the default in a future version like Maven 4.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-surefire] dependabot[bot] closed pull request #540: Bump mockito-core from 2.28.2 to 4.6.0
dependabot[bot] closed pull request #540: Bump mockito-core from 2.28.2 to 4.6.0 URL: https://github.com/apache/maven-surefire/pull/540 -- 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
[GitHub] [maven-surefire] dependabot[bot] opened a new pull request, #542: Bump mockito-core from 2.28.2 to 4.6.1
dependabot[bot] opened a new pull request, #542: URL: https://github.com/apache/maven-surefire/pull/542 Bumps [mockito-core](https://github.com/mockito/mockito) from 2.28.2 to 4.6.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.6.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.1 2022-06-02 - https://github.com/mockito/mockito/compare/v4.6.0...v4.6.1";>6 commit(s) by Andy Coates, Chen Ni, dependabot[bot] Bump material from 1.6.0 to 1.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2662";>#2662)](https://github-redirect.dependabot.com/mockito/mockito/pull/2662";>mockito/mockito#2662) Bump core-ktx from 1.7.0 to 1.8.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2661";>#2661)](https://github-redirect.dependabot.com/mockito/mockito/pull/2661";>mockito/mockito#2661) Bump groovy from 3.0.10 to 3.0.11 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2660";>#2660)](https://github-redirect.dependabot.com/mockito/mockito/pull/2660";>mockito/mockito#2660) Fix for Issue2656 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2659";>#2659)](https://github-redirect.dependabot.com/mockito/mockito/pull/2659";>mockito/mockito#2659) Bump assertj-core from 3.22.0 to 3.23.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2658";>#2658)](https://github-redirect.dependabot.com/mockito/mockito/pull/2658";>mockito/mockito#2658) Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>#2656)](https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>mockito/mockito#2656) Fix typo [(https://github-redirect.dependabot.com/mockito/mockito/issues/2655";>#2655)](https://github-redirect.dependabot.com/mockito/mockito/pull/2655";>mockito/mockito#2655) v4.6.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.0 2022-05-27 - https://github.com/mockito/mockito/compare/v4.5.1...v4.6.0";>14 commit(s) by Hervé Boutemy, K. Siva Prasad Reddy, Rafael Winterhalter, dependabot[bot] Bump shipkit-changelog from 1.1.15 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2654";>#2654)](https://github-redirect.dependabot.com/mockito/mockito/pull/2654";>mockito/mockito#2654) Bump versions.errorprone from 2.13.1 to 2.14.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2653";>#2653)](https://github-redirect.dependabot.com/mockito/mockito/pull/2653";>mockito/mockito#2653) Bump shipkit-auto-version from 1.1.20 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2651";>#2651)](https://github-redirect.dependabot.com/mockito/mockito/pull/2651";>mockito/mockito#2651) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648 : Add support for customising strictness via https://github.com/Mock";>@Mock annotation and MockSettings [(https://github-redirect.dependabot.com/mockito/mockito/issues/2650";>#2650)](https://github-redirect.dependabot.com/mockito/mockito/pull/2650";>mockito/mockito#2650) Any way to enable Strict Stubbing when using Mockito.mock() without using https://github.com/Mock";>@Mock? [(https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648)](https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>mockito/mockito#2648) Reintroduce inheriting type annotations from interfaces if only one interface is mocked, including additional interfaces. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2645";>#2645)](https://github-redirect.dependabot.com/mockito/mockito/pull/2645";>mockito/mockito#2645) Bump com.diffplug.spotless from 6.6.0 to 6.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2643";>#2643)](https://github-redirect.dependabot.com/mockito/mockito/pull/2643";>mockito/mockito#2643) fix Reproducible Build issue [(https://github-redirect.dependabot.com/mockito/mockito/issues/2642";>#2642)](https://github-redirect.dependabot.com/mockito/mockito/pull/2642";>mockito/mockito#2642) Bump com.diffplug.spotless from 6.5.2 to 6.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2641";>#2641)](https://github-redirect.dependabot.com/mockito/mockito/pull/2641";>mockito/mockito#2641) Mockito mock of interfaces lost annotation information [(https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>#2640)](https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>mockito/mockito#2640) Bump material from 1.5.0 to 1.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2637";>#2637)](https://github-redirect.dependabot.com/mockito/mockito/pull/2637";>mockito/mockito#2637) Bump com.diffpl
[GitHub] [maven-surefire] dependabot[bot] commented on pull request #540: Bump mockito-core from 2.28.2 to 4.6.0
dependabot[bot] commented on PR #540: URL: https://github.com/apache/maven-surefire/pull/540#issuecomment-1145258953 Superseded by #542. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (MNG-7493) 3.8.5 regression when resolving dependencies between submodules
stephane geneix created MNG-7493: Summary: 3.8.5 regression when resolving dependencies between submodules Key: MNG-7493 URL: https://issues.apache.org/jira/browse/MNG-7493 Project: Maven Issue Type: Bug Components: Core Affects Versions: 3.8.5 Reporter: stephane geneix Attachments: maven-test.tar.gz see attached file for a set of projects that trigger the issue. I've tried to reduce it to the minimal set of files necessary to reproduce the issue There's a README with the command to execute as well. The description is as follow : We have one main package (package0) that declares 2 modules (package1 and package2). package1 and package2 both declare a package3 as their parent. package1 has a dependency on package2 package2 has a pom dependency on package0 compiling package1 works on 3.8.4 (or 3.6.3) but fails on 3.8.5. Here's the error text : [ERROR] Failed to execute goal on project package1: Could not resolve dependencies for project org.example:package1:jar:0.0.1: Failed to collect dependencies at org.example:package2:jar:0.0.1: Failed to read artifact descriptor for org.example:package2:jar:0.0.1: Could not transfer artifact org.example:package0:pom:0.0.1-SNAPSHOT from/to nexus-snapshots (https://nexus.soma.salesforce.com/nexus/content/repositories/snapshots): authentication failed for https://nexus.soma.salesforce.com/nexus/content/repositories/snapshots/org/example/package0/0.0.1-SNAPSHOT/package0-0.0.1-SNAPSHOT.pom, status: 401 Unauthorized -> [Help 1] [ERROR] I believe that the 401 unauthorized is a red herring. Even after cleaning up the ~.m2/repository, the problem persists on 3.8.5, but everything works on 3.8.4. I'm not exactly clear as to why there is such a dependency between all those packages, but the fact that the new maven version is broken is a significant problem in our CI systems -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MNG-7493) 3.8.5 regression when resolving dependencies between submodules
[ https://issues.apache.org/jira/browse/MNG-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephane geneix updated MNG-7493: - Description: see attached file for a set of projects that trigger the issue. I've tried to reduce it to the minimal set of files necessary to reproduce the issue There's a README with the command to execute as well. The description is as follow : We have one main package (package0) that declares 2 modules (package1 and package2). package1 and package2 both declare a package3 as their parent. package1 has a dependency on package2 package2 has a pom dependency on package0 compiling package1 works on 3.8.4 (or 3.6.3) but fails on 3.8.5. Here's the error text : [ERROR] Failed to execute goal on project package1: Could not resolve dependencies for project org.example:package1:jar:0.0.1: Failed to collect dependencies at org.example:package2:jar:0.0.1: Failed to read artifact descriptor for org.example:package2:jar:0.0.1: Could not transfer artifact org.example:package0:pom:0.0.1-SNAPSHOT from/to nexus-snapshots ([https://[XXX]/nexus/content/repositories/snapshots):|https://nexus.soma.salesforce.com/nexus/content/repositories/snapshots):] authentication failed for [https://[XXX]/nexus/content/repositories/snapshots/org/example/package0/0.0.1-SNAPSHOT/package0-0.0.1-SNAPSHOT.pom|https://nexus.soma.salesforce.com/nexus/content/repositories/snapshots/org/example/package0/0.0.1-SNAPSHOT/package0-0.0.1-SNAPSHOT.pom], status: 401 Unauthorized -> [Help 1] [ERROR] I believe that the 401 unauthorized is a red herring. Even after cleaning up the ~.m2/repository, the problem persists on 3.8.5, but everything works on 3.8.4. I'm not exactly clear as to why there is such a dependency between all those packages, but the fact that the new maven version is broken is a significant problem in our CI systems was: see attached file for a set of projects that trigger the issue. I've tried to reduce it to the minimal set of files necessary to reproduce the issue There's a README with the command to execute as well. The description is as follow : We have one main package (package0) that declares 2 modules (package1 and package2). package1 and package2 both declare a package3 as their parent. package1 has a dependency on package2 package2 has a pom dependency on package0 compiling package1 works on 3.8.4 (or 3.6.3) but fails on 3.8.5. Here's the error text : [ERROR] Failed to execute goal on project package1: Could not resolve dependencies for project org.example:package1:jar:0.0.1: Failed to collect dependencies at org.example:package2:jar:0.0.1: Failed to read artifact descriptor for org.example:package2:jar:0.0.1: Could not transfer artifact org.example:package0:pom:0.0.1-SNAPSHOT from/to nexus-snapshots (https://nexus.soma.salesforce.com/nexus/content/repositories/snapshots): authentication failed for https://nexus.soma.salesforce.com/nexus/content/repositories/snapshots/org/example/package0/0.0.1-SNAPSHOT/package0-0.0.1-SNAPSHOT.pom, status: 401 Unauthorized -> [Help 1] [ERROR] I believe that the 401 unauthorized is a red herring. Even after cleaning up the ~.m2/repository, the problem persists on 3.8.5, but everything works on 3.8.4. I'm not exactly clear as to why there is such a dependency between all those packages, but the fact that the new maven version is broken is a significant problem in our CI systems > 3.8.5 regression when resolving dependencies between submodules > --- > > Key: MNG-7493 > URL: https://issues.apache.org/jira/browse/MNG-7493 > Project: Maven > Issue Type: Bug > Components: Core >Affects Versions: 3.8.5 >Reporter: stephane geneix >Priority: Major > Attachments: maven-test.tar.gz > > > see attached file for a set of projects that trigger the issue. I've tried to > reduce it to the minimal set of files necessary to reproduce the issue > There's a README with the command to execute as well. > The description is as follow : > We have one main package (package0) that declares 2 modules (package1 and > package2). > package1 and package2 both declare a package3 as their parent. > package1 has a dependency on package2 > package2 has a pom dependency on package0 > compiling package1 works on 3.8.4 (or 3.6.3) but fails on 3.8.5. > Here's the error text : > [ERROR] Failed to execute goal on project package1: Could not resolve > dependencies for project org.example:package1:jar:0.0.1: Failed to collect > dependencies at org.example:package2:jar:0.0.1: Failed to read artifact > descriptor for org.example:package2:jar:0.0.1: Could not transfer artifact > org.example:package0:pom:0.0.1-SNAPSHOT from/to nexus-snapshots > ([https://[XXX]/nexus/content/repositories/snapshots):|https://nexus.soma.salesforce.com/n
[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request, #221: Bump mockito-core from 4.3.1 to 4.6.1
dependabot[bot] opened a new pull request, #221: URL: https://github.com/apache/maven-dependency-plugin/pull/221 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.3.1 to 4.6.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.6.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.1 2022-06-02 - https://github.com/mockito/mockito/compare/v4.6.0...v4.6.1";>6 commit(s) by Andy Coates, Chen Ni, dependabot[bot] Bump material from 1.6.0 to 1.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2662";>#2662)](https://github-redirect.dependabot.com/mockito/mockito/pull/2662";>mockito/mockito#2662) Bump core-ktx from 1.7.0 to 1.8.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2661";>#2661)](https://github-redirect.dependabot.com/mockito/mockito/pull/2661";>mockito/mockito#2661) Bump groovy from 3.0.10 to 3.0.11 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2660";>#2660)](https://github-redirect.dependabot.com/mockito/mockito/pull/2660";>mockito/mockito#2660) Fix for Issue2656 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2659";>#2659)](https://github-redirect.dependabot.com/mockito/mockito/pull/2659";>mockito/mockito#2659) Bump assertj-core from 3.22.0 to 3.23.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2658";>#2658)](https://github-redirect.dependabot.com/mockito/mockito/pull/2658";>mockito/mockito#2658) Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>#2656)](https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>mockito/mockito#2656) Fix typo [(https://github-redirect.dependabot.com/mockito/mockito/issues/2655";>#2655)](https://github-redirect.dependabot.com/mockito/mockito/pull/2655";>mockito/mockito#2655) v4.6.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.0 2022-05-27 - https://github.com/mockito/mockito/compare/v4.5.1...v4.6.0";>14 commit(s) by Hervé Boutemy, K. Siva Prasad Reddy, Rafael Winterhalter, dependabot[bot] Bump shipkit-changelog from 1.1.15 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2654";>#2654)](https://github-redirect.dependabot.com/mockito/mockito/pull/2654";>mockito/mockito#2654) Bump versions.errorprone from 2.13.1 to 2.14.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2653";>#2653)](https://github-redirect.dependabot.com/mockito/mockito/pull/2653";>mockito/mockito#2653) Bump shipkit-auto-version from 1.1.20 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2651";>#2651)](https://github-redirect.dependabot.com/mockito/mockito/pull/2651";>mockito/mockito#2651) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648 : Add support for customising strictness via https://github.com/Mock";>@Mock annotation and MockSettings [(https://github-redirect.dependabot.com/mockito/mockito/issues/2650";>#2650)](https://github-redirect.dependabot.com/mockito/mockito/pull/2650";>mockito/mockito#2650) Any way to enable Strict Stubbing when using Mockito.mock() without using https://github.com/Mock";>@Mock? [(https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648)](https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>mockito/mockito#2648) Reintroduce inheriting type annotations from interfaces if only one interface is mocked, including additional interfaces. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2645";>#2645)](https://github-redirect.dependabot.com/mockito/mockito/pull/2645";>mockito/mockito#2645) Bump com.diffplug.spotless from 6.6.0 to 6.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2643";>#2643)](https://github-redirect.dependabot.com/mockito/mockito/pull/2643";>mockito/mockito#2643) fix Reproducible Build issue [(https://github-redirect.dependabot.com/mockito/mockito/issues/2642";>#2642)](https://github-redirect.dependabot.com/mockito/mockito/pull/2642";>mockito/mockito#2642) Bump com.diffplug.spotless from 6.5.2 to 6.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2641";>#2641)](https://github-redirect.dependabot.com/mockito/mockito/pull/2641";>mockito/mockito#2641) Mockito mock of interfaces lost annotation information [(https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>#2640)](https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>mockito/mockito#2640) Bump material from 1.5.0 to 1.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2637";>#2637)](https://github-redirect.dependabot.com/mockito/mockito/pull/2637";>mockito/mockito#2637) Bump com
[GitHub] [maven-dependency-plugin] dependabot[bot] commented on pull request #220: Bump mockito-core from 4.3.1 to 4.6.0
dependabot[bot] commented on PR #220: URL: https://github.com/apache/maven-dependency-plugin/pull/220#issuecomment-1145409100 Superseded by #221. -- 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
[GitHub] [maven-dependency-plugin] dependabot[bot] closed pull request #220: Bump mockito-core from 4.3.1 to 4.6.0
dependabot[bot] closed pull request #220: Bump mockito-core from 4.3.1 to 4.6.0 URL: https://github.com/apache/maven-dependency-plugin/pull/220 -- 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
[GitHub] [maven-doxia-sitetools] dependabot[bot] opened a new pull request, #46: Bump htmlunit from 2.24 to 2.62.0
dependabot[bot] opened a new pull request, #46: URL: https://github.com/apache/maven-doxia-sitetools/pull/46 Bumps [htmlunit](https://github.com/HtmlUnit/htmlunit) from 2.24 to 2.62.0. Release notes Sourced from https://github.com/HtmlUnit/htmlunit/releases";>htmlunit's releases. HtmlUnit 2.62.0 Chrome/Edge 102 Firefox 101 Bugfixes & Enhancements Window.postMessage now supports arbitary js objects as message instead of converting them into strings. Please have a look at the https://htmlunit.sourceforge.io/changes-report.html#a2.62.0";>full release notes for details about this release. :two_hearts: Thank you to all who have contributed and to the sponsors (more sponsoring is welcome https://t.co/mmX3kAlCXy";>https://github.com/sponsors/rbri). HtmlUnit 2.61.0 Chrome/Edge 100 Firefox 99 Bugfixes & Enhancements neko: Possilbe OOM exception with broken input fixed use NativeConsole from core-js instead of our own implementation INCOMPATIBLE CHANGE: Class MediaList was moved from package com.gargoylesoftware.htmlunit.javascript.host.dom into package com.gargoylesoftware.htmlunit.javascript.host.css new method WebRequest.getParameters() returning all parameters (from the url and the body if available). This change was required to fix some issues with Spring MockMVC. Please have a look at the https://htmlunit.sourceforge.io/changes-report.html#a2.61.0";>full release notes for details about this release. :two_hearts: Thank you to all who have contributed and to the sponsors (more sponsoring is welcome https://t.co/mmX3kAlCXy";>https://github.com/sponsors/rbri). HtmlUnit 2.60.0 Chrome/Edge 99 Bugfixes fix broken package-info files generated by the maven plugin used for version 2.59.0 (see https://github-redirect.dependabot.com/HtmlUnit/htmlunit/issues/457";>HtmlUnit/htmlunit#457) Please have a look at the https://htmlunit.sourceforge.io/changes-report.html#a2.60.0";>full release notes for details about this release. HtmlUnit 2.59.0 Chrome/Edge 98 Firefox 97 Polyfills for Fetch and Proxy ClipboardHandler Rhino updates Bugfixes dedicated documentation of the WebClient/WebClientOptions Please have a look at the https://htmlunit.sourceforge.io/changes-report.html#a2.59.0";>full release notes for details about this release. HtmlUnit 2.58.0 bunch of Rhino updates client side validation fixes SimpleScriptable is deprecated, please use HtmlUnitScriptable instead Please have a look at the https://htmlunit.sourceforge.io/changes-report.html#a2.58.0";>full release notes for details about this release. HtmlUnit 2.57.0 Chrome/Edge 97 ... (truncated) Commits https://github.com/HtmlUnit/htmlunit/commit/6f0213723249f8557404d790aa1887d46d6cb956";>6f02137 prepare 2.62.0 https://github.com/HtmlUnit/htmlunit/commit/211af2d7aaed9152ed1b25e25a74e4fe011da422";>211af2d use the updated driver https://github.com/HtmlUnit/htmlunit/commit/ea052c97c037bdec3c3b5d56f1d237ec0140bad6";>ea052c9 introduce HtmlInput.getValue() & HtmlInput.setValue(String) https://github.com/HtmlUnit/htmlunit/commit/98ed2a8a7faa14a903b44f0c8c2cb6b2284b0334";>98ed2a8 pmd update https://github.com/HtmlUnit/htmlunit/commit/48ae803fc63134943f996fb93801c8f63c9a15ef";>48ae803 introduce HtmlInput.getValue() https://github.com/HtmlUnit/htmlunit/commit/5e0dba00499a278f4d618802be0be4f28684389c";>5e0dba0 edge 102, FF 101 https://github.com/HtmlUnit/htmlunit/commit/a54b74c7ab63a8184636d4104c284f96ad0c0089";>a54b74c use latest releases https://github.com/HtmlUnit/htmlunit/commit/dd854dfc2eb093edb112e6e36894d0d204b52831";>dd854df code style https://github.com/HtmlUnit/htmlunit/commit/9b96d9556dfd156c9c9b9a65dec8398373ddf1f0";>9b96d95 document last rhino changes https://github.com/HtmlUnit/htmlunit/commit/fcf9378d68b93983292d2fe614f75c7bcb736a6c";>fcf9378 more cleanup Additional commits viewable in https://github.com/HtmlUnit/htmlunit/compare/HtmlUnit-2.24...2.62.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, overwri
[GitHub] [maven-doxia-sitetools] dependabot[bot] commented on pull request #40: Bump htmlunit from 2.24 to 2.61.0
dependabot[bot] commented on PR #40: URL: https://github.com/apache/maven-doxia-sitetools/pull/40#issuecomment-1145530204 Superseded by #46. -- 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
[GitHub] [maven-doxia-sitetools] dependabot[bot] closed pull request #40: Bump htmlunit from 2.24 to 2.61.0
dependabot[bot] closed pull request #40: Bump htmlunit from 2.24 to 2.61.0 URL: https://github.com/apache/maven-doxia-sitetools/pull/40 -- 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
[GitHub] [maven-surefire] olamy merged pull request #535: [SUREFIRE-2086] Management of temporary files
olamy merged PR #535: URL: https://github.com/apache/maven-surefire/pull/535 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (SUREFIRE-2086) Management of temporary files
[ https://issues.apache.org/jira/browse/SUREFIRE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned SUREFIRE-2086: -- Assignee: Olivier Lamy > Management of temporary files > - > > Key: SUREFIRE-2086 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2086 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 3.0.0-M6 >Reporter: Markus Spann >Assignee: Olivier Lamy >Priority: Minor > > Management of temporary files in surefire into sub directories of the > system's directory of temporary files to avoid bloating the temp directory > root. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (SUREFIRE-2086) Management of temporary files
[ https://issues.apache.org/jira/browse/SUREFIRE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-2086. -- Resolution: Fixed PR merged. Thanks > Management of temporary files > - > > Key: SUREFIRE-2086 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2086 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 3.0.0-M6 >Reporter: Markus Spann >Assignee: Olivier Lamy >Priority: Minor > Fix For: 3.0.0-M7 > > > Management of temporary files in surefire into sub directories of the > system's directory of temporary files to avoid bloating the temp directory > root. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SUREFIRE-2086) Management of temporary files
[ https://issues.apache.org/jira/browse/SUREFIRE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SUREFIRE-2086: --- Fix Version/s: 3.0.0-M7 > Management of temporary files > - > > Key: SUREFIRE-2086 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2086 > Project: Maven Surefire > Issue Type: New Feature >Affects Versions: 3.0.0-M6 >Reporter: Markus Spann >Assignee: Olivier Lamy >Priority: Minor > Fix For: 3.0.0-M7 > > > Management of temporary files in surefire into sub directories of the > system's directory of temporary files to avoid bloating the temp directory > root. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[GitHub] [maven-surefire] chalmagr commented on pull request #516: [SUREFIRE-2065] Test Reports Inconsistencies with Parameterized and junit4
chalmagr commented on PR #516: URL: https://github.com/apache/maven-surefire/pull/516#issuecomment-1145594062 Hi - been unavailable for some time... will look into this shortly. Thanks! -- 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
[GitHub] [maven-surefire] sman-81 commented on pull request #535: [SUREFIRE-2086] Management of temporary files
sman-81 commented on PR #535: URL: https://github.com/apache/maven-surefire/pull/535#issuecomment-1145594568 Thanks @olamy! -- 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
[GitHub] [maven-wrapper] dependabot[bot] opened a new pull request, #48: Bump mockito-core from 4.5.1 to 4.6.1
dependabot[bot] opened a new pull request, #48: URL: https://github.com/apache/maven-wrapper/pull/48 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.5.1 to 4.6.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.6.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.1 2022-06-02 - https://github.com/mockito/mockito/compare/v4.6.0...v4.6.1";>6 commit(s) by Andy Coates, Chen Ni, dependabot[bot] Bump material from 1.6.0 to 1.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2662";>#2662)](https://github-redirect.dependabot.com/mockito/mockito/pull/2662";>mockito/mockito#2662) Bump core-ktx from 1.7.0 to 1.8.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2661";>#2661)](https://github-redirect.dependabot.com/mockito/mockito/pull/2661";>mockito/mockito#2661) Bump groovy from 3.0.10 to 3.0.11 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2660";>#2660)](https://github-redirect.dependabot.com/mockito/mockito/pull/2660";>mockito/mockito#2660) Fix for Issue2656 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2659";>#2659)](https://github-redirect.dependabot.com/mockito/mockito/pull/2659";>mockito/mockito#2659) Bump assertj-core from 3.22.0 to 3.23.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2658";>#2658)](https://github-redirect.dependabot.com/mockito/mockito/pull/2658";>mockito/mockito#2658) Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>#2656)](https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>mockito/mockito#2656) Fix typo [(https://github-redirect.dependabot.com/mockito/mockito/issues/2655";>#2655)](https://github-redirect.dependabot.com/mockito/mockito/pull/2655";>mockito/mockito#2655) v4.6.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.0 2022-05-27 - https://github.com/mockito/mockito/compare/v4.5.1...v4.6.0";>14 commit(s) by Hervé Boutemy, K. Siva Prasad Reddy, Rafael Winterhalter, dependabot[bot] Bump shipkit-changelog from 1.1.15 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2654";>#2654)](https://github-redirect.dependabot.com/mockito/mockito/pull/2654";>mockito/mockito#2654) Bump versions.errorprone from 2.13.1 to 2.14.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2653";>#2653)](https://github-redirect.dependabot.com/mockito/mockito/pull/2653";>mockito/mockito#2653) Bump shipkit-auto-version from 1.1.20 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2651";>#2651)](https://github-redirect.dependabot.com/mockito/mockito/pull/2651";>mockito/mockito#2651) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648 : Add support for customising strictness via https://github.com/Mock";>@Mock annotation and MockSettings [(https://github-redirect.dependabot.com/mockito/mockito/issues/2650";>#2650)](https://github-redirect.dependabot.com/mockito/mockito/pull/2650";>mockito/mockito#2650) Any way to enable Strict Stubbing when using Mockito.mock() without using https://github.com/Mock";>@Mock? [(https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648)](https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>mockito/mockito#2648) Reintroduce inheriting type annotations from interfaces if only one interface is mocked, including additional interfaces. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2645";>#2645)](https://github-redirect.dependabot.com/mockito/mockito/pull/2645";>mockito/mockito#2645) Bump com.diffplug.spotless from 6.6.0 to 6.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2643";>#2643)](https://github-redirect.dependabot.com/mockito/mockito/pull/2643";>mockito/mockito#2643) fix Reproducible Build issue [(https://github-redirect.dependabot.com/mockito/mockito/issues/2642";>#2642)](https://github-redirect.dependabot.com/mockito/mockito/pull/2642";>mockito/mockito#2642) Bump com.diffplug.spotless from 6.5.2 to 6.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2641";>#2641)](https://github-redirect.dependabot.com/mockito/mockito/pull/2641";>mockito/mockito#2641) Mockito mock of interfaces lost annotation information [(https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>#2640)](https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>mockito/mockito#2640) Bump material from 1.5.0 to 1.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2637";>#2637)](https://github-redirect.dependabot.com/mockito/mockito/pull/2637";>mockito/mockito#2637) Bump com.diffplug.sp
[GitHub] [maven-wrapper] dependabot[bot] commented on pull request #46: Bump mockito-core from 4.5.1 to 4.6.0
dependabot[bot] commented on PR #46: URL: https://github.com/apache/maven-wrapper/pull/46#issuecomment-1145600380 Superseded by #48. -- 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
[GitHub] [maven-wrapper] dependabot[bot] closed pull request #46: Bump mockito-core from 4.5.1 to 4.6.0
dependabot[bot] closed pull request #46: Bump mockito-core from 4.5.1 to 4.6.0 URL: https://github.com/apache/maven-wrapper/pull/46 -- 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] (MRELEASE-1072) scm.tag removed for next snapshot during prepare when using svn
[
https://issues.apache.org/jira/browse/MRELEASE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545749#comment-17545749
]
Herve Boutemy commented on MRELEASE-1072:
-
[~sleberrigaud] the issue :)
because I need feedback to make sure the new feature make sense and deserves
the new maintenance
I want to start the vote this WE, with this issue integrated or not
> scm.tag removed for next snapshot during prepare when using svn
> ---
>
> Key: MRELEASE-1072
> URL: https://issues.apache.org/jira/browse/MRELEASE-1072
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> In case that the original {{project.scm}} section contains a tag element
> (e.g. with value "trunk") this is removed during prepare for the next
> snapshot version. The tagged/release version contains the properly adjusted
> tag element.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request, #129: Bump mockito-core from 4.6.0 to 4.6.1
dependabot[bot] opened a new pull request, #129: URL: https://github.com/apache/maven-invoker-plugin/pull/129 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.6.0 to 4.6.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.6.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.1 2022-06-02 - https://github.com/mockito/mockito/compare/v4.6.0...v4.6.1";>6 commit(s) by Andy Coates, Chen Ni, dependabot[bot] Bump material from 1.6.0 to 1.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2662";>#2662)](https://github-redirect.dependabot.com/mockito/mockito/pull/2662";>mockito/mockito#2662) Bump core-ktx from 1.7.0 to 1.8.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2661";>#2661)](https://github-redirect.dependabot.com/mockito/mockito/pull/2661";>mockito/mockito#2661) Bump groovy from 3.0.10 to 3.0.11 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2660";>#2660)](https://github-redirect.dependabot.com/mockito/mockito/pull/2660";>mockito/mockito#2660) Fix for Issue2656 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2659";>#2659)](https://github-redirect.dependabot.com/mockito/mockito/pull/2659";>mockito/mockito#2659) Bump assertj-core from 3.22.0 to 3.23.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2658";>#2658)](https://github-redirect.dependabot.com/mockito/mockito/pull/2658";>mockito/mockito#2658) Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>#2656)](https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>mockito/mockito#2656) Fix typo [(https://github-redirect.dependabot.com/mockito/mockito/issues/2655";>#2655)](https://github-redirect.dependabot.com/mockito/mockito/pull/2655";>mockito/mockito#2655) Commits https://github.com/mockito/mockito/commit/ff98622a8f4bbe96ef5405434b5d788fcd118bb4";>ff98622 Restore behavior for mocks configured without strictness (https://github-redirect.dependabot.com/mockito/mockito/issues/2659";>#2659) https://github.com/mockito/mockito/commit/1fbef57f8a54ec6ff3ffc1551b493351df81ab9e";>1fbef57 Bump groovy from 3.0.10 to 3.0.11 (https://github-redirect.dependabot.com/mockito/mockito/issues/2660";>#2660) https://github.com/mockito/mockito/commit/c47c7ecedd66824325be0e62b883d78c97444521";>c47c7ec Bump core-ktx from 1.7.0 to 1.8.0 (https://github-redirect.dependabot.com/mockito/mockito/issues/2661";>#2661) https://github.com/mockito/mockito/commit/2bbf7963b17ea83c24c6925e0bd7ddc99e222825";>2bbf796 Bump material from 1.6.0 to 1.6.1 (https://github-redirect.dependabot.com/mockito/mockito/issues/2662";>#2662) https://github.com/mockito/mockito/commit/4f41700cfbd00afeff7b9b48e1cdf777cf248ed5";>4f41700 Bump assertj-core from 3.22.0 to 3.23.1 (https://github-redirect.dependabot.com/mockito/mockito/issues/2658";>#2658) https://github.com/mockito/mockito/commit/e5a06c5dbae4fecdbb8054d542d3bc5ba5c8ee00";>e5a06c5 Fix typo (https://github-redirect.dependabot.com/mockito/mockito/issues/2655";>#2655) See full diff in https://github.com/mockito/mockito/compare/v4.6.0...v4.6.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 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 an
[GitHub] [maven-jlink-plugin] dependabot[bot] opened a new pull request, #111: Bump mockito-core from 4.2.0 to 4.6.1
dependabot[bot] opened a new pull request, #111: URL: https://github.com/apache/maven-jlink-plugin/pull/111 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.2.0 to 4.6.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.6.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.1 2022-06-02 - https://github.com/mockito/mockito/compare/v4.6.0...v4.6.1";>6 commit(s) by Andy Coates, Chen Ni, dependabot[bot] Bump material from 1.6.0 to 1.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2662";>#2662)](https://github-redirect.dependabot.com/mockito/mockito/pull/2662";>mockito/mockito#2662) Bump core-ktx from 1.7.0 to 1.8.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2661";>#2661)](https://github-redirect.dependabot.com/mockito/mockito/pull/2661";>mockito/mockito#2661) Bump groovy from 3.0.10 to 3.0.11 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2660";>#2660)](https://github-redirect.dependabot.com/mockito/mockito/pull/2660";>mockito/mockito#2660) Fix for Issue2656 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2659";>#2659)](https://github-redirect.dependabot.com/mockito/mockito/pull/2659";>mockito/mockito#2659) Bump assertj-core from 3.22.0 to 3.23.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2658";>#2658)](https://github-redirect.dependabot.com/mockito/mockito/pull/2658";>mockito/mockito#2658) Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>#2656)](https://github-redirect.dependabot.com/mockito/mockito/issues/2656";>mockito/mockito#2656) Fix typo [(https://github-redirect.dependabot.com/mockito/mockito/issues/2655";>#2655)](https://github-redirect.dependabot.com/mockito/mockito/pull/2655";>mockito/mockito#2655) v4.6.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.6.0 2022-05-27 - https://github.com/mockito/mockito/compare/v4.5.1...v4.6.0";>14 commit(s) by Hervé Boutemy, K. Siva Prasad Reddy, Rafael Winterhalter, dependabot[bot] Bump shipkit-changelog from 1.1.15 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2654";>#2654)](https://github-redirect.dependabot.com/mockito/mockito/pull/2654";>mockito/mockito#2654) Bump versions.errorprone from 2.13.1 to 2.14.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2653";>#2653)](https://github-redirect.dependabot.com/mockito/mockito/pull/2653";>mockito/mockito#2653) Bump shipkit-auto-version from 1.1.20 to 1.2.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2651";>#2651)](https://github-redirect.dependabot.com/mockito/mockito/pull/2651";>mockito/mockito#2651) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648 : Add support for customising strictness via https://github.com/Mock";>@Mock annotation and MockSettings [(https://github-redirect.dependabot.com/mockito/mockito/issues/2650";>#2650)](https://github-redirect.dependabot.com/mockito/mockito/pull/2650";>mockito/mockito#2650) Any way to enable Strict Stubbing when using Mockito.mock() without using https://github.com/Mock";>@Mock? [(https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>#2648)](https://github-redirect.dependabot.com/mockito/mockito/issues/2648";>mockito/mockito#2648) Reintroduce inheriting type annotations from interfaces if only one interface is mocked, including additional interfaces. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2645";>#2645)](https://github-redirect.dependabot.com/mockito/mockito/pull/2645";>mockito/mockito#2645) Bump com.diffplug.spotless from 6.6.0 to 6.6.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2643";>#2643)](https://github-redirect.dependabot.com/mockito/mockito/pull/2643";>mockito/mockito#2643) fix Reproducible Build issue [(https://github-redirect.dependabot.com/mockito/mockito/issues/2642";>#2642)](https://github-redirect.dependabot.com/mockito/mockito/pull/2642";>mockito/mockito#2642) Bump com.diffplug.spotless from 6.5.2 to 6.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2641";>#2641)](https://github-redirect.dependabot.com/mockito/mockito/pull/2641";>mockito/mockito#2641) Mockito mock of interfaces lost annotation information [(https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>#2640)](https://github-redirect.dependabot.com/mockito/mockito/issues/2640";>mockito/mockito#2640) Bump material from 1.5.0 to 1.6.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2637";>#2637)](https://github-redirect.dependabot.com/mockito/mockito/pull/2637";>mockito/mockito#2637) Bump com.diff
[GitHub] [maven-jlink-plugin] dependabot[bot] commented on pull request #108: Bump mockito-core from 4.2.0 to 4.6.0
dependabot[bot] commented on PR #108: URL: https://github.com/apache/maven-jlink-plugin/pull/108#issuecomment-1145651148 Superseded by #111. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] dependabot[bot] closed pull request #108: Bump mockito-core from 4.2.0 to 4.6.0
dependabot[bot] closed pull request #108: Bump mockito-core from 4.2.0 to 4.6.0 URL: https://github.com/apache/maven-jlink-plugin/pull/108 -- 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
