It would have been better if you checked the issues first, this one in particular: http://code.google.com/p/camel-extra/issues/detail?id=22
As it is, camel-extra violates the ASF policies by using the apache package names. I am in the process of clarifying this. There was a discuss about that, but nobody seemed to care. The best bet so far seems to be using org.apachextra.camel.extra or something like that and we move the project there (still google code, separate area). And we will probably need to redo the release. With that change we could also publish to maven central. Hadrian On Feb 3, 2011, at 3:05 AM, Henryk Konsek (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/CAMEL-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990006#comment-12990006 > ] > > Henryk Konsek commented on CAMEL-3615: > -------------------------------------- > > Camel-extra 2.6.0 artifacts released. > > Now I need only to upgrade version of project to 2.7-SNAPSHOT (i.e. migrate > commons-logging to SLF4J). > >> Release Camel Extra 2.6.0 >> ------------------------- >> >> Key: CAMEL-3615 >> URL: https://issues.apache.org/jira/browse/CAMEL-3615 >> Project: Camel >> Issue Type: Task >> Reporter: Claus Ibsen >> >> We should release camel-extra 2.6.0 which is upgraded to use camel 2.6. > > -- > This message is automatically generated by JIRA. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
