Stephen Colebourne

Sounds like it should be generated as `private final transient`. And yes, if already present it should not be generated.

If you could PR the first part, we can keep an RFE open for the second, thanks

Wondering exactly what you have in mind in pseudo code. This only affects mutable beans (immutable ones cannot have circular references).

So, I think the main difficulty here is how to link the child back to the parent object. I don't really want to go down the route of assigning identifiers...

This is good spot, but probably quite tricky to fix given it would require a lot more knowledge about the class structure.

Joda-Beans was intended for a use case where code checked out of a source repo should compile immediately (without any need to run a tool like an annotation processor or...

`MetaBean` is a normal Java interface and can be implemented as such - any way you want.

The normal way to write a primitive value is: @PropertyDefinition private final double number; JSON [does not support](https://stackoverflow.com/questions/1423081/json-left-out-infinity-and-nan-json-status-in-ecmascript) NaN, so the parsing of `null` is intended to provide a backdoor...

This is not a weird idea ;-) Although undoubtedly every user would want their own documentation format. Ideally, I'd like to change Joda-Beans to allow other output files to be...

I suspect that if you add `hierarchy=immutable` it will do what you want: @BeanDefinition public abstract class ReportBaseColumn implements ImmutableBean { ... @BeanDefinition(builderScope = "public", hierarchy = "immutable") public class...