| Re: [ease-dev] Updating Script Repository |
Thanks, could you also open a bug for the 2nd one? We should try to deal with unknown keywords as good as we can, but in any case we should not show errors when we cannot parse such keywords. Thanks Christian From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Utsav Oza Hi Christian, I have opened a bug report for the first issue (Bug 512130 - [Script Explorer] Path/File names display %20 instead of spaces). Regarding second issue, unfortunately, the scripts had some bad custom headers that didn't have any ease keywords, and it turns out that those headers was causing the dialog to pop every time the location had those scripts. Thanks, Utsav Oza On Mon, Feb 13, 2017 at 1:19 PM, <Christian.Pontesegger@xxxxxxxxxxxx> wrote: Hi, you may have encountered 2 different issues: · first the issue with %20 in the path/file names · second the invalid topic that gets posted. The topic quite likely comes from some content in one of your script headers. Could you post them to see what is treated as a keyword and causes the problem? Please open bug reports for both topics Best regards Christian From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Utsav Oza Hello, When changing script repository location (to any filesystem location having more than one sub-directory level) in the Preference page (and when set to 'recursive=true'), I encounter a problem which says 'invalid topic: org/eclipse/ease/scripts/keywords' (See attached screenshots). Additionally the directory names containing spaces are incorrectly named, I suppose spaces may be encoded using URI class that requires replacing spaces with %20. Is there a bug filed that addresses this issue ? Thanks, Utsav Oza
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature