Yannick Loiseau
Yannick Loiseau
I'm sure IoT folks like @k33g would be pleased :smile:
Maybe two artefacts: the current full version `golo-VERSION.jar`, and `golo-runtime-VERSION.jar` containing only the classes needed at runtime (AFAICT `org.eclipse.golo.runtime.*` and `gololang.*`). I suppose some tweaks to the `build.gradle` would be...
linked to #400 (cc @Artpej)
Arrgg, yes, the `EvaluationEnvironment` depends on the `GoloClassLoader`... Ok, so `org.eclipse.golo.runtime.*`, `org.eclipse.golo.compiler.*` and `gololang.*` then :smile: In any way, we don't need the `org.eclipse.golo.cli.*`, and thus no `jcommander` nor `txtmark`...
Indeed... I opened this issue while trying to create a naive gradle task to create a uberjar: ```gradle task uberjar(type: Jar, dependsOn: [':compileJava',':compileGolo']) { manifest { attributes 'Main-Class': golo.mainModule }...
Couldn't we close this issue, since we moved to gradle?
Indeed, when no space is present, it's parsed as the `-1` constant.
On an other hand, this fails: ``` golo let a = 42 let b = -a ``` with ``` [error] Encountered unexpected `-` ``` and `+` is not allowed as...
Maybe a property file would be more convenient than JSON (it's Java ecosystem after all).
@danielpetisme What I propose is just to wrap methods returning `void` to return the object itself. Fallback is of no use here, since the method exists, and thus doesn't trigger...