You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@codehaus.org> on 2015/01/03 20:25:10 UTC

[jira] (SUREFIRE-855) Allow failsafe to use actual jar file instead of target/classes

     [ https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tibor Digana closed SUREFIRE-855.
---------------------------------

    Resolution: Fixed

commit	0eb85f7a2f971968a9293307616818a0d85f2ee8

> Allow failsafe to use actual jar file instead of target/classes
> ---------------------------------------------------------------
>
>                 Key: SUREFIRE-855
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-855
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin
>    Affects Versions: 2.12
>            Reporter: Benson Margulies
>            Assignee: Tibor Digana
>            Priority: Critical
>             Fix For: 2.19
>
>
> I've got some code that calls Class.getPackage() to see the manifest. I want to test it. A seemingly logical scheme here would be to have failsafe put the actual packaged jar into the classpath instead of the unpacked directory -- or some way to get the manifest copied across.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)