pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roger Lee Whitcomb (Jira)" <j...@apache.org>
Subject [jira] [Commented] (PIVOT-1048) Starting kitchen-sink.jnlp fails with Open Web Start
Date Sun, 26 Apr 2020 03:25:00 GMT

    [ https://issues.apache.org/jira/browse/PIVOT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092463#comment-17092463

Roger Lee Whitcomb commented on PIVOT-1048:

So, the "build.xml" is supposed to add the "<security><all-permissions/></security>"
element to the jnlp file IFF the binaries are signed.  So, in my local builds where I don't
sign them, this piece is missing.  AND in the "trunk" code there appears to be a problem because
the formatting of the generated jnlp file is all screwed up as well (i.e., not the same as
the 2.0.5 branch).

So, [~gunnar_g] can you verify if the .jar files you downloaded were signed or not?  They
are supposed to be, and the jnlp files should have be generated with the appropriate permissions
element.  So, we screwed up somehow in updating the website with the 2.0.5 release.  I will
try to track down what happened, but if you could verify that the .jar files are actually
signed that would help.

> Starting kitchen-sink.jnlp fails with Open Web Start
> ----------------------------------------------------
>                 Key: PIVOT-1048
>                 URL: https://issues.apache.org/jira/browse/PIVOT-1048
>             Project: Pivot
>          Issue Type: Bug
>          Components: demos
>    Affects Versions: 2.0.5
>            Reporter: Ronald Sterckx
>            Assignee: Roger Lee Whitcomb
>            Priority: Major
>         Attachments: stderr.log, stdout.log
> Downloaded openWebStart (https://openwebstart.com) to launch the kitchen-sink.jnlp file
with. Started it with
> {code}/opt/OpenWebStart/javaws -jnlp /tmp/mozilla_app0/kitchen-sink.jnlp > /tmp/stdout.log
2>/tmp/stderr.log {code}
> It downloads the latest JRE, in this case 11.0.6.
> It fails with following message (see stdout.log):
> Caused by: java.security.AccessControlException: access denied ("java.util.PropertyPermission"
"java.runtime.version" "read")

This message was sent by Atlassian Jira

View raw message