Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Wed, 25 Nov 2015 12:54:10 +0000 (UTC)
From: =?utf-8?Q?Conny_Krey=C3=9Fel_=28JIRA=29?= <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12916084.1448442066000.190434.1448456050948@Atlassian.JIRA>
In-Reply-To: <JIRA.12916084.1448442066000@Atlassian.JIRA>
References: <JIRA.12916084.1448442066000@Atlassian.JIRA>
 <JIRA.12916084.1448442066953@arcas>
Subject: [jira] [Commented] (SUREFIRE-1198) Failsafe does not allow to use
 target/classes anymore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SUREFIRE-1198?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
5026712#comment-15026712 ]=20

Conny Krey=C3=9Fel 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 assign=
ed 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-boo=
t/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used a=
nymore. Is there a reason why this behaviour was completely removed in favo=
ur 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)