Jon Pretty

The `fury universe projects diff` command should, for each difference, give each difference a unique identifier. We could then provide a `fury universe projects merge` command which imports a change...

My recent changes to introduce the `Dependency` type resulted in `java/compiler` always appearing in the graph, unlinked, even though it never needs compiling. It should be hidden.

duplicate JAR entry error is not caught

5

When constructing the JAR file, there may still be duplicate entries, and the exception is not caught or handled in any way.

This area of the code is a huge mess. We seem to construct about four different dependency graphs along the way, and I don't trust its performance. The whole thing...

filewatcher uses too many threads

2

When watching Fury, waiting for changes, it creates 30 new threads in order to watch the various source directories. It feels like this ought to be a single thread.

It's annoying to have to write something like this, just to make part of a string use a particular theme: ``` def msg(path: Path) = UserMsg { theme => msg"$path/".string(theme)+theme.italic("unknown")...

introduce more module add parameters

6

It should be possible to add a module defining the following, all in the `add` command, - sources - dependencies - binaries - parameters - environment variables - resources as...

list all binaries in a project or layer, not just current module

1

We might need something more comprehensive than this, but for now, the command should be, ``` fury binary list --all ```

allow dependencies on local JARs

1

We should be able to point to a file, rather than Maven coordinates to specify a binary. It shouldn't be possible to publish a layer containing a local JAR, unless...