| Failed to execute goal org.eclipse.xtend:xtend-maven-plugin:2.32.0:compile [message #1862363] |
Tue, 28 November 2023 19:07  |
 Steve Hickman
Messages: 56
Registered: August 2017 |
Member |
|
|
The linked build trace (out.txt) shows a failure of the xtend-maven-plugin. It appears that the 'plugin.xml' file in my XText UI project is being included in the resourceSet that the XTend compiler is trying to process - and not being filtered out by the NameBasedFilter. That would imply that the fileExtensionProvider has incorrectly gotten '.xml' as the file extension to filter for rather than '.xtend'. (XTendBatchCompiler, line 613). I have not yet tracked down how it got the wrong file extension.
Further, I should note that this failure occurred on the 4th XText based DSL in the stack of languages that I have. The first 3 built fine. That has left me trying to figure out what makes this DSL different.
Everything builds properly in Eclipse - this is a Maven specific build problem.
Further, this has built properly in the past. This failure did not occur until recently after I tried up move up to JDK 21. ( I did not know that 21 is not yet supported). I have reverted to JDK 17, cleared my Maven .m2 cache and started with a fresh Eclipse Workspace in case there was some 'bleed' over between Eclipse built artifacts and Maven. Still the error persists.
Suggestions on what else to look for?
NB: I am in the process of reverting back to the base XText generated grammars and then gradually re-adding all the manual code. I know I'll find this eventually. I wanted to surface this here because the Maven help indicated I should report plugin problems.
Attachment: out.txt
(Size: 746.27KB, Downloaded 53 times)
[Updated on: Tue, 28 November 2023 19:19] Report message to a moderator |
|
|
|
| Re: Failed to execute goal org.eclipse.xtend:xtend-maven-plugin:2.32.0:compile [message #1862378 is a reply to message #1862368] |
Wed, 29 November 2023 23:55  |
Steve Hickman
Messages: 56
Registered: August 2017 |
Member |
|
|
It appears this was caused by inclusion of the directory containing the Eclipse Editor Templates for my DSL in the build.properties 'source' set instead of the 'bin.includes' set. Yes, those are XML files. My guess is that there is some default to a zip file format.
I should note that the same error was in all 4 languages in my DSL stack but the error only showed up in the 4 one (the one that depended on the other 3). This may indicate that some kind of error was accumulating as I built each with Maven.
This is also a good lesson in addressing warnings - they might really be errors in disguise.
[Updated on: Thu, 30 November 2023 17:01] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03069 seconds
] 
Search
Help
Register
Login
Home
