|Re: [cross-project-issues-dev] Deprecating the command line JAR signing service (aka /usr/bin/sign) - read if you use Buckminster|
SamActually, I am still not able to get this to work. It resolves the plugin now but it doesn't seem to do anything.How is it meant to work?
The documentation for eclipse-jarsigner is a bit lacking. I would assume that if you invoke the plugin from a pom, it will replace all .jar files in the directory containing that pom, and its subdirectories, with signed versions, but that doesn't seem to be happening.On Tue, May 29, 2018 at 9:47 AM, Sam Davis <sam.davis@xxxxxxxxxxx> wrote:Thanks, that seems to have done the trick.SamOn Mon, May 28, 2018 at 11:37 PM, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:Sam Davis wrote:
> I am not able to get the eclipse jarsigner maven plugin to work. I've
> made the this change
> to my pom, but I'm getting the following error:
> ERROR] Plugin
eclipse-jarsigner-plugin:1.1.5 or one ofHi Sam,
> its dependencies could not be resolved: Failure to find
eclipse-jarsigner-plugin:jar:1 .1.5 in
> in the local repository, resolution will not be reattempted until the
> update interval of eclipse.maven.central.mirror has elapsed or updates
> are forced -> [Help 1]
> Could anyone tell me what I'm doing wrong?
the CBI project doesn't publish to Maven Central (I wonder why not?).
You hence need an explicit <pluginReposository> declaration in your POM:
Taken from the Code Recommenders pom.xml:
Hope this helps.
The best code possible
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top