[jira] [Commented] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792704#comment-17792704 ] ASF GitHub Bot commented on SUREFIRE-2219: -- michael-o commented on PR #692: URL:

Re: [PR] [SUREFIRE-2219] Add test stdErr/stdOut output to ReportTestCase [maven-surefire]

michael-o commented on PR #692: URL: https://github.com/apache/maven-surefire/pull/692#issuecomment-1838012229 Thanks, I will look into this shortly. I also need to put other PRs into consider because of memory consumption, etc. -- This is an automated message from the Apache Git

[jira] [Commented] (SUREFIRE-2211) additionalClasspathElement with UNC path not working with Maven Failsafe Plugin

[ https://issues.apache.org/jira/browse/SUREFIRE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792647#comment-17792647 ] ASF GitHub Bot commented on SUREFIRE-2211: -- robseidel commented on PR #689: URL:

Re: [PR] [SUREFIRE-2211] Fix UNC classpath elements [maven-surefire]

robseidel commented on PR #689: URL: https://github.com/apache/maven-surefire/pull/689#issuecomment-1837898208 I've now restored the commit message. -- 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

[PR] Bump com.github.luben:zstd-jni from 1.5.5-10 to 1.5.5-11 [maven-assembly-plugin]

dependabot[bot] opened a new pull request, #170: URL: https://github.com/apache/maven-assembly-plugin/pull/170 Bumps [com.github.luben:zstd-jni](https://github.com/luben/zstd-jni) from 1.5.5-10 to 1.5.5-11. Commits

[jira] [Commented] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792636#comment-17792636 ] Alexander Kriegisch commented on SUREFIRE-2219: --- [~michael-o], done, please refer to the

[jira] [Commented] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792633#comment-17792633 ] ASF GitHub Bot commented on SUREFIRE-2219: -- kriegaex opened a new pull request, #692: URL:

[PR] [SUREFIRE-2219] Add test stdErr/stdOut output to ReportTestCase [maven-surefire]

kriegaex opened a new pull request, #692: URL: https://github.com/apache/maven-surefire/pull/692 `TestSuiteXmlParser` no longer ignores the `system-out` and `system-err` tags from the Surefire report XML. It parses them and sets the corresponding properties in `ReportTestCase`.

[jira] [Commented] (MRELEASE-1109) update-versions removes the CI-friendly ${revisions}

[ https://issues.apache.org/jira/browse/MRELEASE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792589#comment-17792589 ] ASF GitHub Bot commented on MRELEASE-1109: -- michael-o commented on code in PR #202: URL:

Re: [PR] [MRELEASE-1109] Snapshot detection and support for versions like `${revision}${sha1}${changelist}` [maven-release]

michael-o commented on code in PR #202: URL: https://github.com/apache/maven-release/pull/202#discussion_r1413214047 ## maven-release-manager/src/main/java/org/apache/maven/shared/release/transform/jdom2/JDomModel.java: ## @@ -198,7 +199,17 @@ public void setVersion(String

[jira] [Commented] (MRELEASE-1109) update-versions removes the CI-friendly ${revisions}

[ https://issues.apache.org/jira/browse/MRELEASE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792588#comment-17792588 ] ASF GitHub Bot commented on MRELEASE-1109: -- michael-o commented on code in PR #202: URL:

Re: [PR] [MRELEASE-1109] Snapshot detection and support for versions like `${revision}${sha1}${changelist}` [maven-release]

michael-o commented on code in PR #202: URL: https://github.com/apache/maven-release/pull/202#discussion_r1413213842 ## maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/AbstractRewritePomsPhase.java: ## @@ -96,7 +96,7 @@ public abstract class

[jira] [Commented] (MBUILDCACHE-76) pom project version change not detected

[ https://issues.apache.org/jira/browse/MBUILDCACHE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792587#comment-17792587 ] Olivier Lamy commented on MBUILDCACHE-76: - We cannot have a full rebuild here as this would

[jira] [Commented] (DOXIA-699) Xhtml5Parser may emit sectionX() without sectionX_()

[ https://issues.apache.org/jira/browse/DOXIA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792566#comment-17792566 ] ASF GitHub Bot commented on DOXIA-699: -- michael-o commented on PR #162: URL:

Re: [PR] [DOXIA-699] Add simple failing test case [maven-doxia]

michael-o commented on PR #162: URL: https://github.com/apache/maven-doxia/pull/162#issuecomment-1837593487 I believe that our parsing assumptions are wrong. [This](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements?retiredLocale=de) says nothing that we need a ``.

[jira] [Commented] (DOXIA-709) Clarify usage of overlapping Sink methods

[ https://issues.apache.org/jira/browse/DOXIA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792565#comment-17792565 ] Michael Osipov commented on DOXIA-709: -- Yes, there is some inconsistency...can you provide a PR for

[jira] [Updated] (SUREFIRE-2212) OutOfMemoryError raised when parsing files with a lot of std-err information in surefire-report-parser

[ https://issues.apache.org/jira/browse/SUREFIRE-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SUREFIRE-2212: - Fix Version/s: 3.x-candidate > OutOfMemoryError raised when parsing files with a lot

[jira] [Assigned] (SUREFIRE-2212) OutOfMemoryError raised when parsing files with a lot of std-err information in surefire-report-parser

[ https://issues.apache.org/jira/browse/SUREFIRE-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SUREFIRE-2212: Assignee: Michael Osipov > OutOfMemoryError raised when parsing files with a

[jira] [Updated] (MBUILDCACHE-76) pom project version change not detected

[ https://issues.apache.org/jira/browse/MBUILDCACHE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Moten updated MBUILDCACHE-76: -- Description: When I run `mvn versions:set -DnewVersion=BLAH`, the build cache extension

[jira] [Updated] (MBUILDCACHE-76) pom project version change not detected

[ https://issues.apache.org/jira/browse/MBUILDCACHE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Moten updated MBUILDCACHE-76: -- Description: When I run `mvn versions:set -DnewVersion=BLAH`, the build cache extension

[jira] [Updated] (MENFORCER-484) [Question/Bug?] about requireSameVersion

[ https://issues.apache.org/jira/browse/MENFORCER-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MENFORCER-484: - Fix Version/s: (was: waiting-for-feedback) > [Question/Bug?] about

[jira] [Commented] (SUREFIRE-1576) Spring Boot Context Failure using Surefire Plugin and -f ./pom.xml

[ https://issues.apache.org/jira/browse/SUREFIRE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792564#comment-17792564 ] Michael Osipov commented on SUREFIRE-1576: -- I have tried to reproduce this on a recent Spring

[jira] [Updated] (SUREFIRE-1576) Spring Boot Context Failure using Surefire Plugin and -f ./pom.xml

[ https://issues.apache.org/jira/browse/SUREFIRE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SUREFIRE-1576: - Fix Version/s: waiting-for-feedback > Spring Boot Context Failure using Surefire

[jira] [Commented] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792563#comment-17792563 ] Michael Osipov commented on SUREFIRE-2219: -- Well, you don't need any HTML/CSS skills, all is

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

[ https://issues.apache.org/jira/browse/DOXIA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792562#comment-17792562 ] ASF GitHub Bot commented on DOXIA-710: -- michael-o commented on PR #180: URL:

Re: [PR] [DOXIASITETOOLS-320] Auto-generate anchor for TOC entries [maven-doxia]

michael-o commented on PR #180: URL: https://github.com/apache/maven-doxia/pull/180#issuecomment-1837574750 > > I don't see need to modify/intercept the sink at all, a parser can do this perfectly with some buffering. TOCMacro does this buffering with a fresh parser as well. > > The

[jira] [Comment Edited] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792540#comment-17792540 ] Alexander Kriegisch edited comment on SUREFIRE-2219 at 12/3/23 3:26 PM:

[jira] [Comment Edited] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792540#comment-17792540 ] Alexander Kriegisch edited comment on SUREFIRE-2219 at 12/3/23 3:26 PM:

[jira] [Comment Edited] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792540#comment-17792540 ] Alexander Kriegisch edited comment on SUREFIRE-2219 at 12/3/23 3:24 PM:

[jira] [Commented] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792540#comment-17792540 ] Alexander Kriegisch commented on SUREFIRE-2219: --- [~michael-o], that was not my plan, and

Re: [PR] Use Maven 3.9.6 as default [maven-gh-actions-shared]

slawekjaranowski merged PR #87: URL: https://github.com/apache/maven-gh-actions-shared/pull/87 -- 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:

[jira] [Commented] (SUREFIRE-2219) Option to include stdOut/stdErr console logs into test report

[ https://issues.apache.org/jira/browse/SUREFIRE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792521#comment-17792521 ] Michael Osipov commented on SUREFIRE-2219: -- I see OK. Do you want to give it a try? I'd be

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

[ https://issues.apache.org/jira/browse/DOXIA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792508#comment-17792508 ] ASF GitHub Bot commented on DOXIA-710: -- kwin commented on PR #180: URL:

Re: [PR] [DOXIASITETOOLS-320] Auto-generate anchor for TOC entries [maven-doxia]

kwin commented on PR #180: URL: https://github.com/apache/maven-doxia/pull/180#issuecomment-1837439220 > I don't see need to modify/intercept the sink at all, a parser can do this perfectly with some buffering. TOCMacro does this buffering with a fresh parser as well. The point is

[jira] [Commented] (MINSTALL-187) Switch to the new maven 4 api

[ https://issues.apache.org/jira/browse/MINSTALL-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792498#comment-17792498 ] ASF GitHub Bot commented on MINSTALL-187: - gnodet commented on code in PR #35: URL:

Re: [PR] [MINSTALL-187] Switch to the new maven 4 api [maven-install-plugin]

gnodet commented on code in PR #35: URL: https://github.com/apache/maven-install-plugin/pull/35#discussion_r1413028746 ## pom.xml: ## @@ -169,24 +131,39 @@ org.slf4j - slf4j-api + slf4j-nop ${slf4jVersion} - provided + test