I'll rephrase the question: can I sign a jar using Maven, if that jar is not
the final package of the project?
0. Compile some .java files -> compile phase of the artifact build.
1. Jar the resulting classes -> compile phase of the artifact build.
2. Sign the jar -> compile phase of the artifact build.
3. Move the jar somewhere in /target/classes -> process-classes phase of the
artifact build.
4. Package /target/classes (including the jar) as a zip -> package phase of
the artifact build.
So this includes just 1 build lifecycle.
Right now I get:
________________________________________________________
[INFO] [jar:sign {execution: jar-classes}]
[DEBUG] Not executing jar:sign as the project is not a Java module
________________________________________________________
Right now I think I have 2 options:
1. make a different artifact for the jar, which I'll include in the zip
(makes the build more complex).
2. use Ant, called from antrun, to sign the jar.
Any other workarounds for this?
Regards,
Costin.
--
View this message in context:
http://www.nabble.com/Problems-with-jar-signing-tp20705582p20719492.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
