Yeah good idea to keep them in the eips folder. We may need to adjust
the maven and catalog tooling about this folder name. I can't remember
what they are doing now. But that is fine we take a look later when we
have more EIPs migrated and can use the tooling to keep the TOC up to
date and docs for the camel-catalog and whatnot.
On Thu, Feb 16, 2017 at 7:51 AM, Andrea Cosentino
> Hi Sebastien,
> Sure, go for it.
> Andrea Cosentino
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
> On Thursday, February 16, 2017 6:32 AM, Sébastien Col
> <sebastien...@gmail.com> wrote:
> Hi Andrea,
> I just noticed that the EIPs you migrated are right
> under camel-core/src/main/docs, along with components. I have worked on
> migrating missing EIPs and I was thinking of grouping them into a "eips"
> Do you mind if I move your files into this folder?
> 2017-01-17 9:43 GMT+01:00 Andrea Cosentino <ancosen1...@yahoo.com.invalid>:
>> Hey Sebastien,
>> At the moment I was looking at the wire-tap page.
>> Feel free to work on any other you want :-)
>> Thanks for your help!
>> Andrea Cosentino
>> Apache Camel PMC Member
>> Apache Karaf Committer
>> Apache Servicemix Committer
>> Email: ancosen1...@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>> On Tuesday, January 17, 2017 8:37 AM, Sébastien Col <
>> sebastien...@gmail.com> wrote:
>> Hi Andrea,
>> I was thinking of working on it also, which ones are you working on?
>> 2017-01-16 10:39 GMT+01:00 Andrea Cosentino <ancosen1...@yahoo.com.invalid
>> > For the point 1, I already started migrating some of them.
>> > --
>> > Andrea Cosentino
>> > ----------------------------------
>> > Apache Camel PMC Member
>> > Apache Karaf Committer
>> > Apache Servicemix Committer
>> > Email: ancosen1...@yahoo.com
>> > Twitter: @oscerd2
>> > Github: oscerd
>> > On Monday, January 16, 2017 10:29 AM, Claus Ibsen <claus.ib...@gmail.com
>> > wrote:
>> > Hi
>> > There is a bunch of stuff which we can/should have on the roadmap to
>> > complete for the Camel 2.19 release.
>> > Here is on top of my head
>> > 1)
>> > Finish migrating the wiki documentation to adoc files. I think its
>> > most of the EIP patterns that are missing. There is a basic list of
>> > EIPs here: https://github.com/apache/camel/blob/master/camel-core/
>> > readme-eip.adoc
>> > 2)
>> > Generate documentation and website. Maybe documentation first and then
>> > we come up with a modern website later - when we have a new logo as
>> > well.
>> > 3)
>> > Mark more stuff to @deprecate so we dont drag them into Camel 3.0.
>> > This is both components / and other artifacts.
>> > And as well the camel-core APIs where there is maybe more we can
>> > For example the old stuff that was created prior to the component docs
>> > we do now with the apt plugin at build time instead of this old code
>> > with runtime that dont really pan out anyway.
>> > 4)
>> > Move spring-boot starters into the platforms folder. There is a ticket
>> > about this.
>> > 5)
>> > More improvements to spring boot auto configuration. We have a bunch
>> > of tickets on that.
>> > 6)
>> > Look at the health check API and see if there is something we can get
>> > started on.
>> > Possible some API to integrate with spring boot actuators (when using
>> > SB) and allow each component to provide their own checks so they can
>> > be implemented ad-hoc. There is a ticket about this.
>> > 7)
>> > Possible some more teaks to camel-catalog based on feedback from IDEA
>> > plugin and the maven validate goal.
>> > 8)
>> > That CDI JEE transaction PR on github.
>> > Ideally we would have had a transaction API in camel-core and then one
>> > impl for camel-spring, and then another for camel-cdi-jee. But that
>> > may require too much work.
>> > 9)
>> > Work on the Java 8 DSL such as get more community feedback, and then
>> > resolve the TODOs with the documentation updates and look into other
>> > areas where the API can benefit from Java 8 lambdas and whatnot. I
>> > dont think we have a ticket about this.
>> > 10)
>> > Karaf users may want to improve/finish up the camel-test-karaf module
>> > so its more usable and end users can use it to test integration tests
>> > with Camel and Karaf.
>> > 11)
>> > Introduce Camel Connectors (more about this later)
>> > Anything else?
>> > --
>> > Claus Ibsen
>> > -----------------
>> > http://davsclaus.com @davsclaus
>> > Camel in Action 2: https://www.manning.com/ibsen2
Camel in Action 2: https://www.manning.com/ibsen2