boot-clj / boot-clj/boot

`pom` dependencies lost when using `jar`

Open
#509 8 comments 0 reactions 0 assignees View on GitHub
Bug
Dominant language
Clojure
Stars
1.7k
Forks
178
PR merge metrics
No merged PRs in 30d

Description

Say I have a task like:

``` clojure
(comp
(pom :project 'com.example/foo
:version "1.0"
;; ...
:dependencies '[[com.example/bar "0.1"]])
(jar)
(target))
```

The `pom.xml` created by `pom` includes all the right values, including ``. This is confirmed by looking at `target/META-INF/maven/com.example/foo/pom.xml`. However, the `pom.xml` included in the JAR has all the right values _except_ ``, which lists the default (the dependencies in the Boot environment).

The `jar` task is clearly picking up on the pom as the resulting file in `foo-1.0.jar`; without a valid POM it would simply be `project.jar`. Why are the custom dependencies lost?

Thanks for the amazing build tool!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.