Hi Vincenzo, The development head of Kepler, and hence the forthcoming Kepler 2.0, allows users to keep their own configuration files for modules. These are stored in ~/KeplerData/modules/[module]/configuration/ configuration.xml. However these files don't specify the location of the log4j.properties file to use -- currently Kepler just uses the log4j.properties file found in the installation directory of the module with highest priority. I'll file an enhancement request for this, it shouldn't be too hard, but it may take us a bit to get to as we're trying to get bugs fixed so we can release 2.0 before adding any new features.
I also tried a variety of stopgap solutions without changing the codebase to either augment the classpath or send in the log4j jvmarg, but I couldn't get this to work. Derik On Feb 19, 2010, at 6:57 AM, Vincenzo Forchi wrote: > Hi, > > Is it possible to start kepler with a custom configuration file, > without having to modify the one in the kepler installation? > I'm thinking of a system-wide installation, where each user might > want to have different logging options, or saving to a file in their > home directory. > > I tried adding -Dlog4j.configuration=file:/path/to/file to the VM > parameters, but it didn't seem to work. > > Thanks in advance, > Vincenzo > > -- > Vincenzo Forchi European Southern Observatory > Karl-Schwarzschild-Strasse 2, D-85748 Garching bei Muenchen, > Germany. > Email: vforchi at eso.org Tel: +49 89 32006136 Fax: +49 89 3202362 > _______________________________________________ > Kepler-users mailing list > Kepler-users at kepler-project.org > http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
