can i somehow get rid of these warnings when I start my dev server?

Sep 30, 2018 11:47:29 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.8.Final
Sep 30, 2018 11:47:29 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.8.Final
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (file:/Users/jacek/.m2/repository/org/jboss/xnio/xnio-nio/3.3.8.Final/xnio-nio-3.3.8.Final.jar) to constructor sun.nio.ch.KQueueSelectorProvider()
WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

not sure if there is an undertow release with a fixed dependency yet

doesn't look like it

not sure if I can just bump xnio without breaking undertow

https://issues.jboss.org/browse/XNIO-322

:thinking_face:

try adding [org.jboss.xnio/xnio-nio "3.6.5.Final"] + [org.jboss.xnio/xnio-api "3.6.5.Final"] to your deps

maybe the warning goes away and everything runs?

I don't get warnings anymore on windows

seems to be a mac issue

@jacek.schae btw are any of your "students" on windows?

I know of one but are there more?

wondering how the percentages win/mac are

just added the deps

Sep 30, 2018 12:29:24 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.6.5.Final
Sep 30, 2018 12:29:24 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.6.5.Final
Sep 30, 2018 12:29:24 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.0.Beta2
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.threads.ThreadLocalResetter$1 (file:/Users/jacek/.m2/repository/org/jboss/threads/jboss-threads/2.3.0.Beta2/jboss-threads-2.3.0.Beta2.jar) to field java.lang.Thread.threadLocals
WARNING: Please consider reporting this to the maintainers of org.jboss.threads.ThreadLocalResetter$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

getting close to having something usable for the ui. wondering if its worth investigating publishing it on windows app store

hehe nice

i don't really have the view into use env

i don't know if someone has win, mac, or linux

ah thought you may log it on purchase or so

apparatently you can :exclusions [org.jboss.threads/jboss-threads]

https://issues.jboss.org/browse/UNDERTOW-1355

thanks for help anyways

the exclusions didn't help either

i saw the video of the ui, look forward to the finalised version

starting build a standalone electron version and its coming along nicely

really liking where this is going

great to hear! 👍 If you would need any feedback feel free to ping me.

I have an app that I’m using bootstrapped CLJS. It works fine in development but when I run a release build, it breaks. There are some errors when I load the bundle:

/assets/bootstrap/js/cljs.core$macros.js:1 Uncaught ReferenceError: goog is not defined
/assets/bootstrap/js/cljs.tools.reader.reader-types$macros.js:1 Uncaught ReferenceError: goog is not defined
/assets/bootstrap/js/cljs.reader$macros.js:1 Uncaught ReferenceError: goog is not defined
/assets/bootstrap/js/cljs.env.macros$macros.js:1 Uncaught ReferenceError: goog is not defined
/assets/bootstrap/js/cljs.analyzer.macros$macros.js:1 Uncaught ReferenceError: goog is not defined
/assets/bootstrap/js/cljs.compiler.macros$macros.js:1 Uncaught ReferenceError: goog is not defined

code is here: https://github.com/Lokeh/lilac.town/blob/master/src/lilactown/client/visual_spec.cljs

shadow-cljs.edn is here: https://github.com/Lokeh/lilac.town/blob/master/shadow-cljs.edn

@lilactown if you use the self-host stuff you cannot compile with :advanced, only :simple

so add :optimizations :simple to the :compiler-options

I'm trying to adapt the first hoplon example to shadow-cljs but its giving me a "CompilerException: clojure.lang.ExceptionInfo: Call to clojure.core/ns did not conform to spec:" error. My ns declaration looks okay to me (but I'm still somewhat new to clojure). Can someone look at it and tell me what might be wrong? Also any other advise in this endeavour would be helpful. [email protected]:vigilancetech-com/address-book.git

thats a clojure error. you are probably trying to load a cljs into clj?

here's my command line: shadow-cljs run build/hop watch app

there is no code here https://github.com/vigilancetech-com/address-book

oops! hmm. I wonder where that push went 😄

ok, check it again

no idea whats going on in that repo sorry

I don't know boot or hoplon

the build.boot is there but I'm not using it. I just added the shadow-cljs files and tried renaming some stuff to make it work. In a nutshell this is what hoplon does: https://github.com/hoplon/hoplon/wiki/How-is-a-hl-file-different%3F

there is not much code in there and I still can't tell whats happening

the hoplon function just slightly finesses the *.hl file to generate the cljs file with those included namespaces. It just has to run before the cljs compile function does so I set up the build.clj file as per this: https://github.com/thheller/shadow-cljs/wiki/Custom-builds

https://github.com/vigilancetech-com/address-book/blob/master/src/build.clj this doesnt do anything

and if you are new to clojure creating a custom build is gonna be tough as it requires pretty in depth knowledge about how CLJS and shadow-cljs + CLJ work

its probably also not for what you are trying to do

I've been having constant trouble getting boot to work with cider. Getting a decent repl doesn't seem to be too much of a priority with the hoplon/boot community, but as I'm working with fairly complex existing app (rather than a new one) I need to be able to get my hands right on the guts of it and understand what makes it "tick"

so it was either this or figwheel under boot, but several of the things you're doing with shadow just seems cleaner

can you get hoplon to just spit out normal .cljs files?

then you don't need to hook into anything and let shadow-cljs just process those cljs files

by "new" I'm meaning I'm probably 6 months in after not having done much programming for a couple decades (with a fair bit of lisp before that)

yeah, I think I could if I could figure out how to either tell boot where to put them or shadow where to find them I guess. I just wanted to start off with baby steps w/shadow to try and fully understand it, like how to get it to run the hoplon function first.

yeah feeding custom inputs to a build is next level advanced stuff

don't do it basically

so that function "hop" I created under the ns won't get called with a "run?"

this shadow-cljs run build/hop watch app will call (build/hop "watch" "app")

hmmm... okay, that's somewhat enlightening

after trying to use npm packages for the 45th time with :npm-deps, I've forced myself to give shadow-cljs a try. I have to say, I'm very much pleased, and I think I've been missing out 🙂