Impossible to Build the Project Due Broken jcabi-xcop Check

[volodya-lombrozo]

I pull repository (master branch) and then run the following command:

mvn clean install -DskipTests -DskipITs

I get the following error immediately:

[INFO] --- antrun:3.1.0:run (jcabi-xcop) @ eo-parent ---
[INFO] Executing tasks
[INFO]      [exec] * SPDX-FileCopyrightText: Copyright (c) 2016-2025 Objectionary.com\n
[INFO]      [exec]  * SPDX-License-Identifier: MITThe MIT License (MIT)\n
[INFO]      [exec] \n
[INFO]      [exec] Copyright (c) 2016-2025 Objectionary.com\n
[INFO]      [exec] \n
[INFO]      [exec] Permission is hereby granted, free of charge, to any person obtaining a copy\n
[INFO]      [exec] of this software and associated documentation files (the "Software"), to deal\n
[INFO]      [exec] in the Software without restriction, including without limitation the rights\n
[INFO]      [exec] to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n
[INFO]      [exec] copies of the Software, and to permit persons to whom the Software is\n
[INFO]      [exec] furnished to do so, subject to the following conditions:\n
[INFO]      [exec] \n
[INFO]      [exec] The above copyright notice and this permission notice shall be included\n
[INFO]      [exec] in all copies or substantial portions of the Software.\n
[INFO]      [exec] \n
[INFO]      [exec] THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n
[INFO]      [exec] IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n
[INFO]      [exec] FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE\n
[INFO]      [exec] AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n
[INFO]      [exec] LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n
[INFO]      [exec] OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\n
[INFO]      [exec] SOFTWARE.
[INFO]      [exec] Broken license in /Users/lombrozo/Workspace/EOlang/eo/eo-maven-plugin/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for eo 1.0-SNAPSHOT:
[INFO] 
[INFO] eo ................................................. FAILURE [  2.127 s]
[INFO] eo-parser .......................................... SKIPPED
[INFO] eo-maven-plugin .................................... SKIPPED
[INFO] eo-runtime ......................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.600 s
[INFO] Finished at: 2025-02-26T14:30:46+03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:3.1.0:run (jcabi-xcop) on project eo-parent: An Ant BuildException has occured: exec returned: 255
[ERROR] around Ant part ...<exec failonerror="true" executable="xcop">... @ 50:56 in /Users/lombrozo/Workspace/EOlang/eo/target/antrun/build-main.xml
[ERROR] -> [Help 1]

Thus, it's impossible to build the project.

[volodya-lombrozo]

I got similar issue and had to disable jcabi-xcop execution to avoid this issue:

<plugin>
	<artifactId>maven-antrun-plugin</artifactId>
	<version>3.1.0</version>
	<executions>
		<execution>
			<id>jcabi-xcop</id>
			<phase>none</phase>
			<goals>
				<goal>run</goal>
			</goals>
		</execution>
	</executions>
</plugin>

[volodya-lombrozo]

@yegor256 Could you have a look, please?

[h1alexbel]

@volodya-lombrozo having the same issue. I'm just wondering why it passes on master branch

[maxonfjvipon]

@volodya-lombrozo @h1alexbel I had the same issue today and fixed it. You need to update your local xcop version to the latest one (which is 0.8.0). To check the version run locally xcop --version. If you've updated xcop and xcop --version shows 0.8.0 but you still get the error, run which xcop, you get the path, copy the path and add --version in the end. The 99% you get the wrong version, just remove the file and it should work now

[h1alexbel]

@maxonfjvipon indeed, now it works. Thanks!