On Ġim, 2014-02-28 at 10:36 +0100, Karl Heinz Marbaise wrote:
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
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 si
No, this does not address my question at all.
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
Ka
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
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 lon
> 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.
Why are you doing this "every time you build"? This seems like the
kind of thing that s
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 lon
