@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.
@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
Yes, in the source the index.cljs.hl file is in a subdir in the resource-path.
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..
The hoplon artifacts aren't in the WAR file created.
@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/
trying again with
(target)
added back in..actually aren't you calling the target task in 0.6.0-snapshot?
@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
it calls target after calling (comp (uber) (jar))
to get access to the uberjar
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
It sounds like you'd have to pick up the fileset/pipeline instead of creating a private one?
Yes, I'll put that together..
thanks!