You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by Anatole Tresch <at...@gmail.com> on 2016/11/23 10:54:22 UTC
Latest updates regarding banner management
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*
Re: Latest updates regarding banner management
Posted by "P. Ottlinger" <po...@apache.org>.
Am 23.11.2016 um 19:36 schrieb Oliver B. Fischer:
> So, I will move it to the core?
+1
Cheers,
Phil
Re: Latest updates regarding banner management
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
The only place I see for this functionality is the
DefaultConfigurationProvider. Right?
As far as I see we do not offer an indendent way to initialize a library
which provides implementations of our API. Maybe this would be a
possible enhencement? If yes this functionality would overlap with
OSGIActivator#startBundle().
WDYT?
Oliver
Am 23.11.16 um 21:41 schrieb Anatole Tresch:
> �10 yes, please\U0001f60a
>
> Am 23.11.2016 19:36 schrieb "Oliver B. Fischer" <o....@swe-blog.net>:
>> Anatole, I agree. I left it in the api package as the same functionality
> was still there but in the ConfigurationProvider. BTW these classes are not
> accessible from other packages.
>> So, I will move it to the core?
>>
>> Oliver
>>
>>
>> Am 23.11.16 um 11:54 schrieb Anatole Tresch:
>>
> additional
> printout
> core
>> --
>> N Oliver B. Fischer
>> A Sch�nhauser Allee 64, 10437 Berlin, Deutschland/Germany
>> P +49 30 44793251
>> M +49 178 7903538
>> E o.b.fischer@swe-blog.net
>> S oliver.b.fischer
>> J oliver.b.fischer@jabber.org
>> X http://xing.to/obf
>>
--
N Oliver B. Fischer
A Sch�nhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Latest updates regarding banner management
Posted by Anatole Tresch <at...@gmail.com>.
×10 yes, please😊
Am 23.11.2016 19:36 schrieb "Oliver B. Fischer" <o....@swe-blog.net>:
>
> Anatole, I agree. I left it in the api package as the same functionality
was still there but in the ConfigurationProvider. BTW these classes are not
accessible from other packages.
>
> So, I will move it to the core?
>
> Oliver
>
>
> Am 23.11.16 um 11:54 schrieb Anatole Tresch:
>
>> 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
>>
>>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
Re: Latest updates regarding banner management
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Anatole, I agree. I left it in the api package as the same functionality
was still there but in the ConfigurationProvider. BTW these classes are
not accessible from other packages.
So, I will move it to the core?
Oliver
Am 23.11.16 um 11:54 schrieb Anatole Tresch:
> 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
>
>
--
N Oliver B. Fischer
A Sch�nhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Latest updates regarding banner management
Posted by Werner Keil <we...@gmail.com>.
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 <at...@gmail.com> 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*
>