Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6EDA10529 for ; Thu, 14 Nov 2013 11:19:27 +0000 (UTC) Received: (qmail 23755 invoked by uid 500); 14 Nov 2013 11:19:27 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 23706 invoked by uid 500); 14 Nov 2013 11:19:24 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 23697 invoked by uid 99); 14 Nov 2013 11:19:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Nov 2013 11:19:21 +0000 Date: Thu, 14 Nov 2013 11:19:21 +0000 (UTC) From: "Julio Carlos Barrera (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KARAF-2588) double escaped path slashes in session variables using shell MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julio Carlos Barrera updated KARAF-2588: ---------------------------------------- Description: In previous versions, like Karaf 2.2.2 ZIP release I could use paths as session variables using Karaf shell: {noformat}scripts.path=C:\\data C:\data{noformat} But now, using Karaf 2.2.11 I need to double escape slashes to obtain the same behaviour: {noformat}scripts.path=C:\\data C:data{noformat} vs {noformat}scripts.path=C:\\\\data C:\data{noformat} I don't know in which version between 2.2.2 and 2.2.11 it has changed. Why did this behaviour change? I have a lot of Karaf scripts that I need to edit adding these double-escaped paths. was: In previous versions, like Karaf 2.2.2 ZIP release I could use paths as session variables using Karaf shell: {noformat}scripts.path=C:\\data C:\data{noformat} But now, using Karaf 2.2.11 I need to double escape slashes to obtain the same behaviour: {noformat}scripts.path=C:\\data C:data{noformat} vs {noformat}scripts.path=C:\\\\data C:\data{noformat} I don't know in which version between 2.2.2 and 2.2.11 it has changed. Why did this behaviour change? I have a lot of Karaf scripts that I need to edit adding this double-escaped paths. > double escaped path slashes in session variables using shell > ------------------------------------------------------------ > > Key: KARAF-2588 > URL: https://issues.apache.org/jira/browse/KARAF-2588 > Project: Karaf > Issue Type: Bug > Components: karaf-shell > Affects Versions: 2.2.11 > Environment: Windows 7 64 bits > Karaf 2.2.11 ZIP release > Windows cmd.exe > Reporter: Julio Carlos Barrera > Priority: Minor > Labels: karaf, karaf-shell, session-variable, windows > > In previous versions, like Karaf 2.2.2 ZIP release I could use paths as session variables using Karaf shell: > {noformat}scripts.path=C:\\data > C:\data{noformat} > But now, using Karaf 2.2.11 I need to double escape slashes to obtain the same behaviour: > {noformat}scripts.path=C:\\data > C:data{noformat} > vs > {noformat}scripts.path=C:\\\\data > C:\data{noformat} > I don't know in which version between 2.2.2 and 2.2.11 it has changed. Why did this behaviour change? I have a lot of Karaf scripts that I need to edit adding these double-escaped paths. -- This message was sent by Atlassian JIRA (v6.1#6144)