maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conny Kreyßel (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1198) Failsafe does not allow to use target/classes anymore
Date Wed, 25 Nov 2015 12:54:10 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026712#comment-15026712
] 

Conny Kreyßel commented on SUREFIRE-1198:
-----------------------------------------

At first this sounds fully correct to me.

But in second you ignore that some plugins reassemble the jar (shade-plugin or spring-boot-maven-plugin).
That means in intergration tests is not the "original" jar attached and used, but the "repackaged"
jar.

If you use the repackaged jar in integration test, you have also the assigned dependencies
artifacts in classpath. This is really a bad situation.

Maybe the default should use the jar in intergration tests - but we should have a swicth to
disable this and use target/classes instead.

> Failsafe does not allow to use target/classes anymore
> -----------------------------------------------------
>
>                 Key: SUREFIRE-1198
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
>             Project: Maven Surefire
>          Issue Type: Bug
>            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)

Mime
View raw message