Fork me on GitHub
#immutant
<
2016-03-15
>
symbit14:03:23

@tcrawley: Great, thank you! For some reason my hoplon resources (index.html) isn't being served, otherwise the server is fine. Investigating, if this is a packaging issue. I don't see any index.html in the entire WAR or the nested JAR where is would likely be.

tcrawley14:03:45

@symbit: is index.html in a dir that is listed in :resource-paths? I think it has to be to end up in the uberjar

symbit14:03:55

Yes, in the source the index.cljs.hl file is in a subdir in the resource-path.

symbit14:03:29

I don't see any of the artifacts from the compiling index.cljs.hl in the project.jar (nor the outer war file.) Adding (show :fileset true) to the uberwar task chain..

symbit15:03:42

The hoplon artifacts aren't in the WAR file created.

symbit15:03:11

@tcrawley: I removed the target and /.boot/ directories. I renamed the (page "somethingveryunique.html"). Expand the WAR and project.jar. There is no sign of somethingveryunique. They are however in the temp directories in the /.boot/cache/tmp/base_dir/subdir1/subdir2/ns1/ns2/random_dir_name1/random_dir_name2/

symbit15:03:01

trying again with

(target)
added back in..

symbit16:03:13

actually aren't you calling the target task in 0.6.0-snapshot?

tcrawley16:03:31

@symbit: sorry, I've been busy with other stuff this morning. I can try and take a look this afternoon - I suspect the issue here is the boot-immutant plugin is running uber itself instead of honoring your pipeline

tcrawley16:03:59

it calls target after calling (comp (uber) (jar)) to get access to the uberjar

tcrawley16:03:58

would it be possible for you to create a sample app that demonstrates the problem? that would make it easier for me to figure out what's going on

symbit16:03:13

It sounds like you'd have to pick up the fileset/pipeline instead of creating a private one?

symbit16:03:28

Yes, I'll put that together..