Cedric Beust

Ah. That's pretty much what jitpack does, though... ## Cédric On Mon, Mar 21, 2016 at 9:46 PM, aneophyte [email protected] wrote: > That would be nice too. But I'm also...

@zoltu `bintray` is already supported, so making it more generic to support any arbitrary artifactory should be trivial. Right now, just maintaining a wiki page with the Kobalt plug-ins I...

Isn't an agent just an extra flag for the JVM? If yes then it's already supported in Kobalt with `jvmArgs()`.

Agreed it would be nice to have this, will investigate. ## Cédric On Tue, Jun 14, 2016 at 2:29 AM, Dmitry Zhuravlev [email protected] wrote: > When working on a large...

I have a basic websocket server working. The server now starts a WebSocket server (the current HTTP one is still running so this should not break anything). Take a look...

This is not currently supported. If you depend on a project, this project's dependencies will be automatically added to your current project. Going to tag this as a feature request.

Mmmh, this seems to be more of a `git` issue than Kobalt? Does your repo have a `HEAD`?

Is this what other build tools do? It seems that this would completely defeat incremental compilation.

Took a quick look, this build uses the [`frontend-maven-plugin`](https://github.com/eirslett/frontend-maven-plugin) which lets you install and manage various Javascript package managers and build tools (npm, grunt, etc...). Not very hard to implement,...

You can already specify compiler flags: ``` javaCompiler { args("-source", "1.7", "-target", "1.7") } ``` Isn't this sufficient?