Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 209.85.220.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALTd4v8UJHP3+DhSkatQVnQA9dhhUMPX2JNR=00JcY0+gt7tTA@mail.gmail.com>
References: 
 <CALTd4v_kW5un1YZWjqHs_J9dd8zPenhNXOi21O67U=DRR4pTyA@mail.gmail.com>
 <1367189188134-5731708.post@n5.nabble.com>
 <CALTd4v8UJHP3+DhSkatQVnQA9dhhUMPX2JNR=00JcY0+gt7tTA@mail.gmail.com>
From: James Strachan <james.strachan@gmail.com>
Date: Mon, 29 Apr 2013 07:05:51 +0100
Message-ID: 
 <CALTd4v8O3_F9MGuz4nL2EpuGbiQ3jx-CeLfP6d0pGLe_x9z3GQ@mail.gmail.com>
Subject: Re: improving Endpoint documentation and tooling
To: dev@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 29 April 2013 07:00, James Strachan <james.strachan@gmail.com> wrote:
> On 28 April 2013 23:46, Babak Vahdat <babak.vahdat@swissonline.ch> wrote:
>> Hi James,
>>
>> Another awesome stuff of yours, Thanks!
>>
>> Though I've got three questions:
>>
>> 1) Following the instructions of yours above I don't see any generated html
>> docs @
>>
>>         camel-core/target/classes/org/apache/camel/component
>>
>> Is there any other steps I'm missing here?
>
> No - though I used JDK 1.7; which JDK & OS are you using?

FWIW I just tried JDK 1.6 then I got no HTML generated.

The build seems to work OK for me though.


>> 2) My suspicion is that the recent failed compilation by our
>> Camel.trunk.notest CI-Server profile is because of the new Maven module
>> (org.apache.camel.apt) as apparently JDK 6 annotation processing has known
>> bug(s). So my question is if there would be some easy way to disable
>> annotation processing (e.g using a profile) so that we could experiment this
>> on CI-Server to see if this would be really the root cause of the problem?
>
> Yeah, we could disable the apt dependency unless on JDK. Am on
> vacation today; will take a stab tomorrow if noone beats me to it. The
> apt is only for the doc generation; so its no biggie to only enable it
> on a profile or jdk basis.
>
>
>
>> And if we could provide a proper fix of this. More details here:
>>
>>
>> http://camel.465427.n5.nabble.com/Our-builds-looks-really-bad-td5731673.html
>>
>> 3) Would it make sense to restrict the EndpointAnnotationProcessor's
>> @SupportedAnnotationTypes to ONLY:
>>
>>         @SupportedAnnotationTypes({"org.apache.camel.spi.*"})
>>
>> I think in this way we could skip the non relevant annotations we have like
>> "org.apache.camel.language.NamespacePrefix" which is currently causing
>> problem on CI-Server.
>
> Ah yeah, thats a good idea! Just committed; I also used Java 7 source
> format for the annotation processor in case that helps.

I just rolled that bit back; as the Java 7 source flag doesn't work on
JDK 1.6 :)

--
James
-------
Red Hat

Email: jstracha@redhat.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/

Open Source Integration