You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/02/01 09:48:00 UTC
[jira] [Comment Edited] (MNG-7087) Maven 4 can't build itself with
Java 11
[ https://issues.apache.org/jira/browse/MNG-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275747#comment-17275747 ]
Michael Osipov edited comment on MNG-7087 at 2/1/21, 9:47 AM:
--------------------------------------------------------------
Here is the cause:
!screenshot-1.png!
To make it even worse, the close method is never called from the wrapped input stream so we never see {{throw new RuntimeException( "Failed to transform pom", t );}}.
The actual error is:
{noformat}
ERROR: ''
FATAL_ERR_MSG
ERROR_MSG
./src/java.xml/share/classes/com/sun/org/apache/xalan/internal/xsltc/compiler/util/ErrorMessages.java
{noformat}
was (Author: michael-o):
Here is the cause:
!screenshot-1.png!
To make it even worse, the close method is never called from the wrapped input stream so we never see [[throw new RuntimeException( "Failed to transform pom", t );}}.
The actual error is:
{noformat}
ERROR: ''
FATAL_ERR_MSG
ERROR_MSG
./src/java.xml/share/classes/com/sun/org/apache/xalan/internal/xsltc/compiler/util/ErrorMessages.java
{noformat}
> Maven 4 can't build itself with Java 11
> ---------------------------------------
>
> Key: MNG-7087
> URL: https://issues.apache.org/jira/browse/MNG-7087
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-alpha-1
> Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT (bb916d0784c7631866167928e4d0615df3317567)
> Java version: 11.0.10, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
> Reporter: Maarten Mulders
> Priority: Blocker
> Fix For: 4.0.x-candidate
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> It's not possible to build Maven HEAD (I've tested with rev. bb916d0) using a recent Maven 4 snapshot. Even {{mvn validate}} doesn't succeed:
> {code}
> [INFO] Scanning for projects...
> ERROR: ''
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.junit.jupiter:junit-jupiter-params:jar -> version ${junitVersion} vs 5.7.0 @ line 77, column 17
> [FATAL] input contained no data @
> @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project (/Users/maarten/Code/open-source/maven/maven/maven-model-builder/pom.xml) has 1 error
> [ERROR] input contained no data
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e' switch.
> [ERROR] Re-run Maven using the '-X' switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> {code}
> I've done `git bisect` (first time, I hope I did it correctly):
> {code}
> 9f88494b6064ad45ea2e2e1e3478afc7af0bc065 is the first bad commit
> Author: rfscholte
> Date: Mon Dec 21 22:23:43 2020 +0100
> [MNG-6957] Versionless reactor dependencies/parent should work even if modules are aggregated in reverse order
>
> This closes #391
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)