[jira] [Created] (MARTIFACT-58) display origin of local repository artifact when comparing

2024-01-04 Thread Herve Boutemy (Jira)
Herve Boutemy created MARTIFACT-58: -- Summary: display origin of local repository artifact when comparing Key: MARTIFACT-58 URL: https://issues.apache.org/jira/browse/MARTIFACT-58 Project: Maven Artifa

[jira] [Commented] (MSHADE-462) 3.5.1 not compatible with 3.4.1: The version cannot be empty

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MSHADE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803387#comment-17803387 ] ASF GitHub Bot commented on MSHADE-462: --- CrazyHZM opened a new pull request, #208:

[PR] [MSHADE-462] 3.5.1 not compatible with 3.4.1: The version cannot be empty [maven-shade-plugin]

2024-01-04 Thread via GitHub
CrazyHZM opened a new pull request, #208: URL: https://github.com/apache/maven-shade-plugin/pull/208 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MSHADE) filed

[jira] [Commented] (SUREFIRE-2231) JaCoCo 0.8.11 fails with old TestNG releases on Java 17+

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803369#comment-17803369 ] ASF GitHub Bot commented on SUREFIRE-2231: -- slachiewicz commented on PR #710:

Re: [PR] [SUREFIRE-2231] JaCoCo 0.8.11 fails with old TestNG releases on Java 17+ [maven-surefire]

2024-01-04 Thread via GitHub
slachiewicz commented on PR #710: URL: https://github.com/apache/maven-surefire/pull/710#issuecomment-1877964618 Nice spot -- 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. T

[jira] [Updated] (MPIR-455) dependencies goal: add support for multi-release jar

2024-01-04 Thread Gabriel Belingueres (Jira)
[ https://issues.apache.org/jira/browse/MPIR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Belingueres updated MPIR-455: - Description: dependencies goal reports dependencies with multi-release support with the hi

[jira] [Created] (MPIR-455) dependencies goal: add support for multi-release jar

2024-01-04 Thread Gabriel Belingueres (Jira)
Gabriel Belingueres created MPIR-455: Summary: dependencies goal: add support for multi-release jar Key: MPIR-455 URL: https://issues.apache.org/jira/browse/MPIR-455 Project: Maven Project Info Rep

Re: [PR] Bump org.apache.maven.plugins:maven-docck-plugin from 1.1 to 1.2 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #713: URL: https://github.com/apache/maven-surefire/pull/713#issuecomment-1877782610 @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 comm

Re: [PR] Bump net.java.dev.javacc:javacc from 7.0.12 to 7.0.13 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #711: URL: https://github.com/apache/maven-surefire/pull/711#issuecomment-1877782543 @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 comm

Re: [PR] Bump commons-io:commons-io from 2.15.0 to 2.15.1 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #712: URL: https://github.com/apache/maven-surefire/pull/712#issuecomment-1877782446 @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 comm

Re: [PR] Drop old TestNG, test with more recent ones [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #710: URL: https://github.com/apache/maven-surefire/pull/710#issuecomment-1877706149 @slachiewicz I am an idiot, created too much noise. I logged the JaCoCo and TestNG issue: https://issues.apache.org/jira/browse/SUREFIRE-2231 -- This is an automated message from

[jira] [Created] (SUREFIRE-2231) JaCoCo 0.8.11 fails with old TestNG releases on Java 17+

2024-01-04 Thread Michael Osipov (Jira)
Michael Osipov created SUREFIRE-2231: Summary: JaCoCo 0.8.11 fails with old TestNG releases on Java 17+ Key: SUREFIRE-2231 URL: https://issues.apache.org/jira/browse/SUREFIRE-2231 Project: Maven Su

[jira] [Commented] (MNG-6776) Inconsistent list of parameters in MojoDescriptor

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803307#comment-17803307 ] ASF GitHub Bot commented on MNG-6776: - michael-o commented on PR #1361: URL: https://gi

Re: [PR] [MNG-6776] Inconsistent list of parameters for MojoDescriptor (#584) [maven]

2024-01-04 Thread via GitHub
michael-o commented on PR #1361: URL: https://github.com/apache/maven/pull/1361#issuecomment-1877694981 @cstamas Any objections before I backport this one? -- 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

[jira] [Commented] (MNG-6776) Inconsistent list of parameters in MojoDescriptor

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MNG-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803306#comment-17803306 ] ASF GitHub Bot commented on MNG-6776: - michael-o commented on PR #1361: URL: https://gi

Re: [PR] [MNG-6776] Inconsistent list of parameters for MojoDescriptor (#584) [maven]

2024-01-04 Thread via GitHub
michael-o commented on PR #1361: URL: https://github.com/apache/maven/pull/1361#issuecomment-1877694799 > good, maybe it's also worth to backport to 3.8.x? I was thinking about the same. Will prepare after this one. -- This is an automated message from the Apache Git Service. To res

Re: [PR] [MPOM-451] Remove repository elements from Apache Parent [maven-apache-parent]

2024-01-04 Thread via GitHub
ctubbsii commented on PR #183: URL: https://github.com/apache/maven-apache-parent/pull/183#issuecomment-1877686303 > > A lot of projects rely on this being already set up > > Understandable, but since these upgrades don't happen automatically and "fail fast", I don't see this as a bi

[PR] Bump org.apache.maven.plugins:maven-docck-plugin from 1.1 to 1.2 [maven-surefire]

2024-01-04 Thread via GitHub
dependabot[bot] opened a new pull request, #713: URL: https://github.com/apache/maven-surefire/pull/713 Bumps [org.apache.maven.plugins:maven-docck-plugin](https://github.com/apache/maven-docck-plugin) from 1.1 to 1.2. Commits https://github.com/apache/maven-docck-plugin/commi

[PR] Bump commons-io:commons-io from 2.15.0 to 2.15.1 [maven-surefire]

2024-01-04 Thread via GitHub
dependabot[bot] opened a new pull request, #712: URL: https://github.com/apache/maven-surefire/pull/712 Bumps commons-io:commons-io from 2.15.0 to 2.15.1. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons-

[PR] Bump net.java.dev.javacc:javacc from 7.0.12 to 7.0.13 [maven-surefire]

2024-01-04 Thread via GitHub
dependabot[bot] opened a new pull request, #711: URL: https://github.com/apache/maven-surefire/pull/711 Bumps [net.java.dev.javacc:javacc](https://github.com/javacc/javacc) from 7.0.12 to 7.0.13. Changelog Sourced from https://github.com/javacc/javacc/blob/master/docs/release-notes

[jira] [Commented] (DOXIASITETOOLS-324) Allow configuration of parser (per markup source path pattern)

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803295#comment-17803295 ] ASF GitHub Bot commented on DOXIASITETOOLS-324: --- kwin commented on

Re: [PR] [DOXIASITETOOLS-324] Allow configuration of Doxia parser [maven-doxia-sitetools]

2024-01-04 Thread via GitHub
kwin commented on code in PR #126: URL: https://github.com/apache/maven-doxia-sitetools/pull/126#discussion_r1442152573 ## doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java: ## @@ -320,9 +337,13 @@ public void renderDocument(

[jira] [Comment Edited] (MPOM-449) Remove the leading "1." from source/target properties

2024-01-04 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MPOM-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803264#comment-17803264 ] Herve Boutemy edited comment on MPOM-449 at 1/4/24 6:15 PM: ver

[jira] [Commented] (MPOM-449) Remove the leading "1." from source/target properties

2024-01-04 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MPOM-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803264#comment-17803264 ] Herve Boutemy commented on MPOM-449: very good idea: this is supported since Java 5, we

[jira] [Updated] (DOXIASITETOOLS-324) Allow configuration of parser (per markup source path pattern)

2024-01-04 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated DOXIASITETOOLS-324: --- Fix Version/s: 2.0.0-M17 > Allow configuration of parser (per markup

[jira] [Updated] (MNG-7991) refactor "aggregator" goal feature

2024-01-04 Thread Herve Boutemy (Jira)
[ https://issues.apache.org/jira/browse/MNG-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-7991: --- Summary: refactor "aggregator" goal feature (was: refactor aggregator goal) > refactor "aggregator" go

[jira] [Updated] (DOXIA-722) Optionally create anchors for index entries server-side (used in TOCs)

2024-01-04 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/DOXIA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated DOXIA-722: -- Description: The links for the TOC macro are created server-side by Doxia while the only referen

[jira] [Updated] (DOXIA-722) Optionally create anchors for index entries server-side (used in TOCs)

2024-01-04 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/DOXIA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated DOXIA-722: -- Fix Version/s: 2.0.0 > Optionally create anchors for index entries server-side (used in TOCs) >

[jira] [Assigned] (DOXIA-710) Inconsistent anchors between toc macro and headers

2024-01-04 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/DOXIA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned DOXIA-710: - Assignee: (was: Konrad Windszus) > Inconsistent anchors between toc macro and headers

[jira] [Commented] (DOXIA-722) Optionally create anchors for index entries server-side (used in TOCs)

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/DOXIA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803241#comment-17803241 ] ASF GitHub Bot commented on DOXIA-722: -- kwin commented on PR #180: URL: https://githu

Re: [PR] [DOXIA-722] Optionally generate anchors for TOC entries [maven-doxia]

2024-01-04 Thread via GitHub
kwin commented on PR #180: URL: https://github.com/apache/maven-doxia/pull/180#issuecomment-1877409083 > The the actual change is perfectly fine, this needs a new JIRA issue because it does not really solve [DOXIA-710](https://issues.apache.org/jira/browse/DOXIA-710) because we cannot solv

[jira] [Updated] (MSITE-1000) Allow parametrisation of Doxia parser per file

2024-01-04 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/MSITE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MSITE-1000: --- Description: Currently only the attributes used for rendering the site can be parameterized

[jira] [Commented] (DOXIA-710) Inconsistent anchors between toc macro and headers

2024-01-04 Thread Konrad Windszus (Jira)
[ https://issues.apache.org/jira/browse/DOXIA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803240#comment-17803240 ] Konrad Windszus commented on DOXIA-710: --- As requested by [~michael-o] the workaround

[jira] [Created] (DOXIA-722) Optionally create anchors for index entries server-side (used in TOCs)

2024-01-04 Thread Konrad Windszus (Jira)
Konrad Windszus created DOXIA-722: - Summary: Optionally create anchors for index entries server-side (used in TOCs) Key: DOXIA-722 URL: https://issues.apache.org/jira/browse/DOXIA-722 Project: Maven D

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803228#comment-17803228 ] ASF GitHub Bot commented on MCOMPILER-391: -- psiroky commented on PR #180: URL

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
psiroky commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1877354179 Ah, I see. In that case you are right, the relocation message should be there. I'll see if I can find some time to take a look at this. -- This is an automated message from

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803209#comment-17803209 ] ASF GitHub Bot commented on MCOMPILER-391: -- famod commented on PR #180: URL:

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
famod commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1877280262 > I think the missing relocation warning has the same cause - the plugin (or more precisely the dependency resolution mechanism the plugin uses) simply does not know that the a

[jira] [Updated] (MNG-7993) New or existing service improvement: "resolve in the context of project"

2024-01-04 Thread Tamas Cservenak (Jira)
[ https://issues.apache.org/jira/browse/MNG-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7993: - Description: See for example MCOMPILER-391. Today all the burden is on plugin to reimplement all t

[jira] [Created] (MNG-7993) New or existing service improvement: "resolve in the context of project"

2024-01-04 Thread Tamas Cservenak (Jira)
Tamas Cservenak created MNG-7993: Summary: New or existing service improvement: "resolve in the context of project" Key: MNG-7993 URL: https://issues.apache.org/jira/browse/MNG-7993 Project: Maven

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803199#comment-17803199 ] ASF GitHub Bot commented on MCOMPILER-391: -- psiroky commented on PR #180: URL

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
psiroky commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-187725 Yeah, there could possibly be some sort of heuristics to try to detect these relocations. Not sure if this would be something that should be done directly in the plugin or ra

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803175#comment-17803175 ] ASF GitHub Bot commented on MCOMPILER-391: -- famod commented on PR #180: URL:

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
famod commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1877127524 @psiroky Yeah, I think you have a very valid point: There is no explicit version for that old groupId and so there is no precise way to find the exact pom with the relo

Re: [PR] subject verb agreement [maven-compiler-plugin]

2024-01-04 Thread via GitHub
elharo merged PR #221: URL: https://github.com/apache/maven-compiler-plugin/pull/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...@

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
psiroky commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1876984635 @famod thanks. In this case, I am not quite sure this is supported from Maven itself. I assume there is no version anywhere in the project depMgmt for `org.hibernate:h

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803039#comment-17803039 ] ASF GitHub Bot commented on MCOMPILER-391: -- psiroky commented on PR #180: URL

Re: [PR] Bump jacocoVersion from 0.8.8 to 0.8.11 [maven-surefire]

2024-01-04 Thread via GitHub
dependabot[bot] commented on PR #683: URL: https://github.com/apache/maven-surefire/pull/683#issuecomment-1876953440 OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependen

Re: [PR] Bump jacocoVersion from 0.8.8 to 0.8.11 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o closed pull request #683: Bump jacocoVersion from 0.8.8 to 0.8.11 URL: https://github.com/apache/maven-surefire/pull/683 -- 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

Re: [PR] Bump jacocoVersion from 0.8.8 to 0.8.11 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #683: URL: https://github.com/apache/maven-surefire/pull/683#issuecomment-1876953392 Merged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To un

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802972#comment-17802972 ] ASF GitHub Bot commented on MCOMPILER-391: -- famod commented on PR #180: URL:

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
famod commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1876946809 @psiroky sure: > Are you relying on the new dependency management Yes, that's what I tried and this doesn't work (old groupId): ```xml

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802947#comment-17802947 ] ASF GitHub Bot commented on MCOMPILER-391: -- psiroky commented on PR #180: URL

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
psiroky commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1876936773 @famod could you please provide a bit more details, maybe with an example configuration of the plugin? Are you relying on the new dependency management, or specifying the ver

[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802911#comment-17802911 ] ASF GitHub Bot commented on MCOMPILER-391: -- famod commented on PR #180: URL:

Re: [PR] [MCOMPILER-391] Use dep mgmt when resolving annotation processors and their deps [maven-compiler-plugin]

2024-01-04 Thread via GitHub
famod commented on PR #180: URL: https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1876921475 Just a heads up: This implementation does not seem to respect relocations, e.g. I was still using https://mvnrepository.com/artifact/org.hibernate/hibernate-jpamodelgen in my

[jira] [Commented] (DOXIASITETOOLS-324) Allow configuration of parser (per markup source path pattern)

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802900#comment-17802900 ] ASF GitHub Bot commented on DOXIASITETOOLS-324: --- kwin opened a new

[PR] [DOXIASITETOOLS-324] Allow configuration of Doxia parser [maven-doxia-sitetools]

2024-01-04 Thread via GitHub
kwin opened a new pull request, #126: URL: https://github.com/apache/maven-doxia-sitetools/pull/126 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscr

[jira] [Created] (DOXIASITETOOLS-324) Allow configuration of parser (per markup source path pattern)

2024-01-04 Thread Konrad Windszus (Jira)
Konrad Windszus created DOXIASITETOOLS-324: -- Summary: Allow configuration of parser (per markup source path pattern) Key: DOXIASITETOOLS-324 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-324

[PR] Drop old TestNG, test with more recent ones [maven-surefire]

2024-01-04 Thread via GitHub
michael-o opened a new pull request, #710: URL: https://github.com/apache/maven-surefire/pull/710 Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/SUREFIRE) filed

Re: [PR] Bump org.testng:testng from 5.10 to 5.11 [maven-surefire]

2024-01-04 Thread via GitHub
dependabot[bot] commented on PR #677: URL: https://github.com/apache/maven-surefire/pull/677#issuecomment-1876707564 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version

Re: [PR] Bump org.testng:testng from 5.10 to 5.11 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o closed pull request #677: Bump org.testng:testng from 5.10 to 5.11 URL: https://github.com/apache/maven-surefire/pull/677 -- 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 commen

Re: [PR] Bump org.testng:testng from 5.10 to 5.11 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #677: URL: https://github.com/apache/maven-surefire/pull/677#issuecomment-1876707374 @slachiewicz Merged this to use a property. The rest requires more work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to G

Re: [PR] Bump org.testng:testng from 5.10 to 5.11 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #677: URL: https://github.com/apache/maven-surefire/pull/677#issuecomment-1876705583 > This is a very old dependency also with classifier java5 Should the classifier dropped or does it require more work? -- This is an automated message from the Apache Git S

Re: [PR] Bump org.testng:testng from 5.10 to 5.11 [maven-surefire]

2024-01-04 Thread via GitHub
slachiewicz commented on PR #677: URL: https://github.com/apache/maven-surefire/pull/677#issuecomment-1876696214 This is a very old dependency also with classifier java5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: [PR] Bump org.testng:testng from 5.10 to 5.11 [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #677: URL: https://github.com/apache/maven-surefire/pull/677#issuecomment-1876686868 @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 comm

Re: [PR] Bump org.htmlunit:htmlunit from 3.8.0 to 3.9.0 in /maven-failsafe-plugin/src/it/jetty-war-test-passing [maven-surefire]

2024-01-04 Thread via GitHub
michael-o merged PR #693: URL: https://github.com/apache/maven-surefire/pull/693 -- 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...@mave

Re: [PR] Bump org.htmlunit:htmlunit from 3.8.0 to 3.9.0 in /maven-failsafe-plugin/src/it/jetty-war-test-passing [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #693: URL: https://github.com/apache/maven-surefire/pull/693#issuecomment-1876685643 @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 comm

Re: [PR] Bump org.htmlunit:htmlunit from 3.8.0 to 3.9.0 in /maven-failsafe-plugin/src/it/jetty-war-test-failing [maven-surefire]

2024-01-04 Thread via GitHub
michael-o merged PR #694: URL: https://github.com/apache/maven-surefire/pull/694 -- 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...@mave

[jira] [Closed] (SUREFIRE-2229) [REGRESSION] SUREFIRE-2224 causes stack trace to be omitted for errors and failures

2024-01-04 Thread Michael Osipov (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed SUREFIRE-2229. Resolution: Fixed Fixed with [e7507601f4f6b10d82518fa5f3d32aab17e26d11|https://gitbox.a

Re: [PR] Bump org.htmlunit:htmlunit from 3.8.0 to 3.9.0 in /maven-failsafe-plugin/src/it/jetty-war-test-failing [maven-surefire]

2024-01-04 Thread via GitHub
michael-o commented on PR #694: URL: https://github.com/apache/maven-surefire/pull/694#issuecomment-1876684845 @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 comm

[jira] [Commented] (SUREFIRE-2229) [REGRESSION] SUREFIRE-2224 causes stack trace to be omitted for errors and failures

2024-01-04 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/SUREFIRE-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802630#comment-17802630 ] ASF GitHub Bot commented on SUREFIRE-2229: -- michael-o closed pull request #70

Re: [PR] [SUREFIRE-2229] [REGRESSION] SUREFIRE-2224 causes stack trace to be o… [maven-surefire]

2024-01-04 Thread via GitHub
michael-o closed pull request #709: [SUREFIRE-2229] [REGRESSION] SUREFIRE-2224 causes stack trace to be o… URL: https://github.com/apache/maven-surefire/pull/709 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo