[
https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358700#comment-358700
]
Tibor Digana commented on SUREFIRE-855:
---------------------------------------
@Benson
@Robert
I have updated my GitHub PR with the solution.
You may have a look. There is documentation update as well.
I might be worth to write an additional IT for checking existing jar resources
(properties, xml, etc.) via reading class loader resources.
> 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)
