Project

General

Profile

Defect #789

No jars are signed when changing the codebase

Added by Nicola Gervasi about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Start date:
02/19/2014
Due date:
% Done:

0%

Estimated time:
Browser (if web client):

Description

I've added one domain to the codebase list and run the tool again (headless mode) to update all jars signature but it looks like it doesn't notice the difference and so it doesn't resign the jars.

History

#1

Updated by Patrick Talbot about 10 years ago

  • Status changed from New to In Progress

Well, technically the signature hasn't changed, so it doesn't find anything that needs resigning.
I will add an item 'all' to the selection property so that it resign them all regardless.

#2

Updated by Patrick Talbot about 10 years ago

  • Status changed from In Progress to Closed

'all' selection was added to v1.1.1

Also available in: Atom PDF