Is there any documentation on using boot for a cljs library, rather than an app? I've got one that I'm moving out of my cljs application into a standalone library namespace and I want to be able to install it locally as well as on clojars.

I'm just wondering if the standard boot pom jar install pipeline for clj libraries is different for cljs.

pkobrien: you make jars with cljs in them the same as clojure

the standard thing you said should work

does it not doit?

I'm just getting started on it.

do I need to use adzerk-oss/boot-cljs

@meow: no because the cljs files go in the jar uncompiled as resources (compilation is done by the consuming application)

@alandipert: Aha! That makes sense.

Do you know of any example boot file for this situation?

Or do I just ignore the fact that my code is .cljs files?

basically just ignore it

on the boot page on github it says:

This sets up the build environment. Then we constructed a pipeline of tasks:

The pom task with options to set the project ID and version, (by default only compiled artifacts end up in the fileset),

only compiled artifact end up in what fileset? And what exactly does that mean?

that's talking about the "roles" of files in the fileset

it shouldn't say "compiled", really

there are two "roles", input and output

files in the fileset can have one or both of these roles

files with the input role are files that can be input to build type tasks, like compilers for instance

files with the output role are files that can be packaged by packaging type tasks, like jar for instance

input files are files that can be input for a transformation

output files are files that can be packaged in the final artifact (i.e. end up in the jar or the target dir)

the way you assign roles is by adding the files to the fileset via :source-paths, :resource-paths, and :asset-paths

each of these corresponds to a permutation of input and output roles

see: https://github.com/boot-clj/boot/wiki/Filesets#fileset-components

so if you add the .cljs files to :source-paths they won't end up in the jar

you want to add them to :resource-paths

then they will have the output role

@micha: gotcha, thanks.

I got problems.

https://github.com/decomplect/ion/blob/master/boot.properties

https://github.com/decomplect/ion/blob/master/build.boot

https://github.com/decomplect/ion/blob/master/src/ion/poly/core.cljs

First problem: I can run boot poly pom jar install from the command-line without error.

but boot build-poly gets me clojure.lang.ExceptionInfo: java.lang.NullPointerException

Second problem: it doesn't seem to be installing quite right.

I'm sure I'm making simple errors with my setup.

Bueller would find my mistakes right away ... if only he were here.

oh i see

pkobrien: poly isn't really a task

tasks need to return middleware

so when you put it in the pipeline and try to compose (poly) with other things you get a NPE

oops

because (poly) doesn't return middleware

right

poly should just be a defn that I call

you can put task-options! and set-env! at the top level

or yeah as a function you call for side effects

why not just have the set-env and task-options as top level expressions?

because I'm going to have other libraries in the ion namespace

I thought I'd use one boot file to control them all

couldn't his poly task end with identity

johnmendonca: totally, good idea

clojure.core/identity is like the identity middleware

so you can return that

the "profile pattern": https://github.com/boot-clj/boot/wiki/Boot-for-Leiningen-Users#profiles-middleware

I like that

so that's fixed: https://github.com/decomplect/ion/blob/master/build.boot

But it's still not installing correctly

what are the symptoms?

This seems to be the meat of it:

org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for ion.poly.core:ion.p
oly.core:jar:LATEST
    result: #object[org.sonatype.aether.resolution.ArtifactDescriptorResult 0x865dd6 "ion.poly.core:ion.poly.core:jar:LA
TEST -> []"]
   org.sonatype.aether.resolution.VersionResolutionException: Failed to resolve version for ion.poly.core:ion.poly.core:
jar:LATEST: Could not find metadata ion.poly.core:ion.poly.core/maven-metadata.xml in local (C:\Users\Patrick\.m2\reposi
tory)
    result: #object[org.sonatype.aether.resolution.VersionResult 0x3d687a "null @ null"]
      org.sonatype.aether.transfer.MetadataNotFoundException: Could not find metadata ion.poly.core:ion.poly.core/maven-
metadata.xml in local (C:\Users\Patrick\.m2\repository)
    metadata: #object[org.sonatype.aether.util.metadata.DefaultMetadata 0x1f116b8 "ion.poly.core:ion.poly.core/maven-met
adata.xml"]

when I look in my local .m2/repository/ion/poly it doesn't look right

this happens when you try to use it, not when you install it, right?

what does the pom look like?

there is a 0.1.0 folder, a core folder, and a maven-metadata-local.xml file

can you paste that?

yes, that was the error when I tried to use the app

looks like either the pom file or the metadata is bad

sometimes maven gets into a fuxx0red state

pom file: https://www.refheap.com/105142

and you need to rm -rf the directory for your project in the .m2

and reinstall

the pom looks fine to me

i'd try rm -rf ~/.m2/repository/ion/poly or something like that

I've been doing that. Same problem.

Shouldn't the maven-metadata-local.xml file be inside the 0.1.0 folder?

nevermind

what does that guy look like?

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>cljsjs</groupId>
  <artifactId>jquery</artifactId>
  <versioning>
    <release>1.8.2-1</release>
    <versions>
      <version>1.8.2-0</version>
      <version>9.9.9</version>
      <version>1.8.2-1</version>
    </versions>
    <lastUpdated>20150120004003</lastUpdated>
  </versioning>
</metadata>

that's kind of what it should look like

<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>ion</groupId>
  <artifactId>poly</artifactId>
  <versioning>
    <release>0.1.0</release>
    <versions>
      <version>0.1.0</version>
    </versions>
    <lastUpdated>20150702223409</lastUpdated>
  </versioning>
</metadata>

looks legit to me

ok so what does the build.boot in the consumer look like?

that's the only place the problem could be i think

pkobrien: ^^

I had an error on the consuming side, getting closer

Now I get

clojure.lang.ExceptionInfo: No such namespace: ion.poly.core, could not locate ion/poly/core.cljs, ion/poly/core.cljc, o
r Closure namespace "ion.poly.core" at line 1 /C:/Users/Patrick/.boot/cache/tmp/Users/Patrick/code/ing/informing/4eg/7o2
s6s/app/core.cljs

https://github.com/pkobrien/ing/tree/master/informing

does the jar actually contain the namespace?

so in my build.boot there I set a dependency on [ion/poly "0.1.0"]

this line looks odd to me: https://github.com/decomplect/ion/blob/master/build.boot#L9

do you have src/ion/poly/ion/poly/core.cljs in your project?

no

src/ion/poly/core.cljs

so you want :resource-paths #{"src"} i think

"src" will be the root of the tree that will be added to the fileset

the jar .m2\repository\ion\poly\0.1.0\poly-0.1.0.jar\ contains core.cljs and META-INF

right

but it should contain ion/poly/core.cljs and the META-INF stuff

ah!

okay, but what if later I add src/ion/phil/core.cljs

and I want poly and phil to be separate

if you do :resource-paths #{"src"} then the src directory will be the root of the classpath, basically

well in that case you make a different root

like maybe "src1" and "src2"

well, I was trying to avoid that

well you can use fancier things i guess

but the real question i guess is: are the projects going to be separate artifacts in maven?

if so it usually makes sense to have separate git repos

because then you can relate releases to git commits in a straightforward way

and things like that

I'm trying to reduce the overhead of multiple git repos

so maybe roll them into one maven artifact

why not have both things in the same jar?

you can have jars with both clj and cljs stuff in them

my idea was to have one git repo for several libraries

ok so one workaround that isn't too crazy i guess would be to use the sift task

keeping the repo structure simple and nonredundant

i've tried this and it never ended up being simpler

I knew I was swimming against the current but figured I'd try it and see what it was like.

especailly if you take pull requests

or if you need to make changelogs and stuff

so you should try the sift task

have all the things in "src", and sift out the ones you don't wnat to include in the jar

boot sift --help

it does a lot of things there

too many probably

but i can imagine like (sift :include #{ #"\.cljs$" }) being part of your pipeline

or something

is there a way to prepend ion/poly/ to what goes in the jar instead?

sure

the sift task, again!

so I can leave my specific stuff for selecting and then just prepend the namespace

(sift :move { #"\.cljs$" "ion/poly/$1" }) for instance

gtg, will look at whatever you suggest

it isn't too late for me to make separate repos for all of this if my way is just too crazy

look at the sift task, it is the swiss army knife of fileset manipulations

bbl, thanks for all your help!

np! good luck