Add javadoc to the setter methods or both of them so you *actually* document your component options what they are intended for.
On Wed, Dec 9, 2015 at 2:01 PM, Roman Vottner <r...@gmx.at> wrote: > Hi there, > > we use Camel 2.16.0 and are currently developing a Camel component and on > trying to build an artifact using „mvn clean install“ or „mvn clean package“ > the build fails due to: Missing component documentation for the following > options: … as the component class defines a getter and setter for a property > with @UriEndpoint and other documentation enabled in Endpoint and > Configuration classes. If the getter/setter is removed from the component > class and the value assignment moved to a customized constructor the build > succeeds. Putting a @UriParam (or similar) annotation on the component > property does not solve the problem and specifying an @Uri… annotation on the > getter/setter does not work either as they are restricted to fields or > classes. > > Is validation considered working as intended as components should not define > getter/setter and therefore properties or is this a bug? -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
