Clojurians Log v2

Snapshots need manual deletion in .m2 last time I checked and therefore no good. I like the idea of using version modifiers like that, and probably -u should change accordingly.

There is a nice package called boot-semver that handles version files pretty well 😉

@martinklepsch can we build and package boot with boot?

ah ah

I was think about that

@flyboarder at the moment it is built with Makefiles

but with your new shiny boot-exec in theory we could use boot to build

“bootception”

There’s a closed PR somewhere that built boot with boot

Seems that Maven gives some well known qualifiers special treatment so that boot -u issue might be a non issue https://stackoverflow.com/a/31482463/175920

I’m assuming Aether/Pomegranate use the same stuff as foundation? Also kind of curious what tools.deps does in this regard

Ah but I think the boot -u issue is still unclear. Depends on whether releases with -beta or similar are taken into account when specifying “RELEASE”

RELEASE has some problems, which is why it is rarely used

Don't remember properly, maybe it was that Maven has to check the repository every time if dependency uses RELEASE version

SNAPSHOT versions are cached for some duration, not sure about RELEASE

SLJ4J warning is from pomegranate/maven-resolver

Will be very hard to fix that unfortunately, we can't automatically add nop/simple logger as that would break projects using real loggers

Maybe we'll need code to check project deps and only add logger if there isn't one

Or maybe slf4-api has some method to check if logger is available... and then we can inject logger... if we can do that before it prints the warning, it would probably be most robust solution

https://github.com/qos-ch/slf4j/blob/master/slf4j-api/src/main/java/org/slf4j/LoggerFactory.java#L149

If we can manage to run code before Maven-resolver classes are loaded, we can use java.util.ServiceLoader.load to check for SLF4JServiceProvider and if none is found, add nop/simple logger to classpath

@juhoteperi Could you open an issue for that?

@juhoteperi do you know if there’s a re-run button somewhere in AppVeyor?

"Re-build commit" under the build view

hm, I don’t think I have that option, maybe only the owner can do it? @juhoteperi

Hmm, I think AppVeyor permissions should depend on Github because there doesn't seem to be any way to configure them

Or hmm, it is under by account so it is possible

@martinklepsch Check now, I found option where I can give permissions based on Github organizations

hm @juhoteperi it should be on a page like this right? https://ci.appveyor.com/project/Deraen/boot/build/288

Yeah

Check again, I tuned the permissions a bit

And have you logged into appveyor with your github account?

or connected gh to your account

yes

still not there 😄

This is what I see, page ends with the blue log output box.

😕

well, I’ll just force push without edits then. Strange though.

hey @shimbaco 👋