Hi, +1 to website and JDK 11 comptability definitely. One small note i want to say IMHO, velocity of adoption of new JDK releases in some corp env is not as fast as JDK releases. I am not saying JDK is super fast on new deliveries but in corp adoptions are somehow tedious and not easy.
it would be good if we have java 8 as the base minimum version. Thanks, Önder On Wed, Dec 12, 2018 at 9:38 AM Francois Papon <francois.pa...@openobject.fr> wrote: > Hi, > > I'm agree for the website and we could also add a new dedicated page > about Camel K ? > > Btw, I'm ready to help working on the website ;) > > Regards, > > François Papon > fpa...@apache.org > > Le 12/12/2018 à 06:57, Willem Jiang a écrit : > > Thanks for th Zoran, I think website is quite important for the user > > find the documents and solutions. > > We definitely could get some help from the community if we put it into > > the roadmap. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Dec 11, 2018 at 10:18 PM Zoran Regvart <zo...@regvart.com> > wrote: > >> Hi Cameleers, > >> exciting times ahead indeed :) > >> > >> I'd like to put the new website and work around Java 11 compatibility > >> on the roadmap. > >> > >> I had a couple of days to experiment with Antora for the user manual > >> and component documentation and thus far it seems very promising. Once > >> I merry this with the Hugo static site generator for the rest of the > >> pages we'll have a rough first pass of the new website (hope on doing > >> that soon). We've had a great deal of interest in getting this done > >> and few folks already helped or announced their willingness to help. > >> And I'm not saying that the website will be done for Camel 3 release, > >> I'd actually like to see it done in the next 1-2 months. > >> > >> For the Java 11 support, I think this should go in to the 2.x with our > >> current approach of testing on Java 11 and upgrading component > >> dependencies when they're Java 11 ready. All work on this is in the > >> `java-10-test` branch. One thought I had is that we could introduce a > >> `camel-java11-compat` dependency that would bring in the JEE APIs > >> (JAXB and the rest) that were removed from Java 11. For Camel 3, > >> perhaps we can make Java 11 the base minimum version -- would be good > >> to get some feedback on this. One more thing we could try to evaluate > >> is the use of Java modules, Camel 3, IMHO, should at least be Java > >> module ready, i.e. have `Automatic-Module-Name` in the manifest. > >> Perhaps we can count the number of component dependencies that are > >> usable on the module path and see if we can go ahead and add > >> `module-info.java` in (some?) of the components. > >> > >> zoran > >> On Tue, Dec 11, 2018 at 2:59 PM Andrea Cosentino > >> <ancosen1...@yahoo.com.invalid> wrote: > >>> Hello Camelers, > >>> > >>> We are starting the work on Apache Camel 3. We are working at multiple > levels to improve Camel and introduce new features. > >>> > >>> The first work has actually started by Guillaume Nodet in the start of > October, where he jump started by cleaning up the codebase, removed > deprecated code and components, improving the routing engine and other > internals in the core. His work is published on the sandbox/3.x branch. We > plan to use his work as the baseline for the actual Camel 3. I have helped > by aligning this branch with all the changes from the master branch (2.x) > so its fully up to date. The intention is to switch over the sandbox/3.x > branch as the new master branch, so we can start working on that branch and > being able to add new features, components etc. (as always) for Camel 3. > >>> > >>> For 2.x users we will create a 2.x branch where we plan to do 1 or 2 > more last 2.x releases, eg 2.24 and 2.25, before 3.0 is ready and released. > >>> > >>> Here in the beginning of the Camel 3 work is to continue the work from > Guillaume Nodet and finish up the cleanup of the codebase, modularize the > camel-core, etc. > >>> > >>> We invite community users and any Camel committers and developers who > has interest to help with the Camel 3 work. We have talked about doing a > number of milestone releases of 3.x that can help give feedback to us > quicker and faster. For example any Camel users of 2.x can try to upgrade > and use the 3.0 milestone releases to report back their findings. > >>> > >>> Over the coming weeks it would be good if we could work on the roadmap > and a rough timetable for Camel 3 so we can sketch out the first set of > goals for the first milestone release and then rinse and repeat for the > upcoming milestone releases. > >>> > >>> We have also talked about letting Camel 3 be a timeboxed release to > avoid it dragging out “forever”. It would be great if we can build and > release Camel 3 within 1 year of development, for example maybe try to aim > for a release in Q3 2019. > >>> > >>> We will keep the community posted on the progress, and as always we > love contribution and any feedback. > >>> > >>> Exciting times ahead! > >>> > >>> Thoughts? > >>> > >>> Claus & Andrea > >>> > >>> -- > >>> Andrea Cosentino > >>> ---------------------------------- > >>> Apache Camel PMC Chair > >>> Apache Karaf Committer > >>> Apache Servicemix PMC Member > >>> Email: ancosen1...@yahoo.com > >>> Twitter: @oscerd2 > >>> Github: oscerd > >> > >> > >> -- > >> Zoran Regvart >
