I want to consider adapting the build process so config files are included in the mmbase jar, in the org.mmbase.config package (i.e. the storage configuration files would be in org.mmbase.config.storages.databases).
This means that you can then start mmbase with only the mmbase.jar. In your own config direcytory you then only need to incldue the files you override.


This basically amounts to changing the 'resources' target in build.xml to:

<target name="resources">
<copy todir="${build.dir}/classes" preservelastmodified="true">
<fileset dir="${source-src.dir}">
<include name="**/*.properties"/>
<include name="**/LICENSE"/>
<include name="**/*.dtd"/>
<include name="**/*.xml"/>
</fileset>
</copy>
<mkdir dir="${build.dir}/classes/org/mmbase/config"/>
<copy todir="${build.dir}/classes/org/mmbase/config" preservelastmodified="true">
<fileset dir="${source-config.dir}">
<include name="**/*.properties"/>
<include name="**/LICENSE"/>
<include name="**/*.dtd"/>
<include name="**/*.xml"/>
</fileset>
</copy>
</target>



This hack is part of step 9 of the Optimization project.

START OF VOTING:   2004/11/30 16:00
END OF CALL:       2004/12/3 16:00

 [_] +1 (YES)
 [_] +0 (ABSTAIN )
 [_] -1 (NO), because :
 [_] VETO, because:


-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Some Drink at the Fountain of Knowledge. Others Just Gurgle."

_______________________________________________
Developers mailing list
[EMAIL PROTECTED]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to