You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2011/07/08 10:24:47 UTC
[DISCUSS] - Remove or reduce ANT support for Camel examples
Hi
We have 34 examples in the Camel kit. And frankly to keep most of them
updated to work and run with Apache Ant is a p*** in the ****.
I would like to discuss if we should consider reducing the number of
examples that can run with Ant?
The current pain points
- Keep Ant examples up to date is manual labor
- Some examples dont currently work as documented in README.txt file
- End user will have to manually download 3rd party libraries such as
Spring, ActiveMQ, Hibernate etc.
- End user will have to set environment variables for home, eg
ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
- Some examples have migrated and uses OpenJPA with Maven instead of
Hibernate, and thus running with Maven vs. Ant diverts.
I suggest that we remove ANT support for the more complicated examples
where you need to download many different 3rd party projects and
whatnot.
We may want to keep it on a few simpler examples that we know can be supported.
Sidebar
======
Now that we talk about examples. I would like to add a very simple
hello world examples as well.
Something we can use in the getting started guide, so people who
download the .zip / .tar can follow a guide.
And run the hello world example and see that Camel is up and running quickly.
For example it could be based on the maven archetype that creates a
sample project (that example which moves files using a Content Based
Router).
Then we could have this example supported by Ant and Maven.
=====
Any thoughts?
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Claus,
+1 to remove ANT from the examples.
Regarding the new hello world examples, it's a good idea, +1 also.
Maven archetype is also helpful for the users.
Regards
JB
On 07/08/2011 10:24 AM, Claus Ibsen wrote:
> Hi
>
> We have 34 examples in the Camel kit. And frankly to keep most of them
> updated to work and run with Apache Ant is a p*** in the ****.
> I would like to discuss if we should consider reducing the number of
> examples that can run with Ant?
>
> The current pain points
> - Keep Ant examples up to date is manual labor
> - Some examples dont currently work as documented in README.txt file
> - End user will have to manually download 3rd party libraries such as
> Spring, ActiveMQ, Hibernate etc.
> - End user will have to set environment variables for home, eg
> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
> - Some examples have migrated and uses OpenJPA with Maven instead of
> Hibernate, and thus running with Maven vs. Ant diverts.
>
> I suggest that we remove ANT support for the more complicated examples
> where you need to download many different 3rd party projects and
> whatnot.
> We may want to keep it on a few simpler examples that we know can be supported.
>
>
> Sidebar
> ======
> Now that we talk about examples. I would like to add a very simple
> hello world examples as well.
> Something we can use in the getting started guide, so people who
> download the .zip / .tar can follow a guide.
> And run the hello world example and see that Camel is up and running quickly.
> For example it could be based on the maven archetype that creates a
> sample project (that example which moves files using a Content Based
> Router).
>
> Then we could have this example supported by Ant and Maven.
> =====
>
> Any thoughts?
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Willem Jiang <wi...@gmail.com>.
Most example can be run with maven, we don't need to let all the Camel
examples can be run with ANT.
BTW, it could be great for the ant guys, if we can provide an ant task
to work as camel:run plugin.
Here is my +1.
On 7/8/11 4:24 PM, Claus Ibsen wrote:
> Hi
>
> We have 34 examples in the Camel kit. And frankly to keep most of them
> updated to work and run with Apache Ant is a p*** in the ****.
> I would like to discuss if we should consider reducing the number of
> examples that can run with Ant?
>
> The current pain points
> - Keep Ant examples up to date is manual labor
> - Some examples dont currently work as documented in README.txt file
> - End user will have to manually download 3rd party libraries such as
> Spring, ActiveMQ, Hibernate etc.
> - End user will have to set environment variables for home, eg
> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
> - Some examples have migrated and uses OpenJPA with Maven instead of
> Hibernate, and thus running with Maven vs. Ant diverts.
>
> I suggest that we remove ANT support for the more complicated examples
> where you need to download many different 3rd party projects and
> whatnot.
> We may want to keep it on a few simpler examples that we know can be supported.
>
>
> Sidebar
> ======
> Now that we talk about examples. I would like to add a very simple
> hello world examples as well.
> Something we can use in the getting started guide, so people who
> download the .zip / .tar can follow a guide.
> And run the hello world example and see that Camel is up and running quickly.
> For example it could be based on the maven archetype that creates a
> sample project (that example which moves files using a Content Based
> Router).
>
> Then we could have this example supported by Ant and Maven.
> =====
>
> Any thoughts?
>
>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Christian Müller <ch...@gmail.com>.
+1 for dropping the ANT support and also for a Camel "hello world" example.
+0 whether this example should have ANT support. +0 for having a Maven
archetype for this example.
Am 09.07.2011 13:12 schrieb "Claus Ibsen" <cl...@gmail.com>:
> Hi Donald
>
> Thank you for your input.
>
> Since the examples have pom.xml file, you can have Maven go download
> all the JAR files for you.
> There is a command to do that.
>
> And then you can just go about doing as you wish without Maven.
>
>
>
> On Fri, Jul 8, 2011 at 6:17 PM, Donald Whytock <dw...@gmail.com> wrote:
>> +0
>>
>> I can't speak for maintaining the Ant scripts for the examples. I can
>> imagine they're a PITA to maintain, and I'm certainly not about to
>> offer to do so.
>>
>> But in the context of this, I'd like to mention that I'm not a Maven
>> user. This isn't a matter of personal preference; I do my development
>> offline on a laptop with no network access, for various reasons
>> involving IP and security. I typically work with local standalone
>> servers -- mail servers, XMPP servers, database servers, etc.
>>
>> This means my usual method of installing a required third-party .jar
>> is to download it on another machine, copy it over to the laptop and
>> install it manually. This is among the reasons I rant sometimes about
>> dependence on third-party packages: it gets troublesome to do this
>> when dependency runs five levels deep. Reading someone saying, "Why
>> don't you just use X?" often makes me cringe.
>>
>> I'm willing to believe that I'm one of a very small number of people
>> (can it be as small as 1?) who develop this way with Camel. After
>> all, most people would develop a Camel application in an environment
>> more similar to their deployment environment. But I'd like to offer
>> it as something to think about when one is inclined to say, "It's
>> okay, our users will just use Maven anyway."
>>
>> Don
>>
>> On Fri, Jul 8, 2011 at 7:57 AM, Jon Anstey <ja...@gmail.com> wrote:
>>> Big +1. The Ant examples were always a pain to work with because we ship
>>> very few 3rd party libs with Camel... which meant you would need to
download
>>> many 3rd party distributions and set up several env variables before
even
>>> running... good riddance I say :)
>>>
>>> On Fri, Jul 8, 2011 at 5:54 AM, Claus Ibsen <cl...@gmail.com>
wrote:
>>>
>>>> Hi
>>>>
>>>> We have 34 examples in the Camel kit. And frankly to keep most of them
>>>> updated to work and run with Apache Ant is a p*** in the ****.
>>>> I would like to discuss if we should consider reducing the number of
>>>> examples that can run with Ant?
>>>>
>>>> The current pain points
>>>> - Keep Ant examples up to date is manual labor
>>>> - Some examples dont currently work as documented in README.txt file
>>>> - End user will have to manually download 3rd party libraries such as
>>>> Spring, ActiveMQ, Hibernate etc.
>>>> - End user will have to set environment variables for home, eg
>>>> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
>>>> - Some examples have migrated and uses OpenJPA with Maven instead of
>>>> Hibernate, and thus running with Maven vs. Ant diverts.
>>>>
>>>> I suggest that we remove ANT support for the more complicated examples
>>>> where you need to download many different 3rd party projects and
>>>> whatnot.
>>>> We may want to keep it on a few simpler examples that we know can be
>>>> supported.
>>>>
>>>>
>>>> Sidebar
>>>> ======
>>>> Now that we talk about examples. I would like to add a very simple
>>>> hello world examples as well.
>>>> Something we can use in the getting started guide, so people who
>>>> download the .zip / .tar can follow a guide.
>>>> And run the hello world example and see that Camel is up and running
>>>> quickly.
>>>> For example it could be based on the maven archetype that creates a
>>>> sample project (that example which moves files using a Content Based
>>>> Router).
>>>>
>>>> Then we could have this example supported by Ant and Maven.
>>>> =====
>>>>
>>>> Any thoughts?
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Jon
>>> ---------------
>>> FuseSource
>>> Email: jon@fusesource.com
>>> Web: fusesource.com
>>> Twitter: jon_anstey
>>> Blog: http://janstey.blogspot.com
>>> Author of Camel in Action: http://manning.com/ibsen
>>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Claus Ibsen <cl...@gmail.com>.
Hi Donald
Thank you for your input.
Since the examples have pom.xml file, you can have Maven go download
all the JAR files for you.
There is a command to do that.
And then you can just go about doing as you wish without Maven.
On Fri, Jul 8, 2011 at 6:17 PM, Donald Whytock <dw...@gmail.com> wrote:
> +0
>
> I can't speak for maintaining the Ant scripts for the examples. I can
> imagine they're a PITA to maintain, and I'm certainly not about to
> offer to do so.
>
> But in the context of this, I'd like to mention that I'm not a Maven
> user. This isn't a matter of personal preference; I do my development
> offline on a laptop with no network access, for various reasons
> involving IP and security. I typically work with local standalone
> servers -- mail servers, XMPP servers, database servers, etc.
>
> This means my usual method of installing a required third-party .jar
> is to download it on another machine, copy it over to the laptop and
> install it manually. This is among the reasons I rant sometimes about
> dependence on third-party packages: it gets troublesome to do this
> when dependency runs five levels deep. Reading someone saying, "Why
> don't you just use X?" often makes me cringe.
>
> I'm willing to believe that I'm one of a very small number of people
> (can it be as small as 1?) who develop this way with Camel. After
> all, most people would develop a Camel application in an environment
> more similar to their deployment environment. But I'd like to offer
> it as something to think about when one is inclined to say, "It's
> okay, our users will just use Maven anyway."
>
> Don
>
> On Fri, Jul 8, 2011 at 7:57 AM, Jon Anstey <ja...@gmail.com> wrote:
>> Big +1. The Ant examples were always a pain to work with because we ship
>> very few 3rd party libs with Camel... which meant you would need to download
>> many 3rd party distributions and set up several env variables before even
>> running... good riddance I say :)
>>
>> On Fri, Jul 8, 2011 at 5:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> We have 34 examples in the Camel kit. And frankly to keep most of them
>>> updated to work and run with Apache Ant is a p*** in the ****.
>>> I would like to discuss if we should consider reducing the number of
>>> examples that can run with Ant?
>>>
>>> The current pain points
>>> - Keep Ant examples up to date is manual labor
>>> - Some examples dont currently work as documented in README.txt file
>>> - End user will have to manually download 3rd party libraries such as
>>> Spring, ActiveMQ, Hibernate etc.
>>> - End user will have to set environment variables for home, eg
>>> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
>>> - Some examples have migrated and uses OpenJPA with Maven instead of
>>> Hibernate, and thus running with Maven vs. Ant diverts.
>>>
>>> I suggest that we remove ANT support for the more complicated examples
>>> where you need to download many different 3rd party projects and
>>> whatnot.
>>> We may want to keep it on a few simpler examples that we know can be
>>> supported.
>>>
>>>
>>> Sidebar
>>> ======
>>> Now that we talk about examples. I would like to add a very simple
>>> hello world examples as well.
>>> Something we can use in the getting started guide, so people who
>>> download the .zip / .tar can follow a guide.
>>> And run the hello world example and see that Camel is up and running
>>> quickly.
>>> For example it could be based on the maven archetype that creates a
>>> sample project (that example which moves files using a Content Based
>>> Router).
>>>
>>> Then we could have this example supported by Ant and Maven.
>>> =====
>>>
>>> Any thoughts?
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>>
>>
>>
>> --
>> Cheers,
>> Jon
>> ---------------
>> FuseSource
>> Email: jon@fusesource.com
>> Web: fusesource.com
>> Twitter: jon_anstey
>> Blog: http://janstey.blogspot.com
>> Author of Camel in Action: http://manning.com/ibsen
>>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Donald Whytock <dw...@gmail.com>.
+0
I can't speak for maintaining the Ant scripts for the examples. I can
imagine they're a PITA to maintain, and I'm certainly not about to
offer to do so.
But in the context of this, I'd like to mention that I'm not a Maven
user. This isn't a matter of personal preference; I do my development
offline on a laptop with no network access, for various reasons
involving IP and security. I typically work with local standalone
servers -- mail servers, XMPP servers, database servers, etc.
This means my usual method of installing a required third-party .jar
is to download it on another machine, copy it over to the laptop and
install it manually. This is among the reasons I rant sometimes about
dependence on third-party packages: it gets troublesome to do this
when dependency runs five levels deep. Reading someone saying, "Why
don't you just use X?" often makes me cringe.
I'm willing to believe that I'm one of a very small number of people
(can it be as small as 1?) who develop this way with Camel. After
all, most people would develop a Camel application in an environment
more similar to their deployment environment. But I'd like to offer
it as something to think about when one is inclined to say, "It's
okay, our users will just use Maven anyway."
Don
On Fri, Jul 8, 2011 at 7:57 AM, Jon Anstey <ja...@gmail.com> wrote:
> Big +1. The Ant examples were always a pain to work with because we ship
> very few 3rd party libs with Camel... which meant you would need to download
> many 3rd party distributions and set up several env variables before even
> running... good riddance I say :)
>
> On Fri, Jul 8, 2011 at 5:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> We have 34 examples in the Camel kit. And frankly to keep most of them
>> updated to work and run with Apache Ant is a p*** in the ****.
>> I would like to discuss if we should consider reducing the number of
>> examples that can run with Ant?
>>
>> The current pain points
>> - Keep Ant examples up to date is manual labor
>> - Some examples dont currently work as documented in README.txt file
>> - End user will have to manually download 3rd party libraries such as
>> Spring, ActiveMQ, Hibernate etc.
>> - End user will have to set environment variables for home, eg
>> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
>> - Some examples have migrated and uses OpenJPA with Maven instead of
>> Hibernate, and thus running with Maven vs. Ant diverts.
>>
>> I suggest that we remove ANT support for the more complicated examples
>> where you need to download many different 3rd party projects and
>> whatnot.
>> We may want to keep it on a few simpler examples that we know can be
>> supported.
>>
>>
>> Sidebar
>> ======
>> Now that we talk about examples. I would like to add a very simple
>> hello world examples as well.
>> Something we can use in the getting started guide, so people who
>> download the .zip / .tar can follow a guide.
>> And run the hello world example and see that Camel is up and running
>> quickly.
>> For example it could be based on the maven archetype that creates a
>> sample project (that example which moves files using a Content Based
>> Router).
>>
>> Then we could have this example supported by Ant and Maven.
>> =====
>>
>> Any thoughts?
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>
>
>
> --
> Cheers,
> Jon
> ---------------
> FuseSource
> Email: jon@fusesource.com
> Web: fusesource.com
> Twitter: jon_anstey
> Blog: http://janstey.blogspot.com
> Author of Camel in Action: http://manning.com/ibsen
>
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Jon Anstey <ja...@gmail.com>.
Big +1. The Ant examples were always a pain to work with because we ship
very few 3rd party libs with Camel... which meant you would need to download
many 3rd party distributions and set up several env variables before even
running... good riddance I say :)
On Fri, Jul 8, 2011 at 5:54 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> We have 34 examples in the Camel kit. And frankly to keep most of them
> updated to work and run with Apache Ant is a p*** in the ****.
> I would like to discuss if we should consider reducing the number of
> examples that can run with Ant?
>
> The current pain points
> - Keep Ant examples up to date is manual labor
> - Some examples dont currently work as documented in README.txt file
> - End user will have to manually download 3rd party libraries such as
> Spring, ActiveMQ, Hibernate etc.
> - End user will have to set environment variables for home, eg
> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
> - Some examples have migrated and uses OpenJPA with Maven instead of
> Hibernate, and thus running with Maven vs. Ant diverts.
>
> I suggest that we remove ANT support for the more complicated examples
> where you need to download many different 3rd party projects and
> whatnot.
> We may want to keep it on a few simpler examples that we know can be
> supported.
>
>
> Sidebar
> ======
> Now that we talk about examples. I would like to add a very simple
> hello world examples as well.
> Something we can use in the getting started guide, so people who
> download the .zip / .tar can follow a guide.
> And run the hello world example and see that Camel is up and running
> quickly.
> For example it could be based on the maven archetype that creates a
> sample project (that example which moves files using a Content Based
> Router).
>
> Then we could have this example supported by Ant and Maven.
> =====
>
> Any thoughts?
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Cheers,
Jon
---------------
FuseSource
Email: jon@fusesource.com
Web: fusesource.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Richard Kettelerij <ri...@gmail.com>.
+1 remove Ant. I don't think users will have a problem installing Maven when
they want to run an example.
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Remove-or-reduce-ANT-support-for-Camel-examples-tp4563886p4563970.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I have created a ticket to track this
https://issues.apache.org/jira/browse/CAMEL-4200
We will of course still keep an eye on the discussion and if the
balance is tipping in favor of keeping them all, then we wont remove
them. Although I wonder if anybody got the strengths and time to go
through all 34 examples and ensure the ANT examples works according to
the README.txt documentation.
We should prefer to keep one ANT example. For example a new hello
world example as discussed.
On Fri, Jul 8, 2011 at 10:24 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> We have 34 examples in the Camel kit. And frankly to keep most of them
> updated to work and run with Apache Ant is a p*** in the ****.
> I would like to discuss if we should consider reducing the number of
> examples that can run with Ant?
>
> The current pain points
> - Keep Ant examples up to date is manual labor
> - Some examples dont currently work as documented in README.txt file
> - End user will have to manually download 3rd party libraries such as
> Spring, ActiveMQ, Hibernate etc.
> - End user will have to set environment variables for home, eg
> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
> - Some examples have migrated and uses OpenJPA with Maven instead of
> Hibernate, and thus running with Maven vs. Ant diverts.
>
> I suggest that we remove ANT support for the more complicated examples
> where you need to download many different 3rd party projects and
> whatnot.
> We may want to keep it on a few simpler examples that we know can be supported.
>
>
> Sidebar
> ======
> Now that we talk about examples. I would like to add a very simple
> hello world examples as well.
> Something we can use in the getting started guide, so people who
> download the .zip / .tar can follow a guide.
> And run the hello world example and see that Camel is up and running quickly.
> For example it could be based on the maven archetype that creates a
> sample project (that example which moves files using a Content Based
> Router).
>
> Then we could have this example supported by Ant and Maven.
> =====
>
> Any thoughts?
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: [DISCUSS] - Remove or reduce ANT support for Camel examples
Posted by Freeman Fang <fr...@gmail.com>.
Hi Claus,
+1 for this idea. Maven obviously is more powerful regarding the
dependency management.
We do same for CXF examples and specifically add a antbuild example to
demonstrate how ant works, for other examples, just remove the ant
support.
Freeman
On 2011-7-8, at 下午4:24, Claus Ibsen wrote:
> Hi
>
> We have 34 examples in the Camel kit. And frankly to keep most of them
> updated to work and run with Apache Ant is a p*** in the ****.
> I would like to discuss if we should consider reducing the number of
> examples that can run with Ant?
>
> The current pain points
> - Keep Ant examples up to date is manual labor
> - Some examples dont currently work as documented in README.txt file
> - End user will have to manually download 3rd party libraries such as
> Spring, ActiveMQ, Hibernate etc.
> - End user will have to set environment variables for home, eg
> ACTIVEMQ_HOME, ASPECTJ_HOME, HIBERNATE_HOME etc.
> - Some examples have migrated and uses OpenJPA with Maven instead of
> Hibernate, and thus running with Maven vs. Ant diverts.
>
> I suggest that we remove ANT support for the more complicated examples
> where you need to download many different 3rd party projects and
> whatnot.
> We may want to keep it on a few simpler examples that we know can be
> supported.
>
>
> Sidebar
> ======
> Now that we talk about examples. I would like to add a very simple
> hello world examples as well.
> Something we can use in the getting started guide, so people who
> download the .zip / .tar can follow a guide.
> And run the hello world example and see that Camel is up and running
> quickly.
> For example it could be based on the maven archetype that creates a
> sample project (that example which moves files using a Content Based
> Router).
>
> Then we could have this example supported by Ant and Maven.
> =====
>
> Any thoughts?
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com