this message in context:
http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-tp5731334p5733219.html
Sent from the Camel Development mailing list archive at Nabble.com.
JDK 1.6, the annotation processing to be not that
>>> much
>>> stable but as long as we can make it to not break our builds then it's
>>> fine and we could mention this on Wiki that this documentation feature is
>>> only available using JDK 1.7+
>>>
&
On 30 April 2013 08:58, Babak Vahdat wrote:
> I did the following changes to make the CI build work again on JDK 1.6:
>
> https://github.com/apache/camel/blob/trunk/camel-core/pom.xml#L395
> https://github.com/apache/camel/blob/trunk/components/pom.xml#L214
>
> Makes sense?
Ah OK, thanks!
> Als
available using JDK 1.7+
>>
>> I've got a Windows box as well (hope you can believe me :-)) and will try
>> to run the build both using JDK 1.6 & JDK 1.7 on that as well to see how
>> that would go.
>
> Thanks! At least the CI builds seem to work fine on Java 1.6 now; so
> maybe we don't have to exclude the apt module for Java 1.6?
>
> --
> James
> ---
> Red Hat
>
> Email:
> jstracha@
> Web: http://fusesource.com
> Twitter: jstrachan, fusenews
> Blog: http://macstrac.blogspot.com/
>
> Open Source Integration
--
View this message in context:
http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-tp5731334p5731774.html
Sent from the Camel Development mailing list archive at Nabble.com.
On 29 April 2013 09:01, Babak Vahdat wrote:
>
>
> Am 29.04.13 08:00 schrieb "James Strachan" unter
> :
>
>>On 28 April 2013 23:46, Babak Vahdat wrote:
>>> Hi James,
>>>
>>> Another awesome stuff of yours, Thanks!
>>>
>>> Though I've got three questions:
>>>
>>> 1) Following the instructions of yo
Am 29.04.13 08:00 schrieb "James Strachan" unter
:
>On 28 April 2013 23:46, Babak Vahdat 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 @
>>
>>
On 29 April 2013 07:00, James Strachan wrote:
> On 28 April 2013 23:46, Babak Vahdat 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 @
>>
>> c
On 28 April 2013 23:46, Babak Vahdat 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
tly causing
problem on CI-Server.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-tp5731334p5731708.html
Sent from the Camel Development mailing list archive at Nabble.com.
I've added a couple of wiki pages to help describe the new capabilities:
the endpoint annotations:
https://cwiki.apache.org/confluence/display/CAMEL/Endpoint+Annotations
the ComponentConfiguration API:
https://cwiki.apache.org/confluence/display/CAMEL/ComponentConfiguration
On 23 April 2013 09:
Endpoint documentation is manually created on the wiki which is quite
error prone; plus the wiki page has to then cope with every version of
Camel we release and is very easy to get stale and incorrect - and
with all the 'since version X' text its confusing for users.
Additionally its hard for too
11 matches
Mail list logo
