+1

Ant users have access to Ivy which allows them to resolve the
necessary dependancies also.  A note could be added that references Ivy for
the Ant users, though any current Ant users should be fully aware of it
already.

Best Regards,
Scott ES

On Tue, Nov 6, 2012 at 7:32 AM, Willem jiang <willem.ji...@gmail.com> wrote:

> +1 to remove these jars.
> It could be reasonable if we provides a third part dependents jars list
> which could be generated by maven.
> That could help the user who don't use maven.
>
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
> (English)
>           http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
>
>
> On Tuesday, November 6, 2012 at 8:48 PM, Claus Ibsen wrote:
>
> > Hi
> >
> > In the binary distro of Apache Camel we have in the lib directory a
> > number of 3rd party JARs
> >
> > lib/slf4j-api-1.6.6.jar
> >
> > lib/optional/
> > commons-beanutils-1.8.3.jar geronimo-j2ee-management_1.0_spec-1.1.jar
> > commons-collections-3.2.1.jar geronimo-jms_1.1_spec-1.1.1.jar
> > commons-dbcp-1.4.jar jasypt-1.9.0.jar
> > commons-lang-2.6.jar log4j-1.2.17.jar
> > commons-pool-1.6.jar slf4j-log4j12-1.6.6.jar
> > geronimo-j2ee-jacc_1.0_spec-1.1.jar
> >
> > lib/spring/
> > aopalliance-1.0.jar spring-expression-3.0.7.RELEASE.jar
> > commons-logging-1.1.1.jar spring-jdbc-3.0.7.RELEASE.jar
> > spring-aop-3.0.7.RELEASE.jar spring-jms-3.0.7.RELEASE.jar
> > spring-asm-3.0.7.RELEASE.jar spring-orm-3.0.7.RELEASE.jar
> > spring-beans-3.0.7.RELEASE.jar spring-test-3.0.7.RELEASE.jar
> > spring-context-3.0.7.RELEASE.jar spring-tx-3.0.7.RELEASE.jar
> > spring-context-support-3.0.7.RELEASE.jar spring-web-3.0.7.RELEASE.jar
> > spring-core-3.0.7.RELEASE.jar
> >
> >
> > I think we should stop including these JARs as they are not needed.
> > They were included back in the days when some of the examples could be
> > run from ANT, which would refer to these JARs to run.
> > But all the examples is Maven based now. And all needed JARs is
> > downloaded on-the-fly.
> >
> > So maybe we should restructure the lib directory?
> >
> > This will also cut down on the size of the distribution and make Camel
> > seems even more light-weight.
> >
> > Any thoughts?
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > Email: cib...@redhat.com (mailto:cib...@redhat.com)
> > Web: http://fusesource.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
>


-- 
-- 
Scott England-Sullivan
Apache Camel Committer
Principal Consultant / Sr. Architect | Red Hat, Inc.
FuseSource is now part of Red Hat
Web:     fusesource.com <http://www.fusesource.com> |
redhat.com<http://www.redhat.com>
Blog:     sully6768.blogspot.com
Twitter: sully6768

Reply via email to