[
https://issues.apache.org/jira/browse/MJARSIGNER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJARSIGNER-20.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> It should be possible to assign a new classifier to the signed artifact
> -----------------------------------------------------------------------
>
> Key: MJARSIGNER-20
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-20
> Project: Maven Jar Signer Plugin
> Issue Type: New Feature
> Affects Versions: 1.2
> Reporter: Sven Kirmess
>
> It should be possible to assign a new classifier to the signed artifact. At
> the moment I can't use this together with the surefire plugin because I get a
> security exception.
> java.lang.SecurityException: class "XYZ"'s signer information does not match
> signer information of other classes in the same package
> I would like to have to artifacts on my nexus server. The default one which
> is unsigned and one with classifier KEYSTORE which is signed with KEYSTORE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
