Hi Yeah I think its great work. Makes it easier when we add other projects to camel-extra and in need of a maven repo for its jars.
And you are welcome to work on a proper release of camel-extra when Apache Camel 2.5 has been released. It would be great to have them in sync as you wrote in another mail. On Mon, Oct 11, 2010 at 2:33 PM, Henryk Konsek <hekon...@gmail.com> wrote: > I've just commit fix to unstable db4o dependencies. > > rev304 adds directory /maven2/others . This is repository for 3rd > party jars (like stable db4o) for camel-extra. > I also deployed com.db4o:db4o-core-java5:3.12 there. > > rev305 (sorry for SVN comment missed) fixes db4o dependency to the > stable one in /trunk/components/camel-db4o/pom.xml. > I also added new repository (/maven2/others) to parent POM > (/trunk/pom.xml) so that all camel-extra components have access to the > new 3rd party repo. > > If only db4o releases stable maven repo, I'll remove db4o from our > camel-extra repository. > > Is such approach fair enough? > > -- > Henryk Konsek > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
