[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357861#comment-15357861
]
Robert Scholte edited comment on SUREFIRE-1198 at 7/1/16 7:52 PM:
------------------------------------------------------------------
IIUC the Spring Boot jar is a jar-in-name-only: it doesn't follow the
specifications of a jar, classes are not in the root but in a subdirectory. I
assume you're using a custom classloader to execute this jar, which means that
the maven-failsafe-plugin should do the same.
was (Author: rfscholte):
IIUC the Spring Boot jar is a jar-in-name-only: it doesn't follow the
specifications of a jar, classes are not in the root but in a subdirectory. I
assume you're using a custom classloader to execute this jar, which means that
the maven-surefire-plugin should do the same.
> Failsafe does not allow to configure the jar file to use
> --------------------------------------------------------
>
> Key: SUREFIRE-1198
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Stephane Nicoll
>
> See [this Spring Boot
> issue|https://github.com/spring-projects/spring-boot/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used
> anymore. Is there a reason why this behaviour was completely removed in
> favour of only the jar file?
> It would be nice if we had an option to chose between the two (defaulting to
> the jar)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)