[
https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358238#comment-358238
]
Robert Scholte commented on SUREFIRE-855:
-----------------------------------------
I haven't worked with bundles, so I can't help you there. Maybe the answer lies
within a OSGi container implementation itself.
> 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
> Priority: Critical
>
> 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)
