Hello,
I'm building some Eclipse plug ins with Maven, and because of the
requirements, I'm not using the Felix bundle plug in, I'm making the bundle
using some Ant tasks, the dependency:copy goal and some other things.
I'm trying to:
- compile the classes (target/classes)
- jar them and put the jar in another folder
(target/osgi-bundle-symbolic-name/jarname.jar)
- sign the resulting jar (I don't change the name)
I'm copying the key store at the process-resources phase, and I'm making the
jar at the compile phase.
However, jar signing does not work:
________________________________________________________
[INFO] [jar:sign {execution: jar-classes}]
[DEBUG] Not executing jar:sign as the project is not a Java module
________________________________________________________
Project packaging is zip, it's basically an OSGi unpacked bundle put in a
zip: a folder which has a jar, a META-INF folder, and some other things in
there.
Any ideas? I found some bug reports regarding something similar, but I'm not
sure they're related.
http://jira.codehaus.org/browse/MJAR-20
I do have the target/classes folder at compile time, it looks like something
in the check is wrong. Are there any workarounds?
PS: I know about making a different module for the jar itself, I don't
really want to pollute the project structure with additional folders, I
already have 70. If I make 30 more, it will be even more confusing. I
believe I will still have to make an additional module, because I might have
to publish the simple jar too...
However, does anyone know if I can make it work without additional modules?
Thank you,
Costin.
--
View this message in context:
http://www.nabble.com/Problems-with-jar-signing-tp20705582p20705582.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]
