Clojurians Log v2

hello... 🙂 🙂 I have an immutant question .. if i have an application made with clojure 1.5 ... and we want to update to 1.8 (to just be current) ... can i leave immutant at immutant-1.0.1-slim or should that be updated too?

@clojuregeek hmm, I don't think that would be a problem, but that's a pretty old Immutant release.

@tcrawley ok.. i'm trying to figure out what this app needs out of immutant ..

I know that 1.0.1 won't work with Java 8, I'm checking the release notes to see if there's anything post 1.0.1 that hints at fixes for Clojure 1.7 or 1.8

I don't see anything immediately that gives me concern

ok good, we are using older java than 1.8 🙂

Let us know how it goes, and if you decide to update Immutant (preferably to 2.x), we'd be happy to help.

ok thanks @tcrawley

question, i see used in the code clojurewerkz.quartzite.scheduler in a namespace, is that the scheduler that is in immutant ?

no, that wouldn't be our scheduler - we don't use quartzite, and talk to Quartz directly instead

you can, however, mix quartzite and Immutant scheduling, sharing the scheduler between the two

i dont find the namespace immutant anywhere in this project ... however the lein-immutant plugin is used in the profile for the user that deploys the application

that's weird - is it just depending on lein-immutant, or is it calling tasks through it as well?

I would think you would at least see immutant.web. Are any immutant dependencies listed in the top-level deps?

no

I suspect that lein-immutant dep may be dead code, the app probably isn't using immutant at all

i dont see anything immutant in the project.clj or anywhere in the project

oh, it was just in ~/.lein/profiles.clj? I think you're in the clear then

ok

thanks 🙂

happy to help!

Hey folks, looks like I'm running into https://issues.jboss.org/browse/UNDERTOW-966 - any plans to cut a new release with undertow bumped to 1.3.27.Final soon?

For now I can override the version in my project, of course 🙂

@dergutemoritz thanks for the heads up, we weren't aware of that issue - would you mind filing an issue at https://issues.jboss.org/projects/IMMUTANT/?

@tcrawley Can do! Happens very consistently with streaming HTTP / SSE

sounds like a good reason to cut a release :)

Here ya go: https://issues.jboss.org/browse/IMMUTANT-627

thanks!

Welcome!