Hi,
No, this does not address my question at all.
Hm...you make a separate project and define your needed artifacts as
dependencies and maven-jarsigner-plugin will sign all artifacts and will
deploy them as attached to that projects.
The other projects (yours) can use those attached and signed artifacts ?
Kind regards
Karl Heinz Marbaise
On Ġim, 2014-02-28 at 08:55 +0100, Karl Heinz Marbaise wrote:
Hi Ramon,
what about:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
Kind regards
Karl Heinz Marbaise
> I have an application which depends on a large number of 3rd party
> artifacts, and which uses webstart to launch. Webstart requires all
Jars
> to be signed using the same certificate. Although the
> webstart-maven-plugin can take care of the signing, there are so many
> jar files that it takes quite a long time to sign them all every time
I
> build.
>
> Since the 3rd party artifacts rarely change, I'd like to sign them
all
> once, and store them in a local repository and have the projects all
> depend on the signed versions. Is there any quick way of doing this?
>
> I was thinking of something like a maven project for each dependency
> which pulls in the JAR, signs it then deploys it to my repository
using
> a modified version number
> (eg, commons.beanutils-1.8.3.jar ->
commons.beanutils-1.8.3-signed.jar).
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
