Quantcast

eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

nsincaglia
I was able to Build eXist-db 3.1.1 after applying the patch that Dmitriy suggested as described here: 

I am using the Oracle Java JDK 1.8.0_65. 

I would like to now digitally sign the jar files. I am doing this by typing the following from the $EXIST_HOME directory:
sudo ./build.sh -f build/scripts/jarsigner.xml
WARNING: JAVA_HOME not found in your environment.
Starting Ant...

java
Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml

jnlp-prepare:

jnlp-keygen:

BUILD FAILED
/mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute should be a integer

Is there another patch related to this? Please advise.

Thanks,

Nick





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Dannes Wessels-3
No,

This should just work.

Are you using Oracles jdk?

Regards

Dannes

--

On 30 Apr 2017, at 20:00, Nick Sincaglia <[hidden email]> wrote:


Is there another patch related to this? Please advise.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Dannes Wessels-3
In reply to this post by nsincaglia
I should read the whole mail. Sorry.

Hmmmm no idea as nothing has changed here...

Regards

Dannes

--
www.exist-db.org

> On 30 Apr 2017, at 20:00, Nick Sincaglia <[hidden email]> wrote:
>
> Is there another patch related to this? Please advise.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Dannes Wessels-3
In reply to this post by nsincaglia
Is it possible to update the jdk?

Regards

Dannes

--
www.exist-db.org

> On 30 Apr 2017, at 20:00, Nick Sincaglia <[hidden email]> wrote:
>
> I am using the Oracle Java JDK 1.8.0_65.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

nsincaglia
Yes, I guess it is possible. I could try that. 

Is there any indication from the reported error that this is a Java error? Is there anything about "Validity attribute should be a integer” which suggests to you that this might be solved by updating the JDK?

I will give it a try and report back.

Nick

On May 1, 2017, at 2:48 AM, Dannes Wessels <[hidden email]> wrote:

Is it possible to update the jdk?

Regards

Dannes

--
www.exist-db.org

On 30 Apr 2017, at 20:00, Nick Sincaglia <[hidden email]> wrote:

I am using the Oracle Java JDK 1.8.0_65.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

nsincaglia
I just upgraded Java. I am still getting the same error. Here is the terminal output.

[ec2-user@ip-10-142-161-212 exist-3.1.1]$ sudo ./build.sh -f build/scripts/jarsigner.xml
WARNING: JAVA_HOME not found in your environment.
Starting Ant...

java
Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml

jnlp-prepare:

jnlp-keygen:

BUILD FAILED
/mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute should be a integer

Total time: 0 seconds

Here is my JAVA_HOME, ant version and Java version settings. 

[ec2-user@ip-10-142-161-212 exist-3.1.1]$ echo $JAVA_HOME 
/usr/java/jdk1.8.0_131

[ec2-user@ip-10-142-161-212 exist-3.1.1]$ ant -version
Apache Ant(TM) version 1.8.3 compiled on February 25 2015

[ec2-user@ip-10-142-161-212 exist-3.1.1]$ java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)



On May 1, 2017, at 10:41 AM, Nick Sincaglia <[hidden email]> wrote:

Yes, I guess it is possible. I could try that. 

Is there any indication from the reported error that this is a Java error? Is there anything about "Validity attribute should be a integer” which suggests to you that this might be solved by updating the JDK?

I will give it a try and report back.

Nick

On May 1, 2017, at 2:48 AM, Dannes Wessels <[hidden email]> wrote:

Is it possible to update the jdk?

Regards

Dannes

--
www.exist-db.org

On 30 Apr 2017, at 20:00, Nick Sincaglia <[hidden email]> wrote:

I am using the Oracle Java JDK 1.8.0_65.





Nick Sincaglia
President/Founder
NueMeta LLC
Digital Media & Technology
Phone: +1-630-303-7035
Skype: nsincaglia





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Dannes Wessels-3
Thnx for trying ......

What Linux distribution is used? Amazon used a modified RHEL no?

What happens if you set JAVA_HOME to the right location?

I hope someone can jump in here as I don't have a Linux box around nor a laptop for the coming week....

Regards

Dannes

--
www.exist-db.org

> On 1 May 2017, at 20:48, Nick Sincaglia <[hidden email]> wrote:
>
> I just upgraded Java. I am still getting the same error. Here is the terminal output.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Adam Retter
In reply to this post by nsincaglia
Hi Nick,

The nightly build system which I created, builds a signed version of
eXist every night.

Once you have an initial clone of the code to a folder called "my-exist":

git clone https://github.com/exist-db/exist.git my-exist


The repeatable build process it follows each night is:

cd my-exist
./build.sh clean
rm -rf extensions/modules/lib
git checkout -- lib/
git fetch origin
git rebase origin/develop
./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
./build.sh installer


Hopefully the above should work for you?

On 30 April 2017 at 14:00, Nick Sincaglia <[hidden email]> wrote:

> I was able to Build eXist-db 3.1.1 after applying the patch that Dmitriy
> suggested as described here:
> http://exist.2174344.n4.nabble.com/eXist-db-3-1-1-BUILD-FAILED-JAVA-HOME-environment-variable-not-set-Please-set-it-and-start-the-build-tp4672140.html
>
> I am using the Oracle Java JDK 1.8.0_65.
>
> I would like to now digitally sign the jar files. I am doing this by typing
> the following from the $EXIST_HOME directory:
> $ sudo ./build.sh -f build/scripts/jarsigner.xml
> WARNING: JAVA_HOME not found in your environment.
> Starting Ant...
>
> java
> Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
>
> jnlp-prepare:
>
> jnlp-keygen:
>
> BUILD FAILED
> /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute
> should be a integer
>
> Is there another patch related to this? Please advise.
>
> Thanks,
>
> Nick
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>



--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

nsincaglia
In reply to this post by Dannes Wessels-3
I am using Amazon Linux AMI release 2017.03

Yes, Amazon Linux is derived from RHEL. I don’t think this issue is related to the operating system or JAVA. The reason I say this is I have eXist-db 3.0 RC1 installed in a sibling folder and I am able to sign those JAR files. Also, as I mentioned in an earlier e-mail, I am able build eXist-db 3.1.1. That would not be possible if JAVA was the issue.

Does anyone know what the error "/mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute should be a integer” hints at? 

Could there be a failure with the jnlp-keygen? Is there something I can check to make sure that is working?

When I try to run the build using verbose setting I get the following:

[ec2-user@ip-10-142-161-212 exist-3.1.1]$ sudo ./build.sh -v -f build/scripts/jarsigner.xml
WARNING: JAVA_HOME not found in your environment.
Starting Ant...

java
Apache Ant(TM) version 1.9.7 compiled on April 9 2016
Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
Detected Java version: 1.8 in: /usr/java/jdk1.8.0_131/jre
Detected OS: Linux
parsing buildfile /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml with URI = file:/mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
Project base dir set to: /mnt/data/exist-3.1.1
parsing buildfile jar:file:/mnt/data/exist-3.1.1/tools/ant/lib/ant-1.9.7.jar!/org/apache/tools/ant/antlib.xml with URI = jar:file:/mnt/data/exist-3.1.1/tools/ant/lib/ant-1.9.7.jar!/org/apache/tools/ant/antlib.xml from a zip file
Property "keystore.file" has not been set
[available] Unable to find ${keystore.file} to set property keystore.present
Build sequence for target(s) `jnlp-all' is [jnlp-prepare, jnlp-keygen, jnlp-sign-exist, jnlp-sign-core, jnlp-all]
Complete build sequence is [jnlp-prepare, jnlp-keygen, jnlp-sign-exist, jnlp-sign-core, jnlp-all, jnlp-unsign-all, jetty-keygen, jnlp-sign-all, jnlp-pack200, jnlp-clean, ]

jnlp-prepare:

jnlp-keygen:
Property "keystore.alias" has not been set
Property "keystore.password" has not been set
Property "keystore.file" has not been set
Property "keystore.validity" has not been set

BUILD FAILED
/mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute should be a integer
at org.apache.tools.ant.taskdefs.GenerateKey.setValidity(GenerateKey.java:305)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.tools.ant.IntrospectionHelper$AttributeSetter.setObject(IntrospectionHelper.java:1506)
at org.apache.tools.ant.IntrospectionHelper.setAttribute(IntrospectionHelper.java:411)
at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:527)
at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:463)
at org.apache.tools.ant.Task.maybeConfigure(Task.java:202)
at org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:200)
at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:164)
at org.apache.tools.ant.Task.perform(Task.java:347)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
at org.apache.tools.ant.Main.runBuild(Main.java:854)
at org.apache.tools.ant.Main.startAnt(Main.java:236)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:285)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:112)

Total time: 0 seconds

On May 1, 2017, at 2:39 PM, Dannes Wessels <[hidden email]> wrote:

Thnx for trying ......

What Linux distribution is used? Amazon used a modified RHEL no?

What happens if you set JAVA_HOME to the right location?

I hope someone can jump in here as I don't have a Linux box around nor a laptop for the coming week....

Regards

Dannes

--
www.exist-db.org

On 1 May 2017, at 20:48, Nick Sincaglia <[hidden email]> wrote:

I just upgraded Java. I am still getting the same error. Here is the terminal output.



Nick Sincaglia
President/Founder
NueMeta LLC
Digital Media & Technology
Phone: +1-630-303-7035
Skype: nsincaglia





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

nsincaglia
In reply to this post by Adam Retter
I just ran:
sudo ./build.sh clean

And then I ran:
sudo ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core

Both were successful.

However, when I run:
sudo ./build.sh -v -f build/scripts/jarsigner.xml

It fails.

Based on what I am seeing from the verbose output, the keystore.file has not been set.

I am assuming that I still need to run the jarsigner.xml script, correct? If so, is there something I can do to address the issue with the keystone?

Nick


> On May 1, 2017, at 2:54 PM, Adam Retter <[hidden email]> wrote:
>
> Hi Nick,
>
> The nightly build system which I created, builds a signed version of
> eXist every night.
>
> Once you have an initial clone of the code to a folder called "my-exist":
>
> git clone https://github.com/exist-db/exist.git my-exist
>
>
> The repeatable build process it follows each night is:
>
> cd my-exist
> ./build.sh clean
> rm -rf extensions/modules/lib
> git checkout -- lib/
> git fetch origin
> git rebase origin/develop
> ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
> ./build.sh installer
>
>
> Hopefully the above should work for you?
>
> On 30 April 2017 at 14:00, Nick Sincaglia <[hidden email]> wrote:
>> I was able to Build eXist-db 3.1.1 after applying the patch that Dmitriy
>> suggested as described here:
>> http://exist.2174344.n4.nabble.com/eXist-db-3-1-1-BUILD-FAILED-JAVA-HOME-environment-variable-not-set-Please-set-it-and-start-the-build-tp4672140.html
>>
>> I am using the Oracle Java JDK 1.8.0_65.
>>
>> I would like to now digitally sign the jar files. I am doing this by typing
>> the following from the $EXIST_HOME directory:
>> $ sudo ./build.sh -f build/scripts/jarsigner.xml
>> WARNING: JAVA_HOME not found in your environment.
>> Starting Ant...
>>
>> java
>> Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
>>
>> jnlp-prepare:
>>
>> jnlp-keygen:
>>
>> BUILD FAILED
>> /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute
>> should be a integer
>>
>> Is there another patch related to this? Please advise.
>>
>> Thanks,
>>
>> Nick
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> [hidden email]
> irc://irc.freenode.net/existdb



Nick Sincaglia
President/Founder
NueMeta LLC
Digital Media & Technology
Phone: +1-630-303-7035
[hidden email]
http://www.nuemeta.com
Skype: nsincaglia





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Adam Retter
Nick,

You don't need to run sudo ./build.sh -v -f
build/scripts/jarsigner.xml at all. My instructions covered signing
the jars.

On 1 May 2017 at 16:25, Nick Sincaglia <[hidden email]> wrote:

> I just ran:
> sudo ./build.sh clean
>
> And then I ran:
> sudo ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
>
> Both were successful.
>
> However, when I run:
> sudo ./build.sh -v -f build/scripts/jarsigner.xml
>
> It fails.
>
> Based on what I am seeing from the verbose output, the keystore.file has not been set.
>
> I am assuming that I still need to run the jarsigner.xml script, correct? If so, is there something I can do to address the issue with the keystone?
>
> Nick
>
>
>> On May 1, 2017, at 2:54 PM, Adam Retter <[hidden email]> wrote:
>>
>> Hi Nick,
>>
>> The nightly build system which I created, builds a signed version of
>> eXist every night.
>>
>> Once you have an initial clone of the code to a folder called "my-exist":
>>
>> git clone https://github.com/exist-db/exist.git my-exist
>>
>>
>> The repeatable build process it follows each night is:
>>
>> cd my-exist
>> ./build.sh clean
>> rm -rf extensions/modules/lib
>> git checkout -- lib/
>> git fetch origin
>> git rebase origin/develop
>> ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
>> ./build.sh installer
>>
>>
>> Hopefully the above should work for you?
>>
>> On 30 April 2017 at 14:00, Nick Sincaglia <[hidden email]> wrote:
>>> I was able to Build eXist-db 3.1.1 after applying the patch that Dmitriy
>>> suggested as described here:
>>> http://exist.2174344.n4.nabble.com/eXist-db-3-1-1-BUILD-FAILED-JAVA-HOME-environment-variable-not-set-Please-set-it-and-start-the-build-tp4672140.html
>>>
>>> I am using the Oracle Java JDK 1.8.0_65.
>>>
>>> I would like to now digitally sign the jar files. I am doing this by typing
>>> the following from the $EXIST_HOME directory:
>>> $ sudo ./build.sh -f build/scripts/jarsigner.xml
>>> WARNING: JAVA_HOME not found in your environment.
>>> Starting Ant...
>>>
>>> java
>>> Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
>>>
>>> jnlp-prepare:
>>>
>>> jnlp-keygen:
>>>
>>> BUILD FAILED
>>> /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute
>>> should be a integer
>>>
>>> Is there another patch related to this? Please advise.
>>>
>>> Thanks,
>>>
>>> Nick
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Exist-open mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>
>
> Nick Sincaglia
> President/Founder
> NueMeta LLC
> Digital Media & Technology
> Phone: +1-630-303-7035
> [hidden email]
> http://www.nuemeta.com
> Skype: nsincaglia
>
>
>
>



--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

nsincaglia
Thanks Adam.

I suspected that might be the answer but I wanted to make sure because I saw in the output when I ran sudo ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core the following message:

  [signjar] Signing JAR: /mnt/data/exist-3.1.1/start.jar to /mnt/data/exist-3.1.1/start.jar as exist
  [signjar] jar signed.
  [signjar]
  [signjar] Warning:
  [signjar] 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 (2291-02-14) or after any future revocation date.
     [echo] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
     [echo] !! Please run '$EXIST_HOME/build.[bat|sh] -f build\scripts\jarsigner.xml'
     [echo] !! once manually to use a default keystore to sign the core jars or put !!
     [echo] !! your own certificate in $EXIST_HOME/key.store and sign for enabling webstart !!
     [echo] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

jnlp-prepare:

jnlp-keygen:

jnlp-sign-exist:
  [signjar] Signing JAR: /mnt/data/exist-3.1.1/exist-optional.jar to /mnt/data/exist-3.1.1/exist-optional.jar as exist
  [signjar] jar signed.
  [signjar]
  [signjar] Warning:
  [signjar] 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 (2291-02-14) or after any future revocation date.

Best,

Nick

> On May 1, 2017, at 4:16 PM, Adam Retter <[hidden email]> wrote:
>
> Nick,
>
> You don't need to run sudo ./build.sh -v -f
> build/scripts/jarsigner.xml at all. My instructions covered signing
> the jars.
>
> On 1 May 2017 at 16:25, Nick Sincaglia <[hidden email]> wrote:
>> I just ran:
>> sudo ./build.sh clean
>>
>> And then I ran:
>> sudo ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
>>
>> Both were successful.
>>
>> However, when I run:
>> sudo ./build.sh -v -f build/scripts/jarsigner.xml
>>
>> It fails.
>>
>> Based on what I am seeing from the verbose output, the keystore.file has not been set.
>>
>> I am assuming that I still need to run the jarsigner.xml script, correct? If so, is there something I can do to address the issue with the keystone?
>>
>> Nick
>>
>>
>>> On May 1, 2017, at 2:54 PM, Adam Retter <[hidden email]> wrote:
>>>
>>> Hi Nick,
>>>
>>> The nightly build system which I created, builds a signed version of
>>> eXist every night.
>>>
>>> Once you have an initial clone of the code to a folder called "my-exist":
>>>
>>> git clone https://github.com/exist-db/exist.git my-exist
>>>
>>>
>>> The repeatable build process it follows each night is:
>>>
>>> cd my-exist
>>> ./build.sh clean
>>> rm -rf extensions/modules/lib
>>> git checkout -- lib/
>>> git fetch origin
>>> git rebase origin/develop
>>> ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
>>> ./build.sh installer
>>>
>>>
>>> Hopefully the above should work for you?
>>>
>>> On 30 April 2017 at 14:00, Nick Sincaglia <[hidden email]> wrote:
>>>> I was able to Build eXist-db 3.1.1 after applying the patch that Dmitriy
>>>> suggested as described here:
>>>> http://exist.2174344.n4.nabble.com/eXist-db-3-1-1-BUILD-FAILED-JAVA-HOME-environment-variable-not-set-Please-set-it-and-start-the-build-tp4672140.html
>>>>
>>>> I am using the Oracle Java JDK 1.8.0_65.
>>>>
>>>> I would like to now digitally sign the jar files. I am doing this by typing
>>>> the following from the $EXIST_HOME directory:
>>>> $ sudo ./build.sh -f build/scripts/jarsigner.xml
>>>> WARNING: JAVA_HOME not found in your environment.
>>>> Starting Ant...
>>>>
>>>> java
>>>> Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
>>>>
>>>> jnlp-prepare:
>>>>
>>>> jnlp-keygen:
>>>>
>>>> BUILD FAILED
>>>> /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute
>>>> should be a integer
>>>>
>>>> Is there another patch related to this? Please advise.
>>>>
>>>> Thanks,
>>>>
>>>> Nick
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Exist-open mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>
>>>
>>>
>>>
>>> --
>>> Adam Retter
>>>
>>> eXist Developer
>>> { United Kingdom }
>>> [hidden email]
>>> irc://irc.freenode.net/existdb
>>
>>
>>
>> Nick Sincaglia
>> President/Founder
>> NueMeta LLC
>> Digital Media & Technology
>> Phone: +1-630-303-7035
>> [hidden email]
>> http://www.nuemeta.com
>> Skype: nsincaglia
>>
>>
>>
>>
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> [hidden email]
> irc://irc.freenode.net/existdb



Nick Sincaglia
President/Founder
NueMeta LLC
Digital Media & Technology
Phone: +1-630-303-7035
[hidden email]
http://www.nuemeta.com
Skype: nsincaglia





------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.1.1 Digitally Signing Jars Build Failed: Validity attribute should be a integer

Adam Retter
I think that the date 2291-02-14 is probably far enough in the future
that you probably need not worry ;-)

On 1 May 2017 at 17:49, Nick Sincaglia <[hidden email]> wrote:

> Thanks Adam.
>
> I suspected that might be the answer but I wanted to make sure because I saw in the output when I ran sudo ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core the following message:
>
>   [signjar] Signing JAR: /mnt/data/exist-3.1.1/start.jar to /mnt/data/exist-3.1.1/start.jar as exist
>   [signjar] jar signed.
>   [signjar]
>   [signjar] Warning:
>   [signjar] 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 (2291-02-14) or after any future revocation date.
>      [echo] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>      [echo] !! Please run '$EXIST_HOME/build.[bat|sh] -f build\scripts\jarsigner.xml'
>      [echo] !! once manually to use a default keystore to sign the core jars or put !!
>      [echo] !! your own certificate in $EXIST_HOME/key.store and sign for enabling webstart !!
>      [echo] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
> jnlp-prepare:
>
> jnlp-keygen:
>
> jnlp-sign-exist:
>   [signjar] Signing JAR: /mnt/data/exist-3.1.1/exist-optional.jar to /mnt/data/exist-3.1.1/exist-optional.jar as exist
>   [signjar] jar signed.
>   [signjar]
>   [signjar] Warning:
>   [signjar] 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 (2291-02-14) or after any future revocation date.
>
> Best,
>
> Nick
>
>> On May 1, 2017, at 4:16 PM, Adam Retter <[hidden email]> wrote:
>>
>> Nick,
>>
>> You don't need to run sudo ./build.sh -v -f
>> build/scripts/jarsigner.xml at all. My instructions covered signing
>> the jars.
>>
>> On 1 May 2017 at 16:25, Nick Sincaglia <[hidden email]> wrote:
>>> I just ran:
>>> sudo ./build.sh clean
>>>
>>> And then I ran:
>>> sudo ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
>>>
>>> Both were successful.
>>>
>>> However, when I run:
>>> sudo ./build.sh -v -f build/scripts/jarsigner.xml
>>>
>>> It fails.
>>>
>>> Based on what I am seeing from the verbose output, the keystore.file has not been set.
>>>
>>> I am assuming that I still need to run the jarsigner.xml script, correct? If so, is there something I can do to address the issue with the keystone?
>>>
>>> Nick
>>>
>>>
>>>> On May 1, 2017, at 2:54 PM, Adam Retter <[hidden email]> wrote:
>>>>
>>>> Hi Nick,
>>>>
>>>> The nightly build system which I created, builds a signed version of
>>>> eXist every night.
>>>>
>>>> Once you have an initial clone of the code to a folder called "my-exist":
>>>>
>>>> git clone https://github.com/exist-db/exist.git my-exist
>>>>
>>>>
>>>> The repeatable build process it follows each night is:
>>>>
>>>> cd my-exist
>>>> ./build.sh clean
>>>> rm -rf extensions/modules/lib
>>>> git checkout -- lib/
>>>> git fetch origin
>>>> git rebase origin/develop
>>>> ./build.sh jnlp-unsign-all all jnlp-sign-exist jnlp-sign-core
>>>> ./build.sh installer
>>>>
>>>>
>>>> Hopefully the above should work for you?
>>>>
>>>> On 30 April 2017 at 14:00, Nick Sincaglia <[hidden email]> wrote:
>>>>> I was able to Build eXist-db 3.1.1 after applying the patch that Dmitriy
>>>>> suggested as described here:
>>>>> http://exist.2174344.n4.nabble.com/eXist-db-3-1-1-BUILD-FAILED-JAVA-HOME-environment-variable-not-set-Please-set-it-and-start-the-build-tp4672140.html
>>>>>
>>>>> I am using the Oracle Java JDK 1.8.0_65.
>>>>>
>>>>> I would like to now digitally sign the jar files. I am doing this by typing
>>>>> the following from the $EXIST_HOME directory:
>>>>> $ sudo ./build.sh -f build/scripts/jarsigner.xml
>>>>> WARNING: JAVA_HOME not found in your environment.
>>>>> Starting Ant...
>>>>>
>>>>> java
>>>>> Buildfile: /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml
>>>>>
>>>>> jnlp-prepare:
>>>>>
>>>>> jnlp-keygen:
>>>>>
>>>>> BUILD FAILED
>>>>> /mnt/data/exist-3.1.1/build/scripts/jarsigner.xml:69: Validity attribute
>>>>> should be a integer
>>>>>
>>>>> Is there another patch related to this? Please advise.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Nick
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>> _______________________________________________
>>>>> Exist-open mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Adam Retter
>>>>
>>>> eXist Developer
>>>> { United Kingdom }
>>>> [hidden email]
>>>> irc://irc.freenode.net/existdb
>>>
>>>
>>>
>>> Nick Sincaglia
>>> President/Founder
>>> NueMeta LLC
>>> Digital Media & Technology
>>> Phone: +1-630-303-7035
>>> [hidden email]
>>> http://www.nuemeta.com
>>> Skype: nsincaglia
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>
>
> Nick Sincaglia
> President/Founder
> NueMeta LLC
> Digital Media & Technology
> Phone: +1-630-303-7035
> [hidden email]
> http://www.nuemeta.com
> Skype: nsincaglia
>
>
>
>



--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Loading...