Quantcast

eXist-db 3.0 RC1 build from source (develop), error with jarsigner

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

eXist-db 3.0 RC1 build from source (develop), error with jarsigner

nsincaglia
I just tried building eXist-db from source using the develop code. I am assuming this is eXist 3.0.RC1. I was able to successfully run the build script but when I tried to sign the jar files I got the following error message.

> sudo ./build.sh -f build/scripts/jarsigner.xml
Starting Ant...

/usr/lib/jvm/java-8-oracle/jre/bin/java
Buildfile: /mnt/data/exist-3.0-RC/build/scripts/jarsigner.xml

jnlp-prepare:

jnlp-keygen:

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

I looked at the jarsigner.xml file and compared it to another developer version of eXist-db I created about 6 months ago and there were several differences, particularly with several of the classpath references. For example:

OLD CODE:
<taskdef name="unsignjar"
            classname="nl.ow.dilemma.ant.jar.UnsignJarTask"
            classpath="${asocat-exist.jar}”/>

NEW CODE:
<taskdef name="unsignjar"
            classname="nl.ow.dilemma.ant.jar.UnsignJarTask">
            <classpath>
                <pathelement location="${asocat-exist.jar}"/>
            </classpath>
        </taskdef>

OLD CODE:
<taskdef name="repack"
            classname="nl.ow.dilemma.ant.jar.RepackJarTask"
            classpath="${asocat-exist.jar}”/>

NEW CODE:
<taskdef name="repack"
            classname="nl.ow.dilemma.ant.jar.RepackJarTask">
            <classpath>
                <pathelement location="${asocat-exist.jar}"/>
            </classpath>
        </taskdef>

OLD CODE:
<taskdef name="pack"
            classname="nl.ow.dilemma.ant.jar.Pack200Task"
            classpath="${asocat-exist.jar}”/>

NEW CODE:
<taskdef name="pack"
            classname="nl.ow.dilemma.ant.jar.Pack200Task">
            <classpath>
                <pathelement location="${asocat-exist.jar}"/>
            </classpath>
        </taskdef>

OLD CODE:
    <!-- Set sign properties -->
    <property name="keystore.alias" value="exist"/>
    <property name="keystore.password" value="secret"/>
    <property name="keystore.file" value="key.store"/>
    <property name="keystore.validity" value="100000"/>

I ended up copying over the old jarsigner.xml file and tried using that to sign the jars and it worked fine.

I thought I would post this in case others ran into the issue.

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.0 RC1 build from source (develop), error with jarsigner

nsincaglia
I think I was mistaken in thinking I was pulling down the eXist-db 3.0 RC1 from github. I see now that there is a location on github specifically for that code:
https://github.com/eXist-db/exist/releases/tag/eXist-3.0.RC1

So, I guess I downloaded the 3.0 RC2 code which I saw someone mention is not recommended to be used right now.

I think I got confused when I read the following statement on github:
"NOTE: In the above example, we switched the current (checked-out) branch from develop to master. We use the GitFlow for eXist process:

develop is the current (and stable) work-in-progress (the next release)
master is the latest release The choice of which to use is up to you."

The (and stable) made me think it was eXist-db 3.0 RC1 but now I am under the impression it is 3.0 RC2.

Nick
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: eXist-db 3.0 RC1 build from source (develop), error with jarsigner

Emmanuelle Morlock
In reply to this post by nsincaglia
Hi Nick,

I had the same problem.
Your message helped me to modify the exist/build/scripts/jarsigner.xml
(l. 68 I substituted "100000" to ${keystore.validity} in the validity
attribute. Then the build process of "./build.sh -f
build/scripts/jarsigner.xml" was succesful.

Thanks !

Best,

Emmanuelle


Le 23/01/2017 à 02:17, Nick Sincaglia a écrit :

> I just tried building eXist-db from source using the develop code. I am assuming this is eXist 3.0.RC1. I was able to successfully run the build script but when I tried to sign the jar files I got the following error message.
>
>> sudo ./build.sh -f build/scripts/jarsigner.xml
> Starting Ant...
>
> /usr/lib/jvm/java-8-oracle/jre/bin/java
> Buildfile: /mnt/data/exist-3.0-RC/build/scripts/jarsigner.xml
>
> jnlp-prepare:
>
> jnlp-keygen:
>
> BUILD FAILED
> /mnt/data/exist-3.0-RC/build/scripts/jarsigner.xml:69: Validity attribute should be a integer
>
> I looked at the jarsigner.xml file and compared it to another developer version of eXist-db I created about 6 months ago and there were several differences, particularly with several of the classpath references. For example:
>
> OLD CODE:
> <taskdef name="unsignjar"
>              classname="nl.ow.dilemma.ant.jar.UnsignJarTask"
>              classpath="${asocat-exist.jar}”/>
>
> NEW CODE:
> <taskdef name="unsignjar"
>              classname="nl.ow.dilemma.ant.jar.UnsignJarTask">
>              <classpath>
>                  <pathelement location="${asocat-exist.jar}"/>
>              </classpath>
>          </taskdef>
>
> OLD CODE:
> <taskdef name="repack"
>              classname="nl.ow.dilemma.ant.jar.RepackJarTask"
>              classpath="${asocat-exist.jar}”/>
>
> NEW CODE:
> <taskdef name="repack"
>              classname="nl.ow.dilemma.ant.jar.RepackJarTask">
>              <classpath>
>                  <pathelement location="${asocat-exist.jar}"/>
>              </classpath>
>          </taskdef>
>
> OLD CODE:
> <taskdef name="pack"
>              classname="nl.ow.dilemma.ant.jar.Pack200Task"
>              classpath="${asocat-exist.jar}”/>
>
> NEW CODE:
> <taskdef name="pack"
>              classname="nl.ow.dilemma.ant.jar.Pack200Task">
>              <classpath>
>                  <pathelement location="${asocat-exist.jar}"/>
>              </classpath>
>          </taskdef>
>
> OLD CODE:
>      <!-- Set sign properties -->
>      <property name="keystore.alias" value="exist"/>
>      <property name="keystore.password" value="secret"/>
>      <property name="keystore.file" value="key.store"/>
>      <property name="keystore.validity" value="100000"/>
>
> I ended up copying over the old jarsigner.xml file and tried using that to sign the jars and it worked fine.
>
> I thought I would post this in case others ran into the issue.
>
> 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


--
Emmanuelle Morlock
IE CNRS - Humanités numériques & TEI
UMR 5189 HISoMA
http://www.hisoma.mom.fr

06 85 84 69 16
@emma_morlock

----------------------------------------------
Membre du comité de coordination d'Humanistica,
    association francophone des Humanités numériques
    <http://www.humanisti.ca>

Page HiSoMA : http://www.hisoma.mom.fr/annuaire/morlock-emmanuelle
Page HAL : https://cv.archives-ouvertes.fr/emmanuelle-morlock

------------------------------------------------------------------------------
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...