OK, I will report it. Previously I didn't have to use 4 slashes, only 2. [image: i2cat] Julio C. Barrera Juez Office phone: +34 93 357 99 27 Distributed Applications and Networks Area (DANA) i2CAT Foundation, Barcelona, Spain http://dana.i2cat.net
On 14 November 2013 10:25, Achim Nierbeck <[email protected]> wrote: > Hi, > > you might report and issue, though I'm not sure it is really a Karaf > issue. > It's been quite a long time since I tried this, but afairc this is typical > for a Windows Environment to have 4 backslashes in parameters, cause you'll > need 2 backslashes for an escaped backslash and since it's a string > interpreted you'll need 2 backslashes resulting in 4 in your scripts.path > variable :/ > > regards, Achim > > > 2013/11/14 Julio Carlos Barrera Juez <[email protected]> > >> Hi! >> >> I was using Karaf in a quite old fashioned version 2.2.2 and I have >> recently updated to version 2.2.11. With Linux I have no problems, but with >> Windows I'm experiencing weird problems using session variables in Karaf >> CLI. >> >> Defining a session variable containing a path like: >> >> scripts.path=C:\\data >> >> I get with Karaf 2.2.2: >> >> C:\data >> >> And with Karaf 2.2.11: >> >> C:data >> >> >> It seems like the previous escaped paths are now lost. Is there a way to >> use paths inside session variables in Windows? >> >> I have just realized that in Karaf 2.2.11 it is necessary to double >> escape each slash: >> >> scripts.path=C:\\\\data >> >> C:\data >> >> Is this behaviour a bug? Should I report it? >> >> [image: i2cat] >> Julio C. Barrera Juez >> Office phone: +34 93 357 99 27 >> Distributed Applications and Networks Area (DANA) >> i2CAT Foundation, Barcelona, Spain >> http://dana.i2cat.net >> > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> > Commiter & Project Lead > blog <http://notizblog.nierbeck.de/> >
