在复杂环境中处理属性和log4j的工具 [英] Tool to handle properties and log4j in a complex environment
问题描述
我在一个相当大的J2EE电子商务网站（30亿营业额）上工作，我们开发人员对我们处理属性和log4j配置的方式感到厌倦。
I work on a pretty big J2EE e-commerce website (3 billion turnover) and we developpers are kinda bored of the way we handle properties and log4j config.
我们实际上有很多应用程序，其中一些使用主应用程序。每个应用程序都有次要版本，每个版本都有一个属性/ log4j配置，可以处理许多环境（开发/打包/集成/测试/预生产/生产）。
我们不能将属性直接放在SCM上。
我所谈论的属性不在耳/战文件中。
We actually have many applications, some of them use a main application. Each application have minor versions and each version have a properties/log4j configuration that handle many environnements (dev/packaging/integration/tests/pre-production/production). We can't put the properties directly on the SCM. The properties i talk about are not in ear/war files.
我们会说应用程序B-App正在使用主应用程序App-A而我们有版本1.0和2.0
We'll say that application B-App is using main application App-A and we have versions 1.0 and 2.0
问题是我们的工具有效，但根本不直观，并且合并通常是不好的，或者没有正确完成，因为这个过程很难尊重...因此，当我们将一个次要版本投入生产时，我们有时会有一些惊喜......一个属性或记录器消失，一个属性更新被回滚......
The matter is that our tool works but is not intuitive at all, and merges are often fortogotten, or not done properly because the process is hard to respect... thus when we put a minor version in production we sometimes have some surprises... a property or logger disappear, a property update is rollbacked...
例子：
我在主应用程序中添加属性xxx.yyy App-A 1.0
然后，如果合并没有正确完成，当我们将App-A 2.0投入生产时，该属性将不存在。
和App-B，也应该使用xxx.yyy，也不能拥有该属性，即使在1.0版本中（这应该仍然是一个手动过程，因为App-A中没有使用App-A的所有属性） ）
Exemple: I add a property xxx.yyy in main application App-A 1.0 Then if the merge is not done correctly the property won't be there when we put App-A 2.0 in production. And App-B, that should normaly also use xxx.yyy, could not have the property too, even in 1.0 version (this should remains a manual process since all properties of App-A are not used in App-B)
我想知道是否有一个开源工具可以很好地处理历史记录，用户权限......
也许我应该开始一个...
I wonder if there is an opensource tool to handle this nicely with historization, user permissions... Perhaps i should start one...
推荐答案
我认为你不需要工具（至少不需要工具）。
I dont think you need a tool (at least not at first).
您需要一个明确定义的流程。在会议室中获取一些利益相关者，并了解在给定生命周期中应该发生的事情，然后找出所需的工具，以确保遵循该流程，并尽可能简单。
You need a clearly defined process. Get some stakeholders in a meeting room and thrash out what should happen in a given lifecycle, then work out what tools you need to ensure that that process is followed, and as easy to do as possible.
这篇关于在复杂环境中处理属性和log4j的工具的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
