Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 465068 - Use Java 8 in jar signing web service
Summary: Use Java 8 in jar signing web service
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Servers (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 463510
Blocks:
  Show dependency tree
 
Reported: 2015-04-20 23:01 EDT by David Williams CLA
Modified: 2015-04-21 11:32 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2015-04-20 23:01:06 EDT 
Once the issues are worked out with bug 463510 (and related bugs) and the "batch processor" moves up to Java 8 ... for "jar (pack2000) processing" and "jar signing", then we should remember to move the webservice up to Java 8 as well. (In bug 464947 comment 17 it was mentioned it is currently at Java 7). 

I do not think there is much difference in "how they sign" or anything ... both at SHA256 checksums, I believe, but we should be sure to keep all ways of signing (and processing) jars in sync with each other for more consistency, and we should keep them "up to date" with latest Java (not necessarily "first release" of latest Java -- let others find the initial bugs :) -- but, up to date enough that what ever we use does not go out of service.
Comment 1 Eclipse Webmaster CLA 2015-04-21 11:32:05 EDT 
OK, I've updated the jarsigner directory to be the Java 8 install.

-M.