[
https://jira.codehaus.org/browse/SUREFIRE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358268#comment-358268
]
Tibor Digana commented on SUREFIRE-855:
---------------------------------------
Benson, can you make a temporary workaround proposed by Robert? I want to know
if we break the current PAX users.
The fix seems to be quite doable.
Can somebody tell me if we have an artifact with EAR, WAR ClassLoaders in Maven
project?
I can get the JAR file path quite easily in order to fallback to JAR (if any
exists):
MavenProject#getModel().getBuild().getDirectory()
MavenProject#getModel().getBuild().getFinalName()
If the JAR file does not exist, I will fallback to
${project.build.outputDirectory}.
> 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)
