You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Enrico Olivelli (JIRA)" <ji...@apache.org> on 2018/12/01 11:24:00 UTC
[jira] [Comment Edited] (SUREFIRE-1602) Surefire fails loading
class ForkedBooter when using a sub-directory pom file and a local maven
repo
[ https://issues.apache.org/jira/browse/SUREFIRE-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705783#comment-16705783 ]
Enrico Olivelli edited comment on SUREFIRE-1602 at 12/1/18 11:23 AM:
---------------------------------------------------------------------
when running with "-file ./integration-tests" the surefirebooter.jar conains entries like this one:
Manifest-Version: 1.0
Class-Path: ../../../../maven_local_repo/org/apache/maven/surefire/sur
efire-booter/3.0.0-M1/surefire-booter-3.0.0-M1.jar
when running with "-file integration-tests" the surefirebooter.jar contains entries like this one:
Manifest-Version: 1.0
Class-Path: ../../../maven_local_repo/org/apache/maven/surefire/surefi
re-booter/3.0.0-M1/surefire-booter-3.0.0-M1.jar
I guess the problem is about having a wrong number of '../'
was (Author: eolivelli):
when running with "./" the surefirebooter.jar conains entries like this one:
Manifest-Version: 1.0
Class-Path: ../../../../maven_local_repo/org/apache/maven/surefire/sur
efire-booter/3.0.0-M1/surefire-booter-3.0.0-M1.jar
I guess the problem is about having a wrong number of '../'
> Surefire fails loading class ForkedBooter when using a sub-directory pom file and a local maven repo
> ----------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1602
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1602
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 3.0.0-M1
> Environment: maven 3.6.0 open-jdk-8 (docker image maven:3.6.0-open-jdk-8)
> Reporter: Daniel Kurzynski
> Priority: Major
> Attachments: execute_error.txt, execute_ok.txt
>
>
> Steps to reproduce:
> Use a docker image for maven:3.6 (docker run -it maven:3.6.0-jdk-8 bash)
> Inside generate a new project:
> {code:java}
> mvn archetype:generate \
> -DinteractiveMode=false \
> -DarchetypeGroupId=com.sap.cloud.s4hana.archetypes \
> -DarchetypeArtifactId=scp-cf-tomee \
> -DarchetypeVersion=2.7.0 \
> -DgroupId=com.sap.cloud.sdk.tutorial \
> -DartifactId=testapp\
> -Dversion=1.0-SNAPSHOT \
> -Dpackage=com.sap.cloud.s4hana.examples{code}
> In the folder testapp set surefire version to 3.0.0-M1 in unit-tests/pom.xml and integration-tests/pom.xml
> Build the project
> {code:java}
> mvn -Dmaven.repo.local=maven_local_repo -Dmaven.test.skip clean install{code}
> Running the tests afterwards will fail
> {code:java}
> mvn test -Dmaven.repo.local=maven_local_repo --file ./integration-tests/pom.xml{code}
> The error message in the logs is:
> Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter
> However, it only fails when using ./ in the beginning of the file parameter in combination with having a local maven repo.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)