[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359561#comment-15359561
]
Robert Scholte commented on SUREFIRE-1198:
------------------------------------------
Failsafe *prefers* to use the jar. If you bind it to an earlier phase when
there's no jar, it'll use the folder with the test-classes. But then you should
wonder why not using the maven-surefire-plugin instead?
So I had a look at the {{Spring-Boot-Maven-Failsafe-Plugin-Issue-master}}
project. It seems like you've decided to introduce a {{BOOT-INFO/classes}}, the
{{META-INF/MANIFEST.MF}} has an entry to this folder.
This made me aware that the plugin is actually still not good enough. In case
of an executable jar ( i.e the Main-Class entry is specified) where the
Class-Path is specified as well, it should use those entries. Spring Boot does
something similar, but with own specified entries.
So the fix should be to be able to map or redirect classes.
> 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)
