camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: Where to get the component jars
Date Sat, 17 May 2008 06:16:01 GMT
Is there any tool can help us generate the dependency jars ?
Or we can write a maven plugin to generate that kind of report.

Willem

Claus Ibsen wrote:
> Hi
>
> Great idea.
>
> On the component list itself there is a column for the maven2 artifactId that you should
use for dependency:
> http://activemq.apache.org/camel/components.html
> For ActiveMQ: it states: activemq-core
>
> Maybe we should add a 2nd column for the groupId as well.
>
> And we could explain in the top of the component list how you get hold on the jars and
how you setup maven2 to include the desired component, just like Hiram did.
>
>
> Med venlig hilsen
>  
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsgårdsvænget 21
> 8362 Hørning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
> -----Original Message-----
> From: Bruce Snyder [mailto:bruce.snyder@gmail.com] 
> Sent: 16. maj 2008 23:40
> To: camel-dev@activemq.apache.org
> Subject: Re: Where to get the component jars
>
> On Fri, May 16, 2008 at 11:27 AM, Hiram Chirino <hiram@hiramchirino.com> wrote:
>   
>> Hey,
>>
>> I was wondering if it would be a good idea to add a section to all the
>> component documentation pages that explains what jar you need for the
>> component to work.  I've added an example the ActiveMQ component.
>> See:
>>
>> http://cwiki.apache.org/confluence/display/CAMEL/ActiveMQ
>>
>> Not sure if it's a good idea since version info in embedded into the
>> docs and that can easily get out of date very quickly.  But I'm sure
>> something like it would be handy for end users.
>>     
>
> This is a good idea. But, as you said, I'm not sure how to keep the
> versions from going out of date every time the software is revved.
>
> Bruce
>   


Mime
View raw message