From bsutter at redhat.com Mon May 14 21:44:29 2018 From: bsutter at redhat.com (Burr Sutter) Date: Mon, 14 May 2018 14:44:29 -0700 Subject: [Devtools] Fabric8 futures Message-ID: Did we ever come to agreement on keeping F8 alive? Specifically the base docker images maven plugin bit.ly/msa-instructions still relies on these tools and that is still one of our most successful assets (seen in bit.ly/microservicesvideo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhuss at redhat.com Wed May 16 16:44:27 2018 From: rhuss at redhat.com (Roland Huss) Date: Wed, 16 May 2018 09:44:27 -0700 Subject: [Devtools] Fabric8 futures In-Reply-To: References: Message-ID: Hi Burr, let me try to comment from a Fuse perspective: * We are still committed to the fabric8 base images (s2i [1] and non-s2i [2]) as they are the only community images available. We will continue to use them in the future FIS releases (at least upstream). * The fabric8-maven-plugin's [3] scope has diverged from our use cases, so we plan to explore new ways of providing a way to leverage OpenShift builds and deployments for the FIS quickstarts. I.e. fmp's scope gets aligned currently to its usage in openshift.io, drifting away from being a general purpose plugin. Also, many features (like gofabric8, helm, cluster installation, .. support) are of no use for us, so we don't want to maintain them for no obvious reason. We have some initial ideas, but nothing concrete. So happy to start a discussion with Devtools, RHOAR and you how to align plans. * Fabric8's docker-maven-plugin [4] will be still supported in the upstream (it has been productised only as an integral part of f-m-p) These our current plan but we too are interested in what the dev tools team is planning on doing, of course. regards ... ... roland [1]: https://github.com/fabric8io-images/s2i [2]: https://github.com/fabric8io-images/java [3]: https://github.com/fabric8io/fabric8-maven-plugin [4]: https://github.com/fabric8io/docker-maven-plugin On Mon, May 14, 2018 at 9:45 PM Burr Sutter wrote: > Did we ever come to agreement on keeping F8 alive? > > Specifically the > base docker images > maven plugin > > bit.ly/msa-instructions still relies on these tools and that is still one > of our most successful assets (seen in bit.ly/microservicesvideo) > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Fri May 25 19:06:59 2018 From: manderse at redhat.com (Max Andersen) Date: Fri, 25 May 2018 21:06:59 +0200 Subject: [Devtools] Fabric8 futures In-Reply-To: References: Message-ID: <30B1AA38-5D09-4A47-9590-F4D436D7D8DA@redhat.com> Roland - if you are seeing OpenShift.io based fixes that don?t make sense please speak up. I didn?t see any feedback on the roadmap request for inputs. The intent is for sure not to diverge away. We want to work together on this rather than see even more new forks. And yes gofabric8 etc. is also not of use for us. The whole images situation we should work on aligning as that also relate to middleware etc. /max http://about.me/maxandersen > On 16 May 2018, at 18:44, Roland Huss wrote: > > Hi Burr, > > let me try to comment from a Fuse perspective: > > * We are still committed to the fabric8 base images (s2i [1] and non-s2i [2]) as they are the only community images available. We will continue to use them in the future FIS releases (at least upstream). > > * The fabric8-maven-plugin's [3] scope has diverged from our use cases, so we plan to explore new ways of providing a way to leverage OpenShift builds and deployments for the FIS quickstarts. I.e. fmp's scope gets aligned currently to its usage in openshift.io, drifting away from being a general purpose plugin. Also, many features (like gofabric8, helm, cluster installation, .. support) are of no use for us, so we don't want to maintain them for no obvious reason. > We have some initial ideas, but nothing concrete. So happy to start a discussion with Devtools, RHOAR and you how to align plans. > > * Fabric8's docker-maven-plugin [4] will be still supported in the upstream (it has been productised only as an integral part of f-m-p) > > These our current plan but we too are interested in what the dev tools team is planning on doing, of course. > > regards ... > ... roland > > [1]: https://github.com/fabric8io-images/s2i > [2]: https://github.com/fabric8io-images/java > [3]: https://github.com/fabric8io/fabric8-maven-plugin > [4]: https://github.com/fabric8io/docker-maven-plugin > >> On Mon, May 14, 2018 at 9:45 PM Burr Sutter wrote: >> Did we ever come to agreement on keeping F8 alive? >> >> Specifically the >> base docker images >> maven plugin >> >> bit.ly/msa-instructions still relies on these tools and that is still one of our most successful assets (seen in bit.ly/microservicesvideo) >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: