but it'll barf if I refer to something outside the repo?

no... but that's not really a good idea for reproducibility.

oh

I achieve reproducibility through another mechanism

I do have to list the jars individually though? I can't just say "grab all the jars in this folder"?

no

(context is that the IntelliJ SDK distributes a big folder of jars in a zip file)

they don't put them in any maven/ivy repository anywhere, as far as I know

do you know if anyone uses pants to build intellij plugins and if they do anything nice there?

or of other lightweight solutions where I basically want to depend on a remote versioned zip file full o' jars

the pants intellij plugin is built with pants. could look at what it does

hmm, is anyone using the

scalajs

backend? i’m getting

Exception message: TaskRegistrar 'scala-js-link' with action ScalaJSLink_resolve_scala_js_link depends on scala_js_ir from task ScalaJSZincCompile_resolve_scala_js_compile which is ordered after it in the 'resolve' goal:
	[0] 'ivy' IvyResolve_resolve_ivy
	[1] 'scala-js-compile' ScalaJSZincCompile_resolve_scala_js_compile
	[2] 'scala-js-link' ScalaJSLink_resolve_scala_js_link
	[3] 'scala-js-compile' ScalaJSZincCompile_resolve_scala_js_compile
	[4] 'scala-js-link' ScalaJSLink_resolve_scala_js_link

ordering matters in the

backends

list:

...hm. actually, that looks like it is installed twice...?

oh, doh, i had

+['pants.contrib.scalajs',]

but it’s already listed in

backend_packages

by default

thanks 🙂

yea, i think if you're loading it as a

plugin

, it's added to

backends

by default

working now!

@bright-apartment-76721 : it might not be to insanely difficult to define a target/task to load a bunch of loose jars from a directory and expose them all on the classpath for the target

@witty-crayon-22786 my concern is around packaging if I do that. I can probably get a pants run to pass in the right thing

loose_jars(.., directory='x/y/z')

, and then the task would expose the

compile_classpath

product and add them for the target.

`run`/`binary`/`bundle` would be fine. but

publish

would not.

afaik

ah okay

so you're saying loose_jars is something I'd write, but wouldn't be hard

yea

...hm, alternatively. you could write it as a macro, and then create a jar_library to cover all of them. similar effect though.

macro? don't think I've come across that in a pants context yet

yea, they're not really documented, because their design will change more in the future.