Fork me on GitHub
#boot
<
2017-06-20
>
richiardiandrea00:06:26

Uhm I have been bitten by the gpg bug:

Adding uberjar entries...
Writing rest-resources-viz-0.1.0.jar...
Signing rest-resources-viz-0.1.0.jar...
Could not sign /tmp/pom4228085068282441784.xml
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available

richiardiandrea00:06:33

what am I missing?

richiardiandrea00:06:56

obviously the key 😄 But I am passing :gpg-user-id to push

richiardiandrea00:06:15

Ok solved with BOOT_GPG_COMMAND=gpg2 boot deploy-extractor --gpg-user-id ...

dm310:06:19

how do I set a javaagent with boot?

dm310:06:01

I guess through BOOT_JVM_OPTIONS - means I need to hardcode the path 😞

dm310:06:55

hmm, can’t get it to work

dm310:06:41

that’s because the classes the agent needs are only loaded in the pod

donyorm12:06:55

So I noticed a profile in a a luminus project I'm converting to boot has an :injections clause in the dev profile. Whats the equivalent in boot?

donyorm12:06:05

(luminus works in lein)

donyorm12:06:38

oh nevermind, I figured it out.

donyorm20:06:27

So with the luminus project I'm having some issues again. Under lein it runs fine, but under boot I get a ClassNotFoundException: org.jboss.vfs.VirtualFileFilter. Both projects have the exact same dependencies. Why would boot faile to load JBoss properly?

donyorm20:06:16

seems to be something with webjars, webjars loads jboss, but boot isn't seeming to load it

juhoteperi20:06:53

Huh, what Webjars package loads jboss?

richiardiandrea21:06:41

is there a way to deploy a source and javadoc artifact with boot ?

donyorm21:06:23

@juhoteperi I assumed that was [org.webjars/webjars-locator-jboss-vfs "0.1.0"] did.

hiredman21:06:55

I would look at your dependencies, I forget how to do it with boot, maybe boot -C, I suspect you have two different dependencies on jboss-vfs of different versions, and some how for whatever reason boot is resolving that conflict in favor of the version without the VirtualFileFilter class, and lein is doing the reverse

richiardiandrea22:06:33

so yeah there is not way to produce javadoc and source so this means that it is not possible to deploy to maven central at the moment

richiardiandrea22:06:11

I guess I can produce it manually

donyorm22:06:45

@hiredman according to boot show -d and lein deps :tree they're using the exact same version.

hiredman22:06:22

more than one or just the one? did deps :tree warning about anything? are you using any plugins?

donyorm22:06:47

@hiredman I only saw one with that signature. There are plugins in the project, but I've commented them out of both lein and boot and I still have the same error

domkm23:06:36

Is there any way to access the properties that Boot reads in from boot.properties? I don't see them in system properties.

donyorm23:06:21

try something like (get (boot.App/config) "BOOT_VERSION" "2.7.1")

domkm23:06:05

@donyorm That worked. Thanks!