Are you interested in controlling the configurations that are managed on the component's definition node (things like component group or sling resource super type) or configurations for the custom code you write in the JSP/Sightly of the component? I agree with Scott that you can't do that for the component definition node, but if you interested in controlling the behavior of your custom code there are a variety of ways to do that:
- You can code your component to pull the configurations in question from a central location in your site hierarchy - like say your root site node or language node - /content/mysite or /content/mysite/en.
- You can create a OSGI configuration service - either specific to you component or more general and use OSGI to manage the configurations - you need to access them either via a JSP tag or a WCM Use bean (if you are coding in Sightly).
There are multiple variations of those two approaches. Each of them has some pros and cons depending on exactly what kind of configurations you are trying manage.