Fork me on GitHub
#boot
<
2018-07-24
>
richiardiandrea00:07:14

Sorry folks, will need to find some time to fix that

richiardiandrea00:07:52

Or revert the change, I don't know how many folks use the pom parent feature

seancorfield00:07:30

Would it suffice to expand (sequential? type) to (and (sequential? type) (= 1 (count type))) since that would un-break all the [str] common use versions out there, while letting the [sym ver path] style destructuring thru?

richiardiandrea01:07:42

Yep I wanted to actually fix that exactly that way ;)

richiardiandrea01:07:31

There are also test files there if I remember correctly

seancorfield01:07:05

I look forward to Boot 2.8.2 🙂

zalky22:07:58

Hi all, tried upgrading boot today to 2.8.1 to go along with the new s3-private-wagon (1.3.2), and I can't seem to figure out how to get the credentials to load. I keep getting Secret key cannot be null errors when attempting to connect to the private s3 repo. The credential provider is finding the s3 passphrase, and I can see the passphrase in the repository entry when I do (:repositories (get-env)) from the repl. I'm using a pretty minimal test build. Has anyone managed to get 2.8.1 working with s3-private-wagon?

seancorfield23:07:09

@zalky Wasn't there a breaking change to how SSL/TLS is handled in 2.8.x?