Hi all Looking at the discussions from this morning I think we need more discussions what core should contain. The term minimalistic obviosly is not precise enough. So we must agree in more detail what the features and objectives of core are. So I make a first try:
1. it should implement the api/spi for simple se usage. 2. it should provider enough logic to provide the minimal building blocks so a user could build a minimal config system. 3. said this I would expect that properties configs are supported ootb as a format. 4. I would expect that adding a propertysource is basically a one liner if the file is in the cp or a file. 5. I would expect that core helps me defining my location declaratively. users dont care about resource loading details, they expect the lib to handle that ootb. 6. I would expect that the mechanisms provided are extendible, so with adding additional modules the api basically still feels the same. Given that abstractions must be defined in the api or in core. 7. I dont think extension modules must rely on the api only (if that would be a decision we might have to discuss if the api may define more things). My idea is that tamaya is a combinable set of modules that as a whole can be tailored to the many different facets required. Constraining modules on api deps will probably lead to much duplications, but lets see... 6 and 7 are things to be argued about I think. If we see core as a supermonimalistic set that is not enough per se for all supertrivial usage scenarios I agree I would remove latest additions to a separate module. Perhaps this is even the best solution to keep our personal hygiene in place ;) Cheers Anatole - Anatole Tresch Glärnischweg 10 8620 Wetzikon Tel +41 (43) 317 05 30 - Send from Mobile
