Am Mo., 13. Apr. 2020 um 00:45 Uhr schrieb David Jencks < david.a.jen...@gmail.com>:
> > That seems like a conceptual circular dependency with which I am not > entirely comfortable. However, it wouldn’t be blocking for me. > > As the example / blueprint is using releases from various places but is not used by other felix or aries projects I think we do not have a real circular dependency. I see the issue though. I also typically expect that felix projects are used in aries but not the other way round. So putting this in Aries might indeed be the better solution. I will spawn a discussion in Aries in parallel to see how the community there likes the idea. > > > > I agree about the naming. Blueprint was a bad choice. What do you think > > about "felix cloud native starter”. > > Names are hard…. ’native’ to me suggests you will be targeting one (or > more) of the nontraditional javas (that I am only vaguely acquainted with > from watching the Camel list) such as graalvm or quarkus. (I know so little > about this that I could be wrong about what these are). > With cloud native I mean an example that really fits in all aspects of cloud readiness. I am not really concerned about compiling to native code. We could try it but I think it is not necessary for a typical cloud service. For serverless it would be different but I am not targeting this space. Christian -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
