How does it work in an app that may have its own splash screen? I know if you develop plugins or components for Eclipse or other IDEs this can show used technologies, but how about standalone apps, will Tamaya show up like a "nag screen" there?;-)
Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead | Eclipse UOMo Lead, Babel Language Champion | Apache Committer Twitter @wernerkeil | @UnitAPI | @JSR354 | @AgoravaProj | @DeviceMap | #DevOps | #EclipseUOMo Skype werner.keil | Google+ gplus.to/wernerkeil On Fri, Jun 17, 2016 at 1:23 PM, John D. Ament <[email protected]> wrote: > On Fri, Jun 17, 2016 at 7:14 AM Oliver B. Fischer < > [email protected]> > wrote: > > > Hi guys, > > > > I startet using Tamaya in a little small tool we use at work. There are > > two things I would like to discuss with you: > > > > 1. The banner of Apache Tamaya is always shown at startup. This is nice > > and at the same time disturbing. Maybe this should be configurable? > > > > I agree. It makes sense for the server component, to know that its there, > but for a client library, its a bit in-your-face. > > > > > > 2. If I am not mistaken the default behaviour is to load all properties > > from /META-INF/javaconfiguration.properties. As I have many properties I > > would like to spread them over multiple property files. But I think we > > don't support his at the moment. Is this correct? If no, would it be a > > reasonable extension for us? > > > > I use > > https://github.com/apache/incubator-tamaya/blob/master/code/core/src/main/java/org/apache/tamaya/core/propertysource/SimplePropertySource.java > to > register custom property files. > > > > > > WDYT? > > > > Bye, > > > > > > Oliver > > > > -- > > N Oliver B. Fischer > > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > > P +49 30 44793251 > > M +49 178 7903538 > > E [email protected] > > S oliver.b.fischer > > J [email protected] > > X http://xing.to/obf > > > > >
