Re: Javadoc error

2020-12-16 Thread Gregor Zurowski
Thanks, Claus. I confirm that this fixes the build issues. On Wed, Dec 16, 2020 at 7:32 AM Claus Ibsen wrote: > > Hi Gregor > > Okay I have a fix now. There is 1 commit on the 3.7.x branch from today. > > On Tue, Dec 15, 2020 at 10:31 PM Gregor Zurowski > wrote: > > > > Hi Claus, > > > > I am no

Re: Javadoc error

2020-12-15 Thread Claus Ibsen
Hi Gregor Okay I have a fix now. There is 1 commit on the 3.7.x branch from today. On Tue, Dec 15, 2020 at 10:31 PM Gregor Zurowski wrote: > > Hi Claus, > > I am now only getting the following WARNING which will also fail the > release buid: > > === > [WARNING] Javadoc Warnings > [WARNING] javad

Re: Javadoc error

2020-12-15 Thread Claus Ibsen
On Tue, Dec 15, 2020 at 10:31 PM Gregor Zurowski wrote: > > Hi Claus, > > I am now only getting the following WARNING which will also fail the > release buid: > > === > [WARNING] Javadoc Warnings > [WARNING] javadoc: warning - Multiple sources of package comments > found for package "javax.annotat

Re: Javadoc error

2020-12-15 Thread Gregor Zurowski
Hi Claus, I am now only getting the following WARNING which will also fail the release buid: === [WARNING] Javadoc Warnings [WARNING] javadoc: warning - Multiple sources of package comments found for package "javax.annotation" === When I build endpoint DSL with `mvn javadoc:javadoc` a second tim

Re: Javadoc error

2020-12-15 Thread Claus Ibsen
Hi Okay Gregor its fixed now. There are 3 more commits on 3.7.x branch from today. On Tue, Dec 15, 2020 at 11:02 AM Claus Ibsen wrote: > > Hi Gregor > > Ah okay I am working on fixing those WARNs now > > On Tue, Dec 15, 2020 at 10:48 AM Gregor Zurowski > wrote: > > > > Hi Claus, > > > > I've lo

Re: Javadoc error

2020-12-15 Thread Claus Ibsen
Hi Gregor Ah okay I am working on fixing those WARNs now On Tue, Dec 15, 2020 at 10:48 AM Gregor Zurowski wrote: > > Hi Claus, > > I've looked into this again and realized that the WARNINGs in the > Javadoc creation phase will break the build during release creation. I > am still getting a longe

Re: Javadoc error

2020-12-15 Thread Gregor Zurowski
Hi Claus, I've looked into this again and realized that the WARNINGs in the Javadoc creation phase will break the build during release creation. I am still getting a longer list of Javadoc WARNINGs when I run `mvnw javadoc:javadoc` on `/camel/core/camel-endpointdsl`: [...] [WARNING] Javadoc Warni

Re: Javadoc error

2020-12-14 Thread Gregor Zurowski
Hi Claus, Thank you so much for your fast response and the fix for this. It is not an issue for the 3.7.0 release, but mostly for a new build setup I am working on. As mentioned in my initial post, I am using Java 8 there, but it seems also picky about those Javadoc annotations. I just checked ou

Re: Javadoc error

2020-12-14 Thread Claus Ibsen
Hi Gregor Okay so the javadoc issue has been fixed. There are about 7 commits on the 3.7.x branch with CAMEL-15946 as prefix that all together fixes this. On Mon, Dec 14, 2020 at 4:00 PM Gregor Zurowski wrote: > > Hi Everyone: > > I am getting the following error when building Javadoc for DSL En

Re: Javadoc error

2020-12-14 Thread Claus Ibsen
I have a potential fix in the source code generator for endpoint and component DSL. So I am rebuild all the components. I will let you know when its fixed. If you need to cherry pick any commits then they will also be on the 3.7.x branch. On Mon, Dec 14, 2020 at 4:37 PM Claus Ibsen wrote: > > Hi

Re: Javadoc error

2020-12-14 Thread Claus Ibsen
Hi I have created a ticket https://issues.apache.org/jira/browse/CAMEL-15946 There is a few commits on the way that fixes some part of this. The generated source code for default values need to take into account HTML escaping. On Mon, Dec 14, 2020 at 4:14 PM Claus Ibsen wrote: > > Hi > > I als

Re: Javadoc error

2020-12-14 Thread Claus Ibsen
Hi I also see this kind of error when building with JDK11. Probably with more sub errors because javadoc is more stricter on JDK11 (eg no @return is a failure, etc.). The endpoint DSL is source code generated, and it seems that javadoc parser fails such as > should be escaped. That is not really