Skip to content

Run compile in separate thread with empty classloader#17

Open
DeLaGuardo wants to merge 4 commits into
luchiniatwork:masterfrom
DeLaGuardo:fix/#16
Open

Run compile in separate thread with empty classloader#17
DeLaGuardo wants to merge 4 commits into
luchiniatwork:masterfrom
DeLaGuardo:fix/#16

Conversation

@DeLaGuardo

Copy link
Copy Markdown

This commit should fix #16

Dependencies from cambada itself are loaded into classloader and if some project
is relying on one of that dependency (eg. clojure.data.xml) compiled class will
not be presented in compiled target directory.

Implementation for that is taken from
badigeon. Another build tool for clojure
cli.

Dependencies from cambada itself are loaded into classloader and if some project
is relying on one of that dependency (eg. clojure.data.xml) compiled class will
not be presented in compiled target directory.

Implementation for that is taken from
[badigeon](https://github.com/EwenG/badigeon). Another build tool for clojure
cli.
@luchiniatwork

Copy link
Copy Markdown
Owner

@DeLaGuardo what would be the best way to test this? I'm thinking ahead in terms of unit testing as well

@aterribili

Copy link
Copy Markdown

I'm having the same problem here. Will this be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Classes from clojure.data.xml can not be found in produced uberjar

3 participants