I can't reproduce your error locally.. -- Andrea Cosentino ---------------------------------- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
On Wednesday, January 10, 2018, 8:30:31 PM GMT+1, Pascal Schumacher <pascalschumac...@gmx.net> wrote: Thanks! Maybe Windows is the cause. Am 10.01.2018 um 20:25 schrieb Andrea Cosentino: > Weird, I'll take a look tomorrow :-) > > Inviato da Yahoo Mail su Android > > Il mer, 10 gen, 2018 alle 20:20, Pascal >Schumacher<pascalschumac...@gmx.net> ha scritto: Thanks! > > I tried that yesterday. First I made these changes: > https://github.com/apache/camel/commit/57d028fca3b35530cb98b39a2263431023b346c1 > and than ran "mvn install" in the "camel\components\camel-ftp" directory. > > Now I notice there an camel-apt-error.log file in the camel-ftp > directory containing: > > Error processing @UriEndpoint > > java.lang.NullPointerException > at org.apache.camel.tools.apt.helper.IOHelper.close(IOHelper.java:73) > at > org.apache.camel.tools.apt.DocumentationHelper.findEndpointJavaDoc(DocumentationHelper.java:74) > at > org.apache.camel.tools.apt.EndpointAnnotationProcessor.createParameterJsonSchema(EndpointAnnotationProcessor.java:316) > at > org.apache.camel.tools.apt.EndpointAnnotationProcessor.writeJSonSchemeDocumentation(EndpointAnnotationProcessor.java:155) > at > org.apache.camel.tools.apt.EndpointAnnotationProcessor$1.call(EndpointAnnotationProcessor.java:128) > at > org.apache.camel.tools.apt.EndpointAnnotationProcessor$1.call(EndpointAnnotationProcessor.java:125) > at > org.apache.camel.tools.apt.AnnotationProcessorHelper.processFile(AnnotationProcessorHelper.java:348) > at > org.apache.camel.tools.apt.EndpointAnnotationProcessor.processEndpointClass(EndpointAnnotationProcessor.java:132) > at > org.apache.camel.tools.apt.EndpointAnnotationProcessor.process(EndpointAnnotationProcessor.java:88) > at > com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794) > at > com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705) > at > com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91) > at > com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035) > at > com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176) > at > com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856) > at com.sun.tools.javac.main.Main.compile(Main.java:523) > at com.sun.tools.javac.main.Main.compile(Main.java:381) > at com.sun.tools.javac.main.Main.compile(Main.java:370) > at com.sun.tools.javac.main.Main.compile(Main.java:361) > at com.sun.tools.javac.Main.compile(Main.java:56) > at com.sun.tools.javac.Main.main(Main.java:42) > > I guess it is because the javadoc:javadoc goal is not executed when > running "mvn install". > > So I tried to run "mvn clean javadoc:javadoc install", but that fails > with javadoc errors. > > > Am 10.01.2018 um 20:03 schrieb Andrea Cosentino: >> The install goal on a componenti will update the .adoc if something changed >> >> Inviato da Yahoo Mail su Android >> >> Il mer, 10 gen, 2018 alle 20:01, Pascal >>Schumacher<pascalschumac...@gmx.net> ha scritto: Hello everybody, >> >> which maven goal generates the component adoc from the javadoc? >> >> Thanks, >> >> Pascal >> >> >> > >
