Clojurians Log v2

Has anyone tried 2.8.0-SNAPSHOT yet? I haven’t created a GitHub release and I’m not sure if that’s required

The AppVeyor build seems to be failing because I haven’t created one

Creating a release for mutable SNAPSHOT feels a bit weird but I’m also not sure which boot.jar I’m supposed to upload? /cc @alandipert

FYI I updated the Github notifications to not post comments on existing issues anymore.

Would be curious if anyone has thoughts on https://github.com/boot-clj/boot/issues/542

(It’s about passing arguments to tasks as-is without any clojure.tools.cli interference)

martinklepsch were you able to do the snapshot release? also i dropped a commen on 542

i like @alandipert’s idea about a new syntax to indicate that args should be passed to a function with that name in build.boot's namespace

seems potentially very useful

especially if symbols can be ns-qualified

@alandipert I published the appropriate jars to Clojars but didn’t create a release on Github. It seems that this is an issue for Windows CI at least but it hasn’t prevented me from using 2.8.0-SNAPSHOT

If anyone can confirm that they are able to run the SNAPSHOT that’d be helpful.

@martinklepsch nope

I modified boot.properties however it fails to download the snapshot

I assume I’ll need to build it myself

@flyboarder does it fail at trying to download a jar from github?

yep

Downloading ...
Exception in thread "main" java.io.FileNotFoundException: 
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
	at java.net.URL.openStream(URL.java:1045)
	at Boot.download(Boot.java:176)
	at Boot.install(Boot.java:227)
	at Boot.main(Boot.java:241)

Ok, I think I know what the issue is then

will post here once fixed, should be in a few hours

Tagging snapshot releases on github is a bit weird — what do people think about using qualifiers like -alpha1?

@martinklepsch its running but I got this:

Downloading ...
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See  for further details.

yeah I’m also getting those SLF4J warnings, will need to look into where those are coming from

Really not happy with those -SNAPSHOT things, might go forward with -alpha1 -alpha2 and so on unless there are objections

this will also simplify https://github.com/boot-clj/boot-bin/issues/6#issuecomment-353688737

that could get awkward quickly

@flyboarder could you elaborate?

if there are accidental issues pushed, I see us going from alpha1 to alpha11 quickly, but thats IMO

personally I dont cut boot releases so i would say whatever is easier for those who do

I see what you mean, also this could become an issue with people running boot -u since -alpha` releases would technically be stable releases as far as I understand