Re: [che-dev] Che stack for Apache Camel/Fuse projects

[Dave Neary <dneary@xxxxxxxxxx>]

Hi Aurélien, Eugene,

This might be a good test case for shipping a stack as a plug-in -
Aurélien, are you willing to put up with a bit of pain and be a guinea
pig for this process? Florent Beloit, who I think you know, is doing
some work on what we call the "Walking Skeleton", a bare-bones extension
packaged as a plug-in for Che.

What do you think?

Thanks,
Dave.

On 09/11/2018 03:49 AM, Yevhen Ivantsov wrote:
> Hi Aurelien!
> 
>     What are the requirements to have it directly integrated in Eclipse Che?
> 
> 
> There are no requirements as such. We used to accept PRs into
> stacks.json and samples.json, whoever ended up in having a lot of stacks
> and samples that do not work. Of course this isn't good UX. Thus, we
> left only basic stacks.
> 
>     How tests are handled for Che stacks? (there are no tests in the
>     community project)
> 
> 
> There are stack tests
> here https://github.com/eclipse/che/tree/master/selenium/che-selenium-test/src/test/java/org/eclipse/che/selenium/stack
> 
>     What are the requirements to have the Camel Docker file in this
>     repository?
> 
> 
> Dockerfiles in that repo are used for automated builds on DockerHub to
> produce eclipse/$image images. To be honest, there are no reqs, now we
> try to keep the default stacks and sample list as soon as possible.
> 
>     Camel requires the same kind of dependency with SpringBoot but with
>     a different version. What is the best:
> 
> 
> SpringBoot image is just a Java image with ~/.m2 pre-populated with
> Springboot deps.  It is usually done to match Springboot version of a
> related sample application.  So, if you update deps there, you should
> probably update version of Springboot the sample app uses.
> 
>     I also noticed that we can have single-machine or multi-machine.
>     Several questions comes to my mind:
> 
> 
> There are no words of caution regarding multi machine workspaces. The
> only thing to bear in mind is that recipe type: compose isn't supported
> on k8s/OpenShift infra and vice versa. Memory consumption should be the
> same. 
> 
> 
> 
> _______________________________________________
> che-dev mailing list
> che-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/che-dev
> 

-- 
Dave Neary - Open Source and Standards team
Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338