Hi, > > Dont put it in a Constant.java or Maven.java > Okay, there we're having a disagreement as I would create something like "OpenEJBProperties".
> Perso i try to create constants only when reusable. The m2 one for instance > is almost internal and not that used at runtime so -+0 to have a constant > for it, in particular cause we can desire to switch it later at runtime > (one reason why some theorically constants are not static final) > I'm not talking about constants, I'm talking about properties or to be more precise property keys. If a property key is used within the production code it has an effect on the runtime so it should be knowledgeable for all developers and not just the developers who are in contact with a certain component. I think I understand where you're coming from as we're not that far away from each other. The intention of such a collection of property keys is primary meant for maintenance and knowledge purposes. It could be declared as internal which discourages it's use by 3rd party developers. When we've got such a collection of property keys we can figure out which ones are truly necessary, or should be named more apropriately or could be dropped. Best regards Daniel Kasmeroglu
