Kristian, Thanks for the input. You're pretty much pouring "salt into a wound" that was ripped open during a massive shrinkage of Tamaya after an initial codebase came from ideas Anatole and a few others (also inspired by Oracle, but it decided not to standardize that as of now) discussed here: https://github.com/java-config/tamaya-export/tree/master/api/src/main/java/org/apache/tamaya (note this is NOT a mirror of Tamaya and only mentioned for comparison)
You'll see the concept of "Environment" existed, but was then pruned until further notice. IMHO missing, because that's among key features making Tamaya more powerful and preferable over e.g. the revamped Apache Commons Config. DeltaSpike on the other hand got a module dedicated to this: https://deltaspike.apache.org/javadoc/1.3.1-SNAPSHOT/org/apache/deltaspike/core/api/projectstage/package-frame.html It is a "lessons-learned" from the restrictive and unfit hard-coded JSF stage enum that tried to mimick Ruby on Rails, too. As of now a rather mighty but abstract concept of ConfigQuery could allow you to define queries like "stage='unit test'" but those query classes are yet to be defined. We'd appreciate your input, either on the mailing list or if you have a concrete idea and JIRA account, you may also consider a "requirement" or "improvement" ticket in JIRA. Cheers, Werner Keil | JCP EC Member, JSR 363 Co Spec Lead | Eclipse UOMo Lead, Babel Language Champion | Apache Committer | Advisory Board Member, Java Track Chair, DWX '15 Twitter @wernerkeil | @UnitAPI | @JSR354 | @JSR377 | @AgoravaProj | #DeviceMap | #DevOps | #EclipseUOMo Skype werner.keil | Google+ gplus.to/wernerkeil [image: --] Werner Keil [image: https://]about.me/wernerkeil <https://about.me/wernerkeil?promo=email_sig> On Thu, Apr 2, 2015 at 2:03 PM, Kristian Rink <[email protected]> wrote: > Folks; > > not sure whether I am right here. Stumbled across Tamaya in an article in > recent German Java Magazin and am starting to take a closer look. Starting > out: In our environment, we need a configuration strategy to provide > various (jetty/dropwizard based) applications with specific configurations > depending upon the very environment they run in (development system, > testing environment, production host). Something like the environments in > Ruby On Rails comes to mind; but so far we haven't found a standardized, > best of all "out-of-the-box" Java solution for that problem. > > I wonder whether Tamaya has approaches or ideas to solve this issue? Is > this on your list of things done / to be done? Any thoughts about this? :) > > TIA and all the best, > Kristian >
