geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Kirby (JIRA)" <>
Subject [jira] Resolved: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed
Date Thu, 15 Jan 2009 23:41:59 GMT


Ted Kirby resolved GERONIMODEVTOOLS-521.

       Resolution: Fixed
    Fix Version/s: 2.1.4
         Assignee: Ted Kirby  (was: Tim McConnell)

Looks good!

The features are signed.  The certificate I think should last longer, and I don't see a signed
date, but the jars show up as signed.  This seems like a good start.  Thanks Delos.

I get this when building on the mac:

INFO] [jar:jar]
[INFO] Building jar: /Users/tedkirby/svn/gdvtls/trunk/features/org.apache.geronimo.v22.feature/target/org.apache.geronimo.v22.feature-2.2.0.jar
[INFO] [jar:sign {execution: default}]
[debug] jarsigner executable=[/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jarsigner]
[debug] Executing: /bin/sh -c "cd /Users/tedkirby/svn/gdvtls/trunk/features/org.apache.geronimo.v22.feature
&& /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jarsigner -verify
[info] jar is unsigned. (signatures missing or not parsable)
[INFO] Warning: The signer certificate will expire within six months.

In eclipse, the jars are signed, and they seem to have the signer artifacts in them.  The
certificate seems to be for 3 months.

Also, I saw no differences between the two patches.

Applied in trunk with rev 734846, and in branches/2.1.4 with rev 734853.

> Sign features so the eclipse update manager recognizes them as signed
> ---------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-521
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3
>            Reporter: Ted Kirby
>            Assignee: Ted Kirby
>             Fix For: 2.2.0, 2.1.4
>         Attachments: 521.patch, 521_updated.patch

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message