#hoplon

exit

\q

hey all, trying to get boot-sassc working again. Can anyone help me diagnose some issues?

Also unable to push a new version to clojars for some reason :(

From the stack trace when `boot build-jar push-release` fails:

org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: https://clojars.org/repo/mathias/boot-sassc/0.1..., ReasonPhrase:Forbidden.

Huh, seems to have worked at some point because the jar is up there now

you can get that kind of error if the version already exists

in clojars

Next question is: Did printing out output from a shell command change?

I'm not seeing any output, and I suspect that sassc is failing inside

hm, i don't think so

I should at least see it output the debug messages around the command run..

but I don't see that at all

or https://github.com/mathias/boot-sassc/blob/mast...

oddly users are saying it works for them, even though boot-sassc no longer works in my demo project for me haha

what if you throw an exception there?

just to make sure it's getting to that part of the code

when all else fails you can printf via exception messages usually

haha

I'll try

Yes, it gets to there.

util/dbug and util/info not seeming to output, and no output from sassc command ,though

Ah here's a possible reason

There's no files in the filset

fileset*

Most of the changes that'd been submitted (and I've merged when they seemed to work) around the fileset, I haven't kept up with the changes

aha

Is there another task that tracks non-clojure fileset changes that I could compare to?

fileset-diff is a good way

i see you alraedy have it

not sure it is working though

if the task isn't watching, it's just being run on a file, would this still work?

the initial diff is the whole thing, so it should work

hmm

and I see we're using the sass-file in there, it's not getting dropped

since last-fileset is initally nil

but debug-by-exception is saying that we don't have any files by the time it gets to actually running

hm

Oh wow.

I'm bad at this :P

I'd updated the instructions on boot-sassc to say to use :resource-paths

But the example project didn't use that yet

that was the one thing that made it not work

hahaha

ok

Thanks :)

in other news, that library is updated with some new features that got PRed and works again

at least for me :-)

great news! :thumbsup:

I'm glad that people are able to use boot-sassc and it works for them. On the other hand, I rarely have time to work on it when it doesn't work

so here's hoping it doesn't break for a good long while!

:D

things should be pretty stable now

so i feel good about it

I don't think it was ever boot changes that broke it

it was that it was hard to set up and get the right version for

now the namespacing is consistent

we can use jruby in the future to pin the exact version of sass, too

for awhile there we had src under mathias/boot-sassc but I had released it as just boot-sassc

so that was confusing to people