Google Code Exporter

``` The gradle convention seems to be that "output" paths are relative to the build dir and inputs are relative to the project dir, so that is what I have...

``` I've seen lots of plugins which pass a "file" instead of a string path for inputs. That seems more robust to me (since it will fail in a clear...

``` From the gradle api docs, the Project.file method: Resolves a file path relative to the project directory of this project. so they are relative, just relative to the project...

``` Yes, correct. But the resolution is in the build.gradle, not inside the plugin. This means that the user has complete control over what they pass. I don't think this...

``` Humm, I suppose I could use File instead of String, set the defaults as they are now and overload the setter so that a string does the resolution relative...

Original comment by `[email protected]` on 10 Oct 2012 at 12:20

``` type->enhancement ``` Original comment by `[email protected]` on 20 Jun 2011 at 3:39 - Added labels: **Type-Enhancement** - Removed labels: **Type-Defect**

``` I think the performance impact of this change could be huge. It would be really really nice to do it ;) ``` Original comment by `marianopeck` on 2 Sep...

``` SRP: "Metastates describe the data encoding. You must be able to resolve the metastate the object to be read. The metastate is data in a predictable (yet extendable) format...

``` FLClassShapeEncoderDecoder FLClassShapeWriterReader FLClassShapeSerializer The same as above but FLClassInformationXXX I don't like the "variables" beacuse it is misleading. We write all the information in order to handle class reshape....