[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fop-dev
Subject:    [jira] [Commented] (FOP-2708) FOP 2.2 binary release's bundled script to run FOP not set as executab
From:       "simon steiner (JIRA)" <jira () apache ! org>
Date:       2017-05-31 11:38:04
Message-ID: JIRA.13075679.1496084770000.330278.1496230684150 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/FOP-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031019#comment-16031019 \
] 

simon steiner commented on FOP-2708:
------------------------------------

http://svn.apache.org/viewvc?view=revision&revision=1797015

> FOP 2.2 binary release's bundled script to run FOP not set as executable
> ------------------------------------------------------------------------
> 
> Key: FOP-2708
> URL: https://issues.apache.org/jira/browse/FOP-2708
> Project: FOP
> Issue Type: Bug
> Components: unqualified
> Affects Versions: 2.2
> Environment: macOS, likely any Unix-like operating system
> Reporter: JCount
> Priority: Minor
> 
> The binary distribution of FOP 2.2 contains the shell script *fop* for running FOP, \
> within the *fop/* subdirectory. In previous versions the mode of this script was \
> *755*, however, in the 2.2 release the mode is set as *644*.  This means that \
> individual users, as well as package managers such as Homebrew, need to change the \
> mode of the script as an additional step during setup. I suspect that this was not \
> intentional, but rather a side effect of changing the build process for the binary \
> distribution. If this is the case, it likely can only be resolved in the next \
> release.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[prev in list] [next in list] [prev in thread] [next in thread]