Jar not timestamped?

Solar2D Android
#1

Hi guys;

I keep getting this warning msg in the Corona terminal when I build for Android:

Jan 11 20:55:32.153: jar signed.

Jan 11 20:55:32.154: 

Jan 11 20:55:32.154: Warning: 

Jan 11 20:55:32.156: No -tsa or -tsacert is provided and this jar is not timestamped. Without a timestamp, users may not be able to validate this jar after the signer certificate’s expiration date (2114-11-17) or after any future revocation date.

Jan 11 20:55:32.231: Using Custom Build Id 00000

Jan 11 20:56:39.311: Android build succeeded

I’m using Corona 2515 and Android Studio 1.0.2

I am fairly new to Android development and am not sure ​if this something serious or I need to be worried about it?

I tried searching Google and the Corona forums with the warning message but I haven’t found any answers yet.

Thanks in advance.

#2

Someone else pointed out a similar message.  I’ve asked engineering to see that this is about.

Rob

#3

Ok thanks for looking into it.

Cheers!

#4

Engineering says this isn’t an issue.  Somewhere after Java 7 u51, they added a warning when .jar files are made without a timestamp.  This serves a purpose to make sure the .jar file doesn’t expire even if the certificate does.  However Android converts jar files to dex files, so this is irrelevant.

Rob

#5

Ok great thanks again for all the hard work!

Cheers.

#6

Someone else pointed out a similar message.  I’ve asked engineering to see that this is about.

Rob

#7

Ok thanks for looking into it.

Cheers!

#8

Engineering says this isn’t an issue.  Somewhere after Java 7 u51, they added a warning when .jar files are made without a timestamp.  This serves a purpose to make sure the .jar file doesn’t expire even if the certificate does.  However Android converts jar files to dex files, so this is irrelevant.

Rob

#9

Ok great thanks again for all the hard work!

Cheers.