[jira] [Commented] (MINVOKER-348) Build job report is truncated
[ https://issues.apache.org/jira/browse/MINVOKER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731567#comment-17731567 ] Alvaro Sanchez-Mariscal commented on MINVOKER-348: -- I debugged it and saw an {{IllegalStateException: character 27 is not allowed in output}} being thrown, in case it helps. > Build job report is truncated > - > > Key: MINVOKER-348 > URL: https://issues.apache.org/jira/browse/MINVOKER-348 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Alvaro Sanchez-Mariscal >Priority: Major > Attachments: BUILD-test-resources.xml, build.log > > > The build-job.xml generated for a project is truncated: > {code:xml} > > result="failure-post-hook" time="42.662" > buildlog="/Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/target/it/test-resources/build.log"> > Assertion failed: > assert log.text.contains("BUILD SUCCESS") >| || >| |false >| '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< > {code} > Examining the build output, it gets truncated after a {{<}} appears, which is > replaced in the XML with {{<}};, but then nothing else. Snippet following > {noformat} > [INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< io.micronaut.build.examples:test-resources > >-\n[INFO] > {noformat} > Then, the verify mojo crashes when reading such file: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) > on project micronaut-maven-integration-tests: Failed to read report file: > /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: > no more data available - expected end tags to > close start tag from line 3 and start tag from > line 2, parser stopped on START_TAG seen ...t part of the build > invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MINVOKER-348) Build job report is truncated
[ https://issues.apache.org/jira/browse/MINVOKER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvaro Sanchez-Mariscal updated MINVOKER-348: - Description: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{<}};, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} was: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{& lt}}, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} > Build job report is truncated > - > > Key: MINVOKER-348 > URL: https://issues.apache.org/jira/browse/MINVOKER-348 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Alvaro Sanchez-Mariscal >Priority: Major > Attachments: BUILD-test-resources.xml, build.log > > > The build-job.xml generated for a project is truncated: > {code:xml} > > result="failure-post-hook" time="42.662" > buildlog="/Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/target/it/test-resources/build.log"> > Assertion failed: > assert log.text.contains("BUILD SUCCESS") >| || >| |false >| '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< > {code} > Examining the build output, it gets truncated after a {{<}} appears, which is > replaced in the XML with {{<}};, but then nothing else. Snippet following > {noformat} > [INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< io.micronaut.build.examples:test-resources > >-\n[INFO] > {noformat} > Then, the verify mojo crashes when reading such file: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-
[jira] [Updated] (MINVOKER-348) Build job report is truncated
[ https://issues.apache.org/jira/browse/MINVOKER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvaro Sanchez-Mariscal updated MINVOKER-348: - Description: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{<}};, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {noformat} was: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{<}};, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} > Build job report is truncated > - > > Key: MINVOKER-348 > URL: https://issues.apache.org/jira/browse/MINVOKER-348 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Alvaro Sanchez-Mariscal >Priority: Major > Attachments: BUILD-test-resources.xml, build.log > > > The build-job.xml generated for a project is truncated: > {code:xml} > > result="failure-post-hook" time="42.662" > buildlog="/Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/target/it/test-resources/build.log"> > Assertion failed: > assert log.text.contains("BUILD SUCCESS") >| || >| |false >| '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< > {code} > Examining the build output, it gets truncated after a {{<}} appears, which is > replaced in the XML with {{<}};, but then nothing else. Snippet following > {noformat} > [INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< io.micronaut.build.examples:test-resources > >-\n[INFO] > {noformat} > Then, the verify mojo crashes when reading such file: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-t
[jira] [Updated] (MINVOKER-348) Build job report is truncated
[ https://issues.apache.org/jira/browse/MINVOKER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvaro Sanchez-Mariscal updated MINVOKER-348: - Description: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{& lt}}, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} was: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{&<}}, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} > Build job report is truncated > - > > Key: MINVOKER-348 > URL: https://issues.apache.org/jira/browse/MINVOKER-348 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Alvaro Sanchez-Mariscal >Priority: Major > Attachments: BUILD-test-resources.xml, build.log > > > The build-job.xml generated for a project is truncated: > {code:xml} > > result="failure-post-hook" time="42.662" > buildlog="/Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/target/it/test-resources/build.log"> > Assertion failed: > assert log.text.contains("BUILD SUCCESS") >| || >| |false >| '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< > {code} > Examining the build output, it gets truncated after a {{<}} appears, which is > replaced in the XML with {{& lt}}, but then nothing else. Snippet following > {noformat} > [INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< io.micronaut.build.examples:test-resources > >-\n[INFO] > {noformat} > Then, the verify mojo crashes when reading such file: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integratio
[jira] [Updated] (MINVOKER-348) Build job report is truncated
[ https://issues.apache.org/jira/browse/MINVOKER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvaro Sanchez-Mariscal updated MINVOKER-348: - Description: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{&<}}, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} was: The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{<}}, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} > Build job report is truncated > - > > Key: MINVOKER-348 > URL: https://issues.apache.org/jira/browse/MINVOKER-348 > Project: Maven Invoker Plugin > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Alvaro Sanchez-Mariscal >Priority: Major > Attachments: BUILD-test-resources.xml, build.log > > > The build-job.xml generated for a project is truncated: > {code:xml} > > result="failure-post-hook" time="42.662" > buildlog="/Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/target/it/test-resources/build.log"> > Assertion failed: > assert log.text.contains("BUILD SUCCESS") >| || >| |false >| '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< > {code} > Examining the build output, it gets truncated after a {{<}} appears, which is > replaced in the XML with {{&<}}, but then nothing else. Snippet following > {noformat} > [INFO] Error stacktraces are turned on.\n[INFO] Scanning for > projects...\n[WARNING] This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] > -< io.micronaut.build.examples:test-resources > >-\n[INFO] > {noformat} > Then, the verify mojo crashes when reading such file: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-tes
[jira] [Created] (MINVOKER-348) Build job report is truncated
Alvaro Sanchez-Mariscal created MINVOKER-348: Summary: Build job report is truncated Key: MINVOKER-348 URL: https://issues.apache.org/jira/browse/MINVOKER-348 Project: Maven Invoker Plugin Issue Type: Bug Affects Versions: 3.5.1 Reporter: Alvaro Sanchez-Mariscal Attachments: BUILD-test-resources.xml, build.log The build-job.xml generated for a project is truncated: {code:xml} Assertion failed: assert log.text.contains("BUILD SUCCESS") | || | |false | '[INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< {code} Examining the build output, it gets truncated after a {{<}} appears, which is replaced in the XML with {{<}}, but then nothing else. Snippet following {noformat} [INFO] Error stacktraces are turned on.\n[INFO] Scanning for projects...\n[WARNING] This build will only read from the build cache, since the clean lifecycle is not part of the build invocation.\n[INFO] \n[INFO] -< io.micronaut.build.examples:test-resources >-\n[INFO] {noformat} Then, the verify mojo crashes when reading such file: {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-invoker-plugin:3.5.1:verify (integration-test) on project micronaut-maven-integration-tests: Failed to read report file: /Users/alvaro/Dev/micronaut-projects/micronaut-maven-plugin/micronaut-maven-integration-tests/target/invoker-reports/BUILD-test-resources.xml: no more data available - expected end tags to close start tag from line 3 and start tag from line 2, parser stopped on START_TAG seen ...t part of the build invocation.\n[INFO] \n[INFO] -<... @8:242 -> [Help 1] {nofirmat} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules
[ https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515766#comment-17515766 ] Alvaro Sanchez-Mariscal commented on MCOMPILER-391: --- Is the Maven team still interested in fixing this issue? If so, I could help to put together a PR, test it, or whatever else that is needed. > annotationProcessorPaths have to follow dependencyManagement rules > -- > > Key: MCOMPILER-391 > URL: https://issues.apache.org/jira/browse/MCOMPILER-391 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.8.0 >Reporter: Stanislav Spiridonov >Priority: Blocker > Attachments: MCOMPILER-391.zip > > > # Use the version from dependency management > # Respect the exclude (blocker for me) -- This message was sent by Atlassian Jira (v8.20.1#820001)