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 <[email protected]> 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 > [email protected] > https://www.redhat.com/mailman/listinfo/devtools >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
