<@U06A03HV1> <@U0N6C2Q9F> I’m finally feeding `fil...
# development
a
@witty-crayon-22786 @fast-nail-55400 I’m finally feeding
file:/
uris into coursier, and it doesn’t seem to like relative URLs. Is there a way for me to reify the full path of a file for me to pass onto a coursier command line?
w
oy.
a
Issue is
Exception in thread "main" java.lang.IllegalArgumentException: URI is not hierarchical
, which is getting thrown by the Java
File
API. SO I ’m not sure I can do a whole lot about that.
w
would need to adjust the wrapper script that we use to define an env var for
cwd
maybe …?
a
Updating the wrapper script would do, I guess.
And URLs from a
Snapshot
that I’ve merged in will always be relative to that, right?
w
correct
a
OK, that’s easy enough then
HACKS 😄
w
seriously. i’m having a similar day
a
Do we have any level of control over what characters will be in the working directory, @witty-crayon-22786?
(just trying to construct a
sed
command, and the usual delimiter of
/
is not very well suited to subbing in a file path full of
/
. Hoping that
@
or
&
or
%
might be OK
w
hm, not fully understanding. but you can use different characters to `sed`:
Copy code
sed -e 's|something|something_else|g'
a
that’s what I’m doing
I was checking if I can safely assume that
@
or
|
etc won’t be in a filename
w
but also, if you actually embed bash interpolation syntax, you might be able to “eval” it after defining the variable …?
I was checking if I can safely assume that 
@
 or 
|
 etc won’t be in a filename
mm. um, yea. i think
|
is safest to assume
a
cool
f
for prior art, the Go runner script also has to switch certain paths to be absolute
a
what file should I be looking in?
(I’m not unhappy with my current approach, but if yours works OK, I should probably copy that)
the Go script doesn’t deal with a placeholder though
you could have your placeholder be environment variable and rely on the wrapper to make that env var available
a
oh ok, yup, I’m basically doing all that