Finally we migrated all the remaining EIPs. So now we need to write a TOC and go ahead with the new website.
Thanks a lot to Onder for his great help! -- Andrea Cosentino ---------------------------------- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, February 8, 2018, 2:27:33 PM GMT+1, Claus Ibsen <claus.ib...@gmail.com> wrote: It does not create the adoc files itself, it just reports its missing. So you add that file yourself. On Thu, Feb 8, 2018 at 2:23 PM, Onder SEZGIN <ondersez...@gmail.com> wrote: > and some eips don't get created by those json files? > eg: how convertBodyTo-eip.adoc is created? > > > On Thu, Feb 8, 2018 at 4:10 PM, Onder SEZGIN <ondersez...@gmail.com> wrote: > >> Ok so far, code reading is going on for me before completing missing eips. >> As far as i can understand, camel-maven-package-plugin reads up all .json >> files under target/classes/org/apache/camel/model. >> >> I think something else under buildtools or tooling places those json files. >> Can somebody tell me how those are getting created, or at least could you >> guide me a starting point to read the code and complete missing eips? >> >> >> On Wed, Feb 7, 2018 at 3:15 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> >>> Hi >>> >>> For the EIPs then you can see this table, and find the broken links >>> for the missing docs >>> https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc >>> >>> Or an alternative is to build camel-core, and in the end it reports a >>> list of missing EIP docs. >>> >>> mvn install -P fastinstall >>> >>> Also some of the existing EIP doc pages could use some examples, as >>> that helps end users to understand these EIPs better. We also added >>> some EIPs in the new adoc that was not on the old site, eg >>> convertBodyTo etc. >>> >>> Some of the DSL models from Camel is skipped for that readme page, but >>> we could essentially if we wanted have an adoc page for every one, >>> also those DSL types for configuring stuff, or those that refer to >>> cross cutting functionality such as error handling etc. >>> >>> But lets start with getting the EIPs docs finished. >>> >>> >>> On Wed, Feb 7, 2018 at 1:08 PM, Andrea Cosentino >>> <ancosen1...@yahoo.com.invalid> wrote: >>> > I don't think there is an easy way, once we finish to migrate the >>> remaining EIPs, we'll need to write a TOC of what we want in the >>> documentation and then migrate only the confluence pages related to the TOC. >>> > >>> > -- >>> > Andrea Cosentino >>> > ---------------------------------- >>> > Apache Camel PMC Member >>> > Apache Karaf Committer >>> > Apache Servicemix PMC Member >>> > Email: ancosen1...@yahoo.com >>> > Twitter: @oscerd2 >>> > Github: oscerd >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Wednesday, February 7, 2018, 1:05:03 PM GMT+1, Onder SEZGIN < >>> ondersez...@gmail.com> wrote: >>> > >>> > >>> > >>> > >>> > >>> > Hi, >>> > >>> > Considering, CAMEL-11497; >>> > >>> > I have generated adoc files from confluence export. >>> > There are almost 900 adoc files. And also I've checkout exsiting adoc >>> files >>> > under my local git clone. >>> > >>> > :~/github/camel$ ls -ltrR | grep ".adoc" | wc -l >>> > 872 >>> > >>> > I think the numbers are quite close. >>> > >>> > I think i can catch up with missing adoc files. >>> > >>> > As complete build to generated all adoc file takes quite a bit long time >>> > for my old computer, i am considering comparing all the adoc file >>> generated >>> > by cxf-web and complete build's result of adoc files. >>> > >>> > So i think i can write a quick small bash command to do such comparison, >>> > but the problem is that some adoc files in the repo and cxf-web's export >>> > does not match. >>> > I think it is because of naming convention used to generate .adoc file >>> from >>> > the repo. >>> > >>> > Is there an easy way to detect and compare both list to find out missing >>> > pieces from repo and the pieces existing in the confluence export. >>> > >>> > That will make comparing easier and add missing adoc files to >>> repository. >>> > >>> > Thanks. >>> > >>> > Ex: >>> > >>> > :~/github/cxf-web/export/camel$ ls -l loop.adoc >>> > -rw-rw-r-- 1 virt virt 5009 Şub 6 11:20 loop.adoc >>> > >>> > ~/github/camel/camel-core/src/main/docs/eips$ ls -l loop-eip.adoc >>> > -rw-rw-r-- 1 onders onders 5786 Şub 6 11:58 loop-eip.adoc >>> > >>> > >>> > On Tue, Feb 6, 2018 at 3:16 PM, Zoran Regvart <zo...@regvart.com> >>> wrote: >>> > >>> >> Hi Önder, >>> >> gulp will do some of the work[1] to copy and transform existing files. >>> >> I think the easiest way could be to create new ascii docs on the >>> >> master and then rebase the website branch to pick those up, >>> >> >>> >> zoran >>> >> >>> >> [1] https://github.com/apache/camel/blob/website/camel-website/ >>> gulpfile.js >>> >> >>> >> On Tue, Feb 6, 2018 at 10:11 AM, Onder SEZGIN <ondersez...@gmail.com> >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > I have gone through the steps Andrea described and checked out >>> Zoran's >>> >> > branch. >>> >> > >>> >> > Now following Zoran's read me to install and run website on my local >>> and >>> >> > see the changes. >>> >> > >>> >> > Is there a suggested way to merge adocs's exports and new website? >>> or i >>> >> > will figure that out. >>> >> > >>> >> > Thanks. >>> >> > >>> >> > >>> >> > On Fri, Feb 2, 2018 at 1:24 PM, Zoran Regvart <zo...@regvart.com> >>> wrote: >>> >> > >>> >> >> Hi Onder, >>> >> >> this is awesome, I've (some time ago) laid out a plan for the new >>> >> >> website with subtasks of CAMEL-11492[1] feel free to take anyone of >>> >> >> those. >>> >> >> >>> >> >> I think the easiest way to start is to checkout that branch (needs >>> >> >> rebase), and thinker with the static site generation to get the hang >>> >> >> of it. Reach out if you have any questions/issues that you >>> encounter. >>> >> >> >>> >> >> My apologies for not working on this I hope to find some time to >>> >> >> continue working on this soon, >>> >> >> >>> >> >> zoran >>> >> >> >>> >> >> [1] https://issues.apache.org/jira/browse/CAMEL-11492 >>> >> >> >>> >> >> On Thu, Feb 1, 2018 at 11:09 AM, Onder SEZGIN < >>> ondersez...@gmail.com> >>> >> >> wrote: >>> >> >> > Hi, >>> >> >> > >>> >> >> > I will be available to help with this in the following weeks. >>> >> >> > In addition to the steps, Andrea described earlier and the work on >>> >> >> > branch[1], how can i help with this? >>> >> >> > Any guidance will be great for me to help more quickly. >>> >> >> > Thanks. >>> >> >> > >>> >> >> > [1] https://github.com/apache/camel/tree/website/camel-website >>> >> >> > >>> >> >> >>> >> >> >>> >> >> -- >>> >> >> Zoran Regvart >>> >> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> Zoran Regvart >>> >> >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> http://davsclaus.com @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >>> >> >> -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
