[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] [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] [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]
{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 {{<}};, 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] [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] [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)
[jira] [Commented] (MPLUGIN-524) "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null" with Nexus Staging plugin
[
https://issues.apache.org/jira/browse/MPLUGIN-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893788#comment-17893788
]
Alvaro Sanchez-Mariscal commented on MPLUGIN-524:
-
[~cstamas] it is false that this is caused by a missing prefix. I've always had
a
[prefix|https://github.com/micronaut-projects/micronaut-maven-plugin/blob/4.7.x/micronaut-maven-plugin/pom.xml#L155].
On
[Central|https://repo1.maven.org/maven2/io/micronaut/maven/maven-metadata.xml]
there is a prefix (although different?), whilst on
[s01|https://s01.oss.sonatype.org/content/repositories/snapshots/io/micronaut/maven/maven-metadata.xml]
there isn't.
Regarding the Nexus Staging plugin, I think we all followed Sonatype's
recommendation here. What is your advise for today's Maven 3? Just use
maven-deploy-plugin? Because as far as I can tell, it won't do releases with a
staging workflow that implies:
* Staging locally.
* Creating a private staging remote repository.
* Performing atomic upload into staging repository.
* Closing staging repo (or dropping if upload failed).
The closest would be {{m-d-p}}'s {{deployAtEnd}}, but if I'm not mistaken, it
doesn't perform a "transactional release", and considering that Sonatype won't
delete incomplete release artifacts, I see a high risk here,
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix() is null"
> with Nexus Staging plugin
>
>
> Key: MPLUGIN-524
> URL: https://issues.apache.org/jira/browse/MPLUGIN-524
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Metadata Model
>Affects Versions: 3.13.0
>Reporter: Tristan Tarrant
>Priority: Major
>
> While attempting to release a plugin with nexus-staging-maven-plugin, I get
> the following exception:
> {noformat}
> [ERROR] Failed to execute goal
> org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getPrefix()" is null ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy
> (injected-nexus-deploy) on project proto-schema-compatibility-maven-plugin:
> Failed to update metadata org.infinispan.maven-plugins/maven-metadata.xml:
> Cannot invoke "String.equals(Object)" because the return value of
> "org.apache.maven.artifact.repository.metadata.Plugin.getP refix()" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:333)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher
