Is that the little "Tamaya startup screen" similar to Spring Boot's? I guess for certain implementations it could be OK but has no room in the API. An API or Spec must not produce banners or splash screens, that is in most cases product-specific.
Spring and other solutions are generally seen as "products" by their creators, so gimmicks like splash screens also on the command line seem reasonable, but to inspire a possible standard or implement it, that IMHO has no room. The Apache branding on the website, even a logo that is fine, but the API should be product-agnostic. Also applies to Microprofile btw. I don't expect to see a "microprofile" banner other than on presentations or demos either. While each vendor, Tomitribe, Payara, IBM, etc. are free to put as many banners into their products as they wish;-) Werner On Wed, Nov 23, 2016 at 11:54 AM, Anatole Tresch <[email protected]> wrote: > Dear all > > I just did a pull on the core repo and realized that now the API has been > extended with BannerManager and more. For me this is a nogo. > BannerManagement must not have any influence on the API, also no additional > artifacts. This code should be moved over to the core part IMO. We might > even replace the API banner functionality with a small single line printout > or even remove this functionality completely from the API part. In the core > part, we can easily add the same functionality, when our Tamaya core is > loaded as an implementation... > > WDYT? > > J Anatole > > > -- > *Anatole Tresch* > PPMC Member Apache Tamaya > JCP Star Spec Lead > *Switzerland, Europe Zurich, GMT+1* > *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> * > *Twitter: @atsticks, @tamayaconf* >
